1.7.10 Server Crash: Exception while updating neighbours

[Dad_Yoshi]

If I remove the LOTR mod the error shifts to some other mod's block (like from Railcraft). Already regenerated the world at least 20 times with various mods removed. Using Realistic Terrain Generator when building world.

 

This has been a pain for over three weeks now...

 

http://pastebin.com/RXigWfb6

[Dad_Yoshi]

If I remove the LOTR mod the error shifts to some other mod's block (like from Railcraft). Already regenerated the world at least 20 times with various mods removed. Using Realistic Terrain Generator when building world.

 

This has been a pain for over three weeks now...

 

http://pastebin.com/RXigWfb6

[Dad_Yoshi]

Logs are here:

 

https://www.dropbox.com/sh/6850siws1jt0d28/AABS2z8Qv3yfPdmoUKqRh5wJa?dl=0

 

If others are needed please let me know.  This time block 255 was assigned to thaumcraft.common.blocks.BlockWarded

 

Thanks!

[Dad_Yoshi]

Logs are here:

 

https://www.dropbox.com/sh/6850siws1jt0d28/AABS2z8Qv3yfPdmoUKqRh5wJa?dl=0

 

If others are needed please let me know.  This time block 255 was assigned to thaumcraft.common.blocks.BlockWarded

 

Thanks!

[Dad_Yoshi]

If I use NEI to dump the block data, this is what I have for 255

 

Thaumcraft:blockWarded,255,true,null,thaumcraft.common.blocks.BlockWarded

 

which is the block ID referenced in the crash log (255 gets assigned to different blocks depending upon which mods I have).  In my original crash file (see the pastebin link) it references a block from the LOTR mod.

[Dad_Yoshi]

If I use NEI to dump the block data, this is what I have for 255

 

Thaumcraft:blockWarded,255,true,null,thaumcraft.common.blocks.BlockWarded

 

which is the block ID referenced in the crash log (255 gets assigned to different blocks depending upon which mods I have).  In my original crash file (see the pastebin link) it references a block from the LOTR mod.

[Dad_Yoshi]

Yes, it eventually crashes with another block from some other mod (Aether, Railcraft, etc) - each of which are assigned ID 255 (depending upon which mods I am starting with)

[Dad_Yoshi]

Yes, it eventually crashes with another block from some other mod (Aether, Railcraft, etc) - each of which are assigned ID 255 (depending upon which mods I am starting with)

[Dad_Yoshi]

The OP pastebin link is to a crash report.  Is there something else needed?

[Dad_Yoshi]

The OP pastebin link is to a crash report.  Is there something else needed?

[Dad_Yoshi]

http://pastebin.com/bvkzGAms

[Dad_Yoshi]

Yes, each time I generate a new world I can play for maybe 2-5 minutes until the crash. 

[ScottehBoeh]

Seems like the blocks from the LOTR Blocks mod seem to be glitched on your map. Any chance you could run the map on vanilla 1.7.10, just to remove the modded blocks? That could potentially fix the issue.

[Dad_Yoshi]

https://www.dropbox.com/s/2uwv1s1pt91dbrt/AnuranClientModPack.zip?dl=1

 

This is the link to the client modpack.

 

 

[Dad_Yoshi]

Well here is an update on this issue.

When the world is generated the various mods which add blocks to the game are processed in alphabetical order based on the name of the file in the 'mods' folder.  The vanilla blocks go up to around 170 and then new blocks are assigned.  You can manipulate which block is given the id of 255 based on which ones you have the system process first.  You do this by changing the file name of the mod file and add an '1' or 'a' to the start of the existing name.

 

I was able to have a world generated with tin ore from the LOTR mod be assigned the id of 255.  With this I have been able to avoid the crash thus far.  However, this has resulted in an overabundance of tin ore in the world but that is minor compared to the crashing/restarting.

 

What I would like to see is a way to assign a specific block to 255 or to somehow have chunk generation substitute it for another.

 

[Dad_Yoshi]

Since the issue seems to be focused around block 255 you should generate a world using Minecraft Server with Forge 10.13.4.1614.  Remove the xaero's Minimap, Dynamic Lights, and Optifine before launching the server.

 

Enter the world with the client, go to NEI, then generate a list of blocks.  Look at the .csv in a text editor and search for 255.  Note the block assigned to that ID.

 

If it is some weird block at some point you will crash the server as you wander around.  This has taken as long as 10-15 minutes for me.  Also, if you can find some place in the various biomes which use block 255, you will see one messed up world.

 

If you delete the world, rename various mod files so they are in a different order (i.e., make Railcraft load  first), you will see block 255 is some other value but the issue still remains.

[Dad_Yoshi]

Thanks anyway.  I found a way to get around the issue via manipulation of how the mods are loaded.

[Dad_Yoshi]

This mod is a great way to overcome the problem with the world generation I was having.

 

http://minecraft.curseforge.com/projects/progressive-world-cleanup

 

Once I got the Block IDs assigned to use lotr:rock as ID 255 I could use Progressive World Cleanup mod to replace it with minecraft:dirt.