Technical Help
|
|
Here are some common issues found when installing and running the mod.
If you find a bug, please report it in an email on the "About" page so we can fix it ASAP!
See the Downloads page for the files that you need to run OreSpawn.
If you find a bug, please report it in an email on the "About" page so we can fix it ASAP!
See the Downloads page for the files that you need to run OreSpawn.
Id Conflicts
BlockId conflicts: Edit the .minecraft/config/OreSpawn.cfg file with your favorite text editor. You can change the BaseBlockID field to help remove blockID conflicts. The default is 2700. OreSpawn uses about a 400-block range. You can change the BaseBlockID value from about 600 to 1800, or 2500 to 3600.
ItemID conflicts: Edit the .minecraft/config/OreSpawn.cfg file with your favorite text editor. You can change the BaseItemID field to help remove conflicts between mods. The default is 9000. OreSpawn uses about a 500-item range. You can change the BaseItemID field to anything from about 3000 to 31500.
DimensionID conflicts: Again, edit the OreSpawn.cfg file. OreSpawn uses dimensionIDs from around 80 to 85 by default. You can change the BaseDimensionID field to anything from around 10 to 250.
BiomeID conflicts: Again, edit the OreSpawn.cfg file. OreSpawn used biomeIDs from about 120 to125. You can change the BaseBiomeID field to anything from around 50 to 250.
ALL IDS CAN BE FOUND UNDER the "orespawnids" section of the OreSpawn.cfg file.
ItemID conflicts: Edit the .minecraft/config/OreSpawn.cfg file with your favorite text editor. You can change the BaseItemID field to help remove conflicts between mods. The default is 9000. OreSpawn uses about a 500-item range. You can change the BaseItemID field to anything from about 3000 to 31500.
DimensionID conflicts: Again, edit the OreSpawn.cfg file. OreSpawn uses dimensionIDs from around 80 to 85 by default. You can change the BaseDimensionID field to anything from around 10 to 250.
BiomeID conflicts: Again, edit the OreSpawn.cfg file. OreSpawn used biomeIDs from about 120 to125. You can change the BaseBiomeID field to anything from around 50 to 250.
ALL IDS CAN BE FOUND UNDER the "orespawnids" section of the OreSpawn.cfg file.
Lag
General Slowness/Lag: A little lag can be expected while generating brand new chunks. That's the way the chunk generator works. I've optimized as much as I can, including making my own special setBlock() that strips out lighting. Until they fix chunk generation to operate in its own separate thread and pre-generate in the direction of travel, there is nothing else I can do.
Excessive lag and slowness can be caused by many things. Here are the three most significant things you can do:
1) Turn off Smooth Lighting. This is a beast!!! I was surprised by just how much CPU the lighting algorithms take. You will be too.
2) Change your Graphics Mode to "Fast". OreSpawn has been updated in V11 to use this feature for tree leaves. OreSpawn has a lot of trees. Trees have a lot of leaves. Leaves in "Fancy" graphics mode are rendered on all four sides whether they are visible or not. Leaves in "Fast" graphics mode are rendered only on the visible side. Big improvement, but it doesn't quite look the same.
3) Give your Minecraft java more memory. Edit your Forge Launch profile. See the "JVM Arguments" checkbox at the bottom? Check it. Now change "-Xmx1G" to either "-Xmx1500M" or "-Xmx2G". This will give java a lot more memory to play with and it won't have to swap things around so much.
Getting too much random lag in the Island Dimension? Solution 1) Wait until all the islands around you have spawned. Usually the lag will go away after things settle down. For a block-based game, setBlock() is uncharacteristically slow. Spawning Islands sets a lot of blocks. Solution 2) Get a faster machine. Solution 3) Edit Orespawn.cfg and lower the Island* numbers. They default to 2 (5 max). Try 1 instead. Then make another world or move to a new chunks area. Solution 4) Find and kill the Island Entities that make the Islands move. Sometimes the big Islands will cause lag. The round Islands eat CPU as well, but then the Triffids won't spawn... Usually tracking down and killing the big Island entities will do the trick though. Solution 5) Spawn a few Beavers. Leaves eat CPU. Beavers eat trees.
Excessive lag and slowness can be caused by many things. Here are the three most significant things you can do:
1) Turn off Smooth Lighting. This is a beast!!! I was surprised by just how much CPU the lighting algorithms take. You will be too.
2) Change your Graphics Mode to "Fast". OreSpawn has been updated in V11 to use this feature for tree leaves. OreSpawn has a lot of trees. Trees have a lot of leaves. Leaves in "Fancy" graphics mode are rendered on all four sides whether they are visible or not. Leaves in "Fast" graphics mode are rendered only on the visible side. Big improvement, but it doesn't quite look the same.
3) Give your Minecraft java more memory. Edit your Forge Launch profile. See the "JVM Arguments" checkbox at the bottom? Check it. Now change "-Xmx1G" to either "-Xmx1500M" or "-Xmx2G". This will give java a lot more memory to play with and it won't have to swap things around so much.
Getting too much random lag in the Island Dimension? Solution 1) Wait until all the islands around you have spawned. Usually the lag will go away after things settle down. For a block-based game, setBlock() is uncharacteristically slow. Spawning Islands sets a lot of blocks. Solution 2) Get a faster machine. Solution 3) Edit Orespawn.cfg and lower the Island* numbers. They default to 2 (5 max). Try 1 instead. Then make another world or move to a new chunks area. Solution 4) Find and kill the Island Entities that make the Islands move. Sometimes the big Islands will cause lag. The round Islands eat CPU as well, but then the Triffids won't spawn... Usually tracking down and killing the big Island entities will do the trick though. Solution 5) Spawn a few Beavers. Leaves eat CPU. Beavers eat trees.
Packet24MobSpawn Crashes
This is a known issue with the base Minecraft code which only supports 256 total entities. We are hoping that this is fixed in 1.7.2. Unlikely, but we can hope... In short, you have too many mobs. OreSpawn is huge. It cannot be combined with other huge mods. There just is not enough space for all the critters running around. Some special blocks and items also use up entity space. Take a look at your mods and remove a few that you really don't need.
Another possible cause of this problem is that some mods are not aware of the bug involving entity IDs over 127. OreSpawn will push mods that are loaded after itself well over that magic number. They may not be able to handle it properly (there is a little-known workaround). The only solution, again, is to remove other mods until it all works.
Another possible cause of this problem is that some mods are not aware of the bug involving entity IDs over 127. OreSpawn will push mods that are loaded after itself well over that magic number. They may not be able to handle it properly (there is a little-known workaround). The only solution, again, is to remove other mods until it all works.
Other Problems
Do you have a recent version of Java? They're up to 7-something. Please check and update if necessary. Please note that the 64-bit version of Java must be manually downloaded and installed. Java people are still in the stone age, and haven't figured out that normal people have moved on to 64-bit platforms.
Are you running the correct version of Forge? Please go to files.minecraftforge.net and get the Forge 9.11.1.965 installer. Versions 11-15 of OreSpawn were built and tested with Forge 9.11.1.965.
Are some of your mods out of date? Maybe from 1.5.2? Please either update or remove them.
Interference with other mods? 9 times out of 10, the problem is another mod that does not play nicely with others. The easiest thing to do, is to remove all the mods except OreSpawn and make sure it works. Then add back your other mods one at a time until you find the culprit. There may be more than one, so keep adding them back one at a time.
If you have a MAC... Go see our Installation page!
If you have an XBOX, you're on your own. Sorry. Try google.
How do you install Forge? Go see our Installation page!
How do you install mods? Go see our Installation page!
Are you running the correct version of Forge? Please go to files.minecraftforge.net and get the Forge 9.11.1.965 installer. Versions 11-15 of OreSpawn were built and tested with Forge 9.11.1.965.
Are some of your mods out of date? Maybe from 1.5.2? Please either update or remove them.
Interference with other mods? 9 times out of 10, the problem is another mod that does not play nicely with others. The easiest thing to do, is to remove all the mods except OreSpawn and make sure it works. Then add back your other mods one at a time until you find the culprit. There may be more than one, so keep adding them back one at a time.
If you have a MAC... Go see our Installation page!
If you have an XBOX, you're on your own. Sorry. Try google.
How do you install Forge? Go see our Installation page!
How do you install mods? Go see our Installation page!
