Just tracked it down. Forge does not pass the player in useItemOnEntity, and since we don't know who's the player, it doesn't get energy from the batpack.
Posts by RichardG
-
-
Sounds are known to cause lag, disable them for now. But wait, I've never heard about reducing the source limit reducing lag.
-
Let the crash happen before getting the console output.
-
Finished integrating the reactor chamber fix, this time with my own code.
-
Use Forge 1.3.3.12 until the next hotfix
-
Use Forge 1.3.3.12, newer versions removed an old file we were using. Next hotfix will fix that
-
Chill dude. I don't know anything about our sound manager, but I do know paulscode's sound system is not suitable for us and we need a solution with raw OpenAL.
-
Windmills seem to turn into generators and drop iron when they break.
-
Aware of it, fixed.
-
Run this tool to get a full report:
https://github.com/downloads/m…craftError/MCErrorV25.jar
Any "failed to load config" errors?
-
Alright, Forge deleted a deprecated interface we were using. Use 1.3.3.12, next hotfix will fix that.
-
Forge is installed incorrectlyAlright, Forge deleted a deprecated interface we were using. Use 1.3.3.12, next hotfix will fix that. -
-
Use NEI or CraftGuide
-
Then it's a client crash, run this tool to get a report:
-
This has been bugging people for a good while, nothing you can do unless disabling sounds.
-
Upgrade Forge to 1.3.3
-
I actually find the extra slot EXTREMELY useful. Why? When I go to macerate or smelt an ore, but find I have another one already in progress, I stick the ore in the slot. Helps so much.
Not anymore :trollface:
No really, why would one put blocks in an expansion slot? I know you start by punching trees, you can carry 230 tons of solid gold, etc. but that seems unreasonable.
-
Not a limitation, I do use our electric item code (use()) on the shearing op.
-
Next snapshot will be full of bugfixes for a possible 1.2 following it
