-
-
Notifications
You must be signed in to change notification settings - Fork 32
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
Level Calculations Not Working Properly #196
Comments
That is weird. There appear to be no blocks on your island, at all. Please do |
Also, do |
Also thought id mention that my end portal doesn't work either for some reason, however im not sure if that is because im running the game on version 1.16.3. I'm fairly sure the island leveling issue isn't due to my Minecraft version however, as it was working perfectly fine a few days ago or so. This is the commands you asked me to type in text form from my console btw:
|
The problem is that your protection range is zero, i.e., the size of your island is 0. It looks like your island distance is 400, so check your config.yml and set the protection range to something like 50 or 100. You'll need to reset your island or use the admin range set command to fix the current island. By the way, with a protection range of zero I'm surprised that any of your players can do anything on their island because the default is for areas outside islands to have no access. If you had to set the global protection settings to allowed for everything, then you'll want to reset those back otherwise players will be building outside their islands. |
For the end portal, make sure that you have the end enabled in bukkit.yml:
The same goes for nether portals - make sure the nether is enabled in server.properties. |
Ah i see. I was trying to limit the protection range as much as possible as I was afraid a protection range would deny players access to build on someone elses island. I am assuming this is not the case, however? And for the end portal, I have that setting enabled, I also looked at my other plugins to see if the end was disabled in any of those, however ive had no luck. Any other potential suggestions? Thank you in advance for any more help you're able to provide, it is very much appreciated! |
That's a rounding error and unfortunately, not really fixable. The way the zeroing works is that it is done on whole levels only so in your case the island has 53 extra blocks just over 100 block count.
Yes, this is definitely the case. The protection range defines the player (or team's) exclusive island space. The default is that visitors or other players cannot build on someone else's island. Usually, players have to become part of the team to do that otherwise you will suffer from loads of player complaints about griefing. If you do want to enable free for all then you can set the default island settings to allow visitor access (rank 0) for all the various protections using |
BTW, I would recommend setting Level just to calculate the Overworld. It's very CPU intensive to do 3 worlds. |
Hello! So recently I started building a server using the BentoBox BSkyblock plugin. So far, everything has worked great! However, I have had one persisting issue that I realized maybe somebody on here could help me resolve. The island leveling system is bugging out on my server, to the point where regardless what block I place, whatever value it may be, it doesn't get calculated into the island level. When performing "/is level", it constantly tells me my island level is 0. I have tried changing block values, along with doing a fairly thorough check of my config files for any errors. The odd part is that the error is only with the leveling addon, and what makes it even more unique is that the leveling commands work, its just the calculation part that isnt working properly. The only other plugin I thought could potentially be causing errors is GriefPrevention, but I wasnt exactly sure as the internet didn't have much info on this issue. Thank you in advance for any help you can provide!
I tried typing in /bsb level (name) in the console, however the report didn't seem to help much. Here is the report:
The text was updated successfully, but these errors were encountered: