Sushen

Here is more detail if you're wondering what I'm talking about - which I doubt, but one never knows ^^ I'm running the following code in the first onTickInGame modloader call : Field[] fields = EntityRenderer.class.getDeclaredFields(); String msg = "Fields for class " + EntityRenderer.class.getName(); for (Field field : fields) { msg+= "\n"+field.getName(); } Log.info(msg); // log with my own logger class This code prints all fields of the EntityRenderer class (mcp name), which is bfr class with 1.5.1 mc version. Results with vanilla or modloaded minecraft is : .. and here with forge : Funny, because I'm asking fields for the bfr class, and I get answers for (magically translated ) client.renderer.EntityRenderer class! (along with mcp mappings)

Hi, I'm the CameraStudio mod author, I post in here because my mod used to work with versions prior to 1.5, but now it doesn't launch anymore with forge's latest version (although it's totally compatible with modloader). As an experienced developer, I always paid attention to stay compatible with other mod makers, BUT, after some investigations, I found out that your reobfuscated code keeps searge field mappings instead of restoring minecraft vanilla ones. To be more precise, it seems out you're changing the field names dynamically with the asm lib - at least I suspect it, because the vanilla fields are present in your distrib class files, but not anymore when Minecraft is launched. I don't know if it's intended to work so, but, by doing such a thing, you're breaking compatibility with all other mods that need to acces minecraft specific internals. I don't know if you're aware of this problem, so, I report it here, and I would like to know if you're going to change something about this behavior. Thank you for your attention, Sushen