-
-
Notifications
You must be signed in to change notification settings - Fork 133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Island coordinates load/save offset #1105
Comments
The offset settings are not well tested so I can imagine it's a bug. Mostly there are never used, maybe never so that's probably why we haven't seen any issues so far. I'll try and replicate the issue. |
I've replicated this. Now I need to find out why it's happening. |
Thanks for your effort so far, i really hope you will find out why. |
I've fixed it. Just running the tests now... |
Can confirm commit#90ad75baa94c7b1dcfc68c1316bb9bd60def82f8 seems to have it fixed, tested with 1.11b1567. |
Island coordinates load/save offset
Island coordinates switching on each server restart
Steps to reproduce the behavior
Our test island will be 50x50 of size, in range from [0|0] to [50|50], without a single block space inbetween isles. Anyway to reproduce, it could be any island in this grid.
The config options (i assume as relevant) look like (i assume as correct for this grid):
Since this is only about loading / saving existing isles, i assume any new island generation relation is off topic here.
So out test island looks like this:
Expected behavior
After first server startup, we check the protection area of the isle for this player.
If you use the JSON above, it's the offline UUID for name
Michel_0
. If your testserver is in online mode, you'll need to change the UUID above to yours or my online UUID... i guess you understand.It simply can be checked by the console command
bsbadmin info Michel_0
.Output will be (at least for me):
As it is correct and i "expect to be always like that". But it isn't.
Stop the server and you'll see the JSON has been changed.
It contains now [25|25] as center coordinate.
So start the server again and run
bsbadmin info Michel_0
again.It's now (at least for me):
Which is wrong. Now stop the server and you'll see the center coordinates has been changed back to [0|0]. So start the server again and run
bsbadmin info Michel_0
and you'll see it's correct again.Stop it, JSON changes, start it, it's wrong, stop it, JSON changes, start it, it's correct.... infinite.
Each second start will be with incorrect coordinates.
If i didn't miss something obvious, i would say it's a major bug, since it's about island protection and you can't expect server owners to restart a server twice on each restart, can you?
Screenshots and videos (Optional)
No screenshots necessary i guess. Console output has been posted as text above (i don't like screenshots from console, prefer text directly).
Environment
BentoBox Version (Mandatory)
Plugins (Optional)
Additional context (Optional)
Nope.
The text was updated successfully, but these errors were encountered: