akiva silver
Assigned
Reported
Comments
@Nathen Ryan
When you were testing what world generation did you use and was it single player or multiplayer.
@Guillaume Keighan
if you allocated 5 gb of ram to minecraft it should be under "JVM arguments". (edit profile > java settings)
the default text is "-Xmx1G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M"
@Guillaume Keighan
yes i know what you mean, this error could occur when the memory dumping process takes too long caused by improper memory allocation. i have had this issue myself, but as soon as i set it to the default ram allocation settings i had no issues from that.
i think it could be done with nbt explorer or mcedit. it may be possible to do it with commands but thats a i dont think is possible.
i got this issue when i messed up on my ram allocation. when you allocate your ram make sure you do it right.
i didnt see that bug report. ok then.
I would think they would patch it in a new pre-release. Just incase if that patch introduces a new bug
I have been having issues and it was a fresh pre-2 map, i first noticed when i went into the nether. blazes did not spawn and i was on my way to the end.
Ahh that makes sense. Well that's good to know.
I found this issue in multiplayer, amplified generation. Since I did some reading on animal spawning, animals should eventually replenish overtime. In my case they went spawning, its possible that because the world was created in pre2 it may affect but I wouldn't think so.