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
Upon further investigation, this seems to happen every time a tree spans more than one chunk - I haven't seen any trees which have successfully generated blocks in more than one chunk. Here's an example:
I wonder if this is because the side chunks aren't loaded when it tries to set the blocks, and so the setting of blocks is silently ignored (a problem which was discussed on Discord some time ago)?
The text was updated successfully, but these errors were encountered:
This is fixed for the trees that MR currently generates by the latest commit in #38 which adds a border. Larger trees will still be broken, but making it work with trees of arbitrary sizes will take a lot of work and a lot of things will need to be figured out, so that's on hold for now.
Upon further investigation, this seems to happen every time a tree spans more than one chunk - I haven't seen any trees which have successfully generated blocks in more than one chunk. Here's an example:
I wonder if this is because the side chunks aren't loaded when it tries to set the blocks, and so the setting of blocks is silently ignored (a problem which was discussed on Discord some time ago)?
The text was updated successfully, but these errors were encountered: