Client crash on chunk entering

Question

Client crash on chunk entering

Xyclade opened this issue 11 years ago · 9 comments

Xyclade commented 11 years ago

As the title says, whenever I enter a specific chunk on my server, the following exception pops up:
http://pastebin.com/cKxajZem

Server version: MCPC+ Version 1.6.4 with Direwolf20 1.0.14 as modpack

progwml6 · Answer 1 · 2014-02-15T07:04:14.000Z

we do not support MCPC

Xyclade · Answer 2 · 2014-02-15T15:52:05.000Z

It seems unrelated to the server version. I ran a test with the Original FTB server version and it crashed as well on the same chunk.

Besides, I found in the pull request history that similar crashes in different classes were easily solved by checking on the length of the array, as it is a very common array index out of bounds exception.

I would really appriciate it being resolved.

Sunstrike · Answer 3 · 2014-02-15T19:54:59.000Z

tl;dr:

MCPC+ can go die in a fire, please.
Latest version or no resolution can/will be provided.

Really short version:

STAHP D:

Sunstrike · Answer 4 · 2014-02-15T19:55:28.000Z

Unless, this was the latest version? >>

mDiyo · Answer 5 · 2014-02-15T19:57:11.000Z

This is the latest version.

It appears the metadata on one of the crop blocks has went over the limit. It should be relatively easy to bypass on our end, but won't fix the real problem. Either you've loaded an old world with block IDs shifting around or one of your mods or plugins is doing nasty things with metadata.

mDiyo · Answer 6 · 2014-02-15T19:58:57.000Z

Could you give a list of your mods and plugins please?

Xyclade · Answer 7 · 2014-02-15T20:09:56.000Z

First of all, thank you!

The complete list of mods and plugins:

Direwolf 1.6.4 pack 1.0.14 (ahead of recommended build)
(I found it easier to list the ones disabled, rather than listing all mods in direwolf20, but in case you wish so, I can add those?)
With only these mods DISABLED:

ZansMinimap 1.6.4
JourneyMap3.1.0_Unlimited_MC1.6.4

Additional mods next to the direwolf pack:

Dynmap for forge (Version 1.9.2-1876)

Plugins:

Coreprotect V2.0.8 (this is pretty much the main reason we do not use the original Jar)
TobiMotd

As I am the server owner, not the actual player that has 'created' the crash chunk I do not know exactly what happened. I have asked him to tell me what he did, and he told me that he applied terraforming on the area before it started happening. He also placed some me system cables and stuff, but that seems unrelated, as you were talking about the metadata of items.

Additionally, as we have dynmap, I have placed a red marker on the map pointing out the area, which if rendered, crashes you. This might give more insight in what mods are active there. (the 3d view allows to see more)
http://minecraft.xyclade.nl:8124/

In case you need anything else please let me know!

Sunstrike · Answer 8 · 2014-02-16T00:35:57.000Z

https://feedthebeast.atlassian.net/wiki/display/PML/Direwolf20+%281.6.x%29+1.0.14

As per FTB's suggestions (and now mine), please link the version lists with reports. The only reason I have this link is Jaded was kind enough to provide it. We are not servants who will hunt for URLs in FTB Confluence on everyones behalf. VikeStep provides these for this purpose; use them.

Xyclade · Answer 9 · 2014-02-24T22:54:10.000Z

I just updated the server to Direwolf20 1.0.16 and the crash still occurs. The updated mod list is:
https://feedthebeast.atlassian.net/wiki/display/PML/Direwolf20+%281.6.x%29+1.0.16

Additional information: it looks like the problem is caused by an automated cotton farm. The automation is done with MFR and Railcraft.

I've manually solved the problem for now by mc-editing all items of id 3260:* out of the chunk file where this occurs. This confirmed the cotton is the problem.

Share to