-
-
Notifications
You must be signed in to change notification settings - Fork 8
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
Border Reset issues #144
Comments
This bug was fixed in later versions of BentoBox. The range wasn't benign set correctly when using upgrades. |
We can't use newer versions of Bentobox due to our server version - is this is a bentobox issue then? Can we update aoneblock to fix it? |
Can you share the output of /box version, so I can see exactly what you are running? |
Any updates? Still having this issue and when players upgrade island with ob upgrade they can't actually build in the range given. |
If you cannot update BentoBox, then you need to use an older version of Upgrades that doesn't use the latest API, which would be build 138. (See BentoBoxWorld/Upgrades#59). Unfortunately, I don't have time to back-port fixes to older versions, so this is the best workaround right now. Bugs are always being fixed, but I only have the bandwidth to make them work on the latest versions of MC, Paper, etc. |
I appreciate it, I'll check and see if this works as a solution and if so that's good enough for me! |
Expected behavior
When you reset borders it should change the protection to 20.
Observed/Actual behavior
Reseting borders is not making it 20 it's making it 45 for some reason however it places the border AT 20. When players attempt to push their island back out to the range through upgrades the border will not push out as far as it is supposed to meaning they don't have access to their max island size (there is about 25 blocks they can't push it.)
Steps/models to reproduce
Have players fully upgrade islands using ob upgrade, reset island range.
BentoBox version
2.7.0
Plugin list
No response
Other
The text was updated successfully, but these errors were encountered: