The Meaning of Life, the Universe, and Everything.
Location:
Somewhere
Join Date:
11/29/2012
Posts:
619
Location:
Australia
Minecraft:
The_SlayerMC
Member Details
Hey, uhh.. Ii was working on DivineRPG's blocks and all of a sudden it stopped loading mc and crashed, so i commented out the block i just added and it loaded up fine again, i un commented it so i could see what the crash was. The crash turned out to be at registering blocks, it said something like this
"divinerpg : add : net.divinerpg.vethea.blocks.dreamgrass 256" THEN on the line underneath it:
"divinerpg : add : net.divinerpg.vethea.blocks.dreamgrass 40XX" (I cant remember the exact number)
But for those of you who have started using 1.7 forge, you would know that the system prints the block/item additions twice.
I don't know why it was set to 256 than to a completely different number in about 0.001 seconds...
I'm thinking that the blocks ID's can only be set under a byte for now or maybe for ever. But what ever it was, it has stopped DivineRPG's progress...
If anyone else has this problem or anyone else knows how to fix it. You would be of much help
that isn't incorrect, I've easily added items/blocks into the game without setting any ID's
No, it's incorrect. Whenever you register an item, even without an ID evident, it will still set an ID, like id++ each time you register it. Go to Minecraft, open a world, press F3+H and look at your items, next to the item name there is an ID. There will be an ID no matter what. The DivineRPG have been exploring 1.7.2 Forge and such for a while now and we have figured out that it does this.
"divinerpg : add : net.divinerpg.vethea.blocks.dreamgrass 256" THEN on the line underneath it:
"divinerpg : add : net.divinerpg.vethea.blocks.dreamgrass 40XX" (I cant remember the exact number)
But for those of you who have started using 1.7 forge, you would know that the system prints the block/item additions twice.
I don't know why it was set to 256 than to a completely different number in about 0.001 seconds...
I'm thinking that the blocks ID's can only be set under a byte for now or maybe for ever. But what ever it was, it has stopped DivineRPG's progress...
If anyone else has this problem or anyone else knows how to fix it. You would be of much help
Incorrect, you do set IDs in 1.7, but it's never used. There is a block ID cap set by Mojang themselves and Forge has yet to fix it.
No, it's incorrect. Whenever you register an item, even without an ID evident, it will still set an ID, like id++ each time you register it. Go to Minecraft, open a world, press F3+H and look at your items, next to the item name there is an ID. There will be an ID no matter what. The DivineRPG have been exploring 1.7.2 Forge and such for a while now and we have figured out that it does this.
True true, I woke up and saw your post, I'm still a bit tired at the moment, sorry for any confusion.
So.. even if you don't set a ID, an ID is still set. There we go.