SanAndreaP

If Forge would prevent MC from removing the unused stuff from the world save, the problem would be, if the user screws up something and they delete all their mods (which would include Forge being removed, too) then those people would still loose their modded stuff. The best way would be if Mojang would implement a warning message (similar to what Forge already provides), which notifies the User if the world has unused Block-/Item-IDs. Then they can choose, if they wanna continue to load (which would involve loosing mod-stuff) or canceling the loading and brings the user back to the world list.

Yeah, that's because vanilla removes unused block- / item-IDs from the world save. Just backup your world before you change things.

Also you have to give the full class path in your dependencies string, NOT the modID! Mine would look like this: dependencies="after:sanandreasp.mods.managers.SAP_ManagerRegistry"

I'm most curious about HOW did you installed it!?

Clean your coremods folder.

Clean your coremods folder.

1. Could you please give us some code? Especially the parts where you register the textures in your blocks/items. 2. Make sure that you spelled it right, especially since it's case-sensitive!

2013-03-29 20:45:44 [WARNING] [ForgeModLoader] Zip file [1.5.1]Eternals Swords Secret Update [Forge].zip failed to read properly, it will be ignored java.util.zip.ZipException: error in opening zip file at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.<init>(Unknown Source) at java.util.zip.ZipFile.<init>(Unknown Source) at java.util.zip.ZipFile.<init>(Unknown Source) at cpw.mods.fml.common.discovery.JarDiscoverer.discover(JarDiscoverer.java:41) at cpw.mods.fml.common.discovery.ContainerType.findMods(ContainerType.java:42) at cpw.mods.fml.common.discovery.ModCandidate.explore(ModCandidate.java:64) at cpw.mods.fml.common.discovery.ModDiscoverer.identifyMods(ModDiscoverer.java:115) at cpw.mods.fml.common.Loader.identifyMods(Loader.java:346) at cpw.mods.fml.common.Loader.loadMods(Loader.java:478) at cpw.mods.fml.client.FMLClientHandler.beginMinecraftLoading(FMLClientHandler.java:160) at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:407) at net.minecraft.client.MinecraftAppletImpl.func_71384_a(SourceFile:56) at net.minecraft.client.Minecraft.run(Minecraft.java:729) at java.lang.Thread.run(Unknown Source) Sure... errors in the common of Forge... Your ZIP is somehow corrupted, therefore Forge can't open it. Either try again until it works, or get 7zip.

Either you screwed up the installation or it's a bug in Buildcraft. Try to reinstall everything and if it still gives you the same error, talk to the Buildcraft people. Nothing to do with Forge.

Wrong. The constructor of the AxisAlignedBB is protected. The correct call would be AxisAlignedBB bb = AxisAlignedBB.getBoundingBox(minx, miny, minz, maxx, maxy, maxz);

"Thou shall use the latest Forge" It is 7.7.1.616, by the way.

Actually there's a forge-hook for this purpose! It's called << int getLightValue(IBlockAccess world, int x, int y, int z) >> You can read the javadoc what it does and what you have to return.

[*]That's not quite correct The names prior to the deobfuscation (the "real" obfuscation encountered in the original minecraft.jar) has names like "a" or "z" or "xy". If you run the deobfuscation, the names will first be translated to so-called "SRG"-names (indices given by MCP), which are called "func_xxxx" for methods/functions or "field_xxxx" for fields/variables. After that, these will be translated into "CSV"-names and they'll get "sense-making" names like "registerIcon(...)" or the like. If the CSV mappings don't contain such a name, the name will simply stay like "func_xxx/field_xxx". [*]It's not that weird The ItemStack is only for seperately instantiating items (you may notice the actual item class is only instanciated once) to save NBTTags (enchantments, for example), save the damage value (tools) / metadata (dyes) and the stack size. The EntityItem is only there for "outside" interactions with the environment (like picking them up or dying in lava/fire).

When creating the item, it's index will be shifted up with 256, means the end-ID wil be YOUR-ID + 256. So either you add 256 to your ID when "/give"-ing or decrease the ID in the initialization with 256.

Your solution is wrong. It's clearly a mod crash (which is caused by the MutantCreatures mod), since the Forge version is 7.7.0.608 and it's for MC 1.5.1!

The problem is that every mod is obfuscated (either with notch names or with srg names). The MCP workspace though, is deobfuscated, so it will throw you the NoClassDefError. You can only use these mods if you put their source, if available, into the MCP source.

The modid param is the Mod-ID and must be identical to the modid variable in the @Mod annotation. description is a short description of what your mod adds / does. You can leave that blank if you want. There's also a param named logoFile which links to the logo file in your package, e.g. "logoFile": "/logo_SAPMan.png". The logo file is named "logo_SAPMan.png" and is in your zip file (in no sub-directories). EDIT: The file goes into your ZIP (in no sub-directories). I don't know how to do it within MCP, though.

No The same crash You can try to switch the encoding of the file to ANSI (in case of Notepad++: Encoding -> ANSI) and see if the first character is somehow "corrupted" or just an empty space. Delete it and save the file. Then try again. No... Then can you upload that config file?

No The same crash You can try to switch the encoding of the file to ANSI (in case of Notepad++: Encoding -> ANSI) and see if the first character is somehow "corrupted" or just an empty space. Delete it and save the file. Then try again.

Too many mods are using the "vanilla" entity registration (which is limited to 256 entities, including vanilla ones), so there are no IDs left for new ones. I think in 1.5 the entity count is increased, but I'm not sure about that. Solution: Update to MC 1.5 or use less mods.

I don't know about the Backpack mod, if it needs to be updated to 1.5.1, but for the EnderStuff+ mod, did you install the Manager pack? If yes, give the logs when you install EnderStuff+ and the Manager Pack and it still crashes!

Delete the file C:/Users/Breixo/AppData/Roaming/.minecraft/config/ComputerCraft.cfg and try again.

Go yell at Optifine, not at Forge.

What I'm curious about is, where's your Minecraft project in your Package explorer? Did you even deobfuscate?

You could try to surround your render stuff with GL11.glPushMatrix() and GL11.glPopMatrix(), like: pushMatrix() your render stuff popMatrix()