-
-
Notifications
You must be signed in to change notification settings - Fork 50
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
No tree growth #355
Comments
From the first new island, I executed /is reset (twice) to generate a completely new island. Tree growth occurred normally. |
I don't know if you've been updating your server as well, but they are fixing bugs with 1.16.1 so maybe there's some ticking issues. There's nothing we're doing to prevent tree growth so this is not really actionable right now. |
Server is 1.16.1 latest, within 1 hour of each code change. I have a monitor on the Spigot change log. Obviously, SkyBlock is unusable if one cannot grow a tree. |
This issue is easily reproducible on my up-to-date Spigot 1.16.1. It might be worth a look. |
You write:
Does this mean that even with bonemeal you cannot grow the tree? |
That is correct. After the lengthy unsuccessful waiting, I decided to test with bonemeal, just to see if the sapling would grow at all. It would not. I have replicated this sequence three times out of three attempts. |
I just saw your comment about bonemeal not working. That sounds like something is blocking growth completely. Can you do /is info for this island? |
I do not see that you followed my script, particularly the /unregister player then /island part. Plausible explanation: After that sequence, BSB believes that the player it outside protection range. I have already started a new island test, so would prefer not to go back to this. I have replicated it previously. |
I did follow your sequence. On the island with the cow pig and duck I unregistered, and did /island. If you cannot grow a tree using bonemeal on your island then yes, it's likely that the tree growth is being blocked by that setting. If you change that setting to Active and bonemeal allows it then that will confirm it. Then we need to find out why BentoBox thinks you are no longer on your island, so do /is info when on the island and look at what it says compared to your coords. Remember, if you are Op, you might be placing blocks where normal players are not allowed to place them. |
The player is OP, but I do not see that he is doing anything OP-restricted. Original island information
which creates a new island (which is unlit, per #354.
|
What is your BSkyblock island config? It looks like you have an island distance of 512? Did you change that recently? If you change the tree growth setting to Active as an experiment, can you grow the tree via bonemeal? At what location is the tree on this island? If you change the player to not be Op as an experiment can the player place blocks on the island? Finally, can you zip up the BentoBox folder (and database) and share it so I can try and replicate? |
Download of plugins/BentoBox/addons/BSkyBlock/config.yml Island distance = 512 since very early on, certainly not recently. I believe that it was set before any islands were created (and the island info -- see above -- certainly reinforces that), but I cannot guarantee it. I will try I will try |
Made PLAYER_ELIDED non-OP, then
Player executes
and many, many more similar console/log errors.
|
Do you still need the "Active" test, or did the non-OP test provide enough information? |
This looks suspicious:
What happened here? Did he try to break a block on the island? Can you do F3 and actually check where the coordinates are? Also, does this player have a range perm on him such that the island range is changing? (I assume not, but just checking). |
I would say more than suspicious -- indicative. It was the result of trying to chop a log out of the tree (as OP, I was able to chop the tree, but not as non-OP). The coordinate was 0,126,512 -- the second block from the bottom of the original tree. The in-game message was |
Why is the player at that location? 0, 126, 512? His island is at 512,120,0... oh wait - I see. Let me study this... |
Okay, a few questions:
|
You're looking at the third island. Look at the second (failing) island. |
Correct.
I have two test players.
http://blackdog.straight8.com/drops/BBox.zip |
Downloaded. |
I managed to replicate this with your database. I haven't worked out why it's happening yet, but I have an island that isn't mine but should be. It survives even after a reboot. Investigating... |
What a relief. Thanks. |
I'm a bit brain frazzled right now. I'll need to look at this tomorrow. |
No hurry at this end. I get around it easily. I just thought that you would want to figure it out, it case it goes deeper or wider. |
I found the offending database entry - it's an island file called 0d6b9b3c-a0a1-49f2-9cd4-a0d3141d3c64.json. This file must be from a long time ago because it's not prefixed with the addon name. This island file has a range of only 128 and not 256. When this file is deleted, things start working again. I think it's messing with the grid manager somehow. Anyway, I suspect it's a left-over from a previous install you did and maybe didn't get deleted? Try and remove it and let me know if it fixes the issue for you. |
Removing that file resolved the issue. As you know, I have been testing BentoBox/BSkyBlock from the first dev release. The data presentation has changed radically over time. Newer releases do not detect leftover potential problems, so it has proved very difficult to upgrade across releases (it is relatively easy to start over, of course). Obviously, a lot of the burden is (and should be) on me, since you have made it abundantly clear that change is the norm. I voluntarily decided to test dev releases, although I must say that testing by me and others has identified a large number of issues. So just saying... Thanks for taking the time and energy to identify this issue. |
@SlimeDog I am very glad that you do this, thank you! Your support is critical. |
Confirmed fixed in BBox 1.15.0-b1839 Shutting it down seems a bit harsh, but I guess it will get their attention. :) |
Problem is resolved for me as well in snapshot 1.15.0 b1846 |
Bug still persist for some players with Release 1.15.0 (https://github.com/BentoBoxWorld/BentoBox/releases/tag/1.15.0) on 1.16.2 PaperMC (latest build) |
@Baterka This bug is closed and contained multiple issues. I don't know what specifically you are referring to, so please file another. |
Description
Describe the bug
Newly planted sapling does not grow.
Steps to reproduce the behavior
Expected behavior
Environment
Output of
/bbox version
(Mandatory)For reference, Spigot Jenkins build 2827.
The text was updated successfully, but these errors were encountered: