You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
place townhall outside in the wilderness outside, and if there is an issue it tells me without crashing
Actual behaviour
I have implemented 20 chunks padding between colonies, I think that's part of the problem and the minecolonies is tripping out and doesn't know how to tell the player that they are too close to the other colony. The whereami command says they are 355 blocks away from nearest colony, which is just shy over 20 chunks.
Steps to reproduce the problem
They crafted a supply camp and placed it down and then tried to place the townhall block. Before they rage quitted they reported that it would say something about being inside of another colony, which makes me think it has something to do with range and minecolonies code not handling that properly.
really interesting you don't ask for a crash report:
Minecolonies version
Version: 1.12.2-0.10.234-ALPHA
Expected behavior
place townhall outside in the wilderness outside, and if there is an issue it tells me without crashing
Actual behaviour
I have implemented 20 chunks padding between colonies, I think that's part of the problem and the minecolonies is tripping out and doesn't know how to tell the player that they are too close to the other colony. The whereami command says they are 355 blocks away from nearest colony, which is just shy over 20 chunks.
Steps to reproduce the problem
They crafted a supply camp and placed it down and then tried to place the townhall block. Before they rage quitted they reported that it would say something about being inside of another colony, which makes me think it has something to do with range and minecolonies code not handling that properly.
really interesting you don't ask for a crash report:
Crash Report
https://paste.lucko.me/twE2wiot6f
Minecolonies Config
http://paste.ubuntu.com/p/8dRpNGjQzr/
The text was updated successfully, but these errors were encountered: