I was on vacation for a week and didn't have time to play or update. I just copied my Alice folder (I still want to visit the 1.4 server a few times) and updated the copy to 1.5. After starting, Minecraft immediately crashed with an error screen containing this: Code: java.lang.IllegalArgumentException: Slot 4049 is already occupied by mods.immibis.redlogic.lamps.BlockLampCube$Off@144cd692 when adding magicbees.block.BlockPlanks@409b15a7 This seems like another ID conflict to me. Perhaps it's happening because I overwrote my old files. I'll try and re-download Alice 1.5 in a completely new folder, without overwriting. Just wanted to throw it in here in case someone else is experiencing problems. Here's my system/installation info from the error screen, you might need it. Spoiler Minecraft Version: 1.5.2 Operating System: Linux (amd64) version 3.8.0-19-generic Java Version: 1.7.0_25, Oracle Corporation Java VM Version: OpenJDK 64-Bit Server VM (mixed mode), Oracle Corporation Memory: 300940792 bytes (286 MB) / 537395200 bytes (512 MB) up to 954466304 bytes (910 MB) JVM Flags: 3 total; -Xms128M -Xmx1024M -XX:MaxPermSize=256M AABB Pool Size: 0 (0 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used Suspicious classes: FML and Forge are installed IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0 FML: MCP v7.51 FML v5.2.23.738 Minecraft Forge 7.8.1.738 Optifine OptiFine_1.5.2_HD_U_D5 SKCraft.com 138 mods loaded, 138 mods active mcp{7.51} [Minecraft Coder Pack] (minecraft.jar)
Perhaps it's because I skipped many updates and upgraded from the latest 1.4 version directly to the current 1.5 version? I'd have kept up with the updates, mind - but I only have a very old laptop and there was no 3G connection (if any mobile connection at all) and no wifi, so I couldn't play. I wanted to. Badly. Edit: I had to unpack my bags but now I'm installing a fresh 1.5. Let's see if it's any better. I do hope it is. Edit2: Maybe I should emphasize I'm running Linux - the launcher could have a problem there?
Also fixed it for me - glad it works now. This error shouldn't happen but if a reinstall works it out, it's not too bad... just tell all Linux users to do a fresh install instead of updating and everything should be alright.