Dog, on 11 September 2014 - 06:08 AM, said:
I've seen that same problem on Cranium's 1.7.10 beta server. So far I've only been able to reliably replicate the problem on Cranium's beta server (not on my test server); so I've hesitated to file a bug report without more information to provide.
my understanding is that it's a known error and will be fixed, but in the meantime I dont know how to handle it without using chunkloaders which will eat up a LOT of resources considering how many persistent chunks I'll be dealing with... I mean, yes, it will work, and if I have to I'll deal with it for now, but I was hoping there was another solution...