Skip to content
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

Water and Lava Flow outside island realm disabled? #5

Closed
AstralNomadED opened this issue Oct 28, 2020 · 8 comments
Closed

Water and Lava Flow outside island realm disabled? #5

AstralNomadED opened this issue Oct 28, 2020 · 8 comments

Comments

@AstralNomadED
Copy link

Setting up a new server and my idea was centered around the islands plugin as a core server mechanic. Couple of days into the server test phase, a bug was reported to me. It seems that water and lava work as they should no the islands, but both naturally spawning and bucket placed water and lava source blocks in the wilderness, nether, end, and any other world do not spread. The source block just sits there. Water will not regen source blocks either. I had begun to remove other plugins and data packs, check config files. Nothing seemed to fix the problem. Today, I removed the islands.jar file and loaded the server. I jumped off and died (expected), used a portal to access the nether, and now lava spreads properly in the nether at least. Any ideas?

@AstralNomadED
Copy link
Author

Just downloaded and installed the 4.5.3 update. Was still using the 4.5.0 file. Seems to fix the flow issue, but all of the islands have been unassigned.

@aleksilassila
Copy link
Owner

Thanks for reporting, I found the bug and I will patch it as soon as I get home. Looks like I reintroduced it with the restriction configuration update (IslandsListener.java:39)

Cheers

@AstralNomadED
Copy link
Author

Thanks for responding so quick. I was worried that I was going to have to make schematics of every island and reset. The 'UUID' and 'trusted' lines in the islands.yml for each island are still there and matching the info in the playerdata folder. When I log in after updating the islands.jar, typing /homes returns with 'Found 0 home(s)'. Luckily, the isSpawn still works and all the islands are physically there.

@aleksilassila
Copy link
Owner

aleksilassila commented Oct 28, 2020

Describe your second problem again; are you for example restricted from interacting with the islands when you dont have bypass permissions? What else is wrong with the islands?

Edit: Also there wasn't any changes to permissions that should cause such issues but it's better to double check your permissions too, although I doubt that was the issue. Is it only the homes that are missing?

@AstralNomadED
Copy link
Author

Sure. Updated from 4.5.0 to 4.5.3. Log on and spawn at island marked with isSpawn: true. Previously owned 3 islands myself, now showing 0 owned when I enter /homes. Also cannot /visit any islands previously owned and named by myself or others. Islands are still in the islands.yml and the islands blocks are present in the world. Can only interact with op permissions. Otherwise, even on my own island, message states that I don't have permission from the owner to interact with the island.

@AstralNomadED
Copy link
Author

It is acting in game as though islands that were created before the update are now no longer owned by anyone. However, the UUID in the islands.yml as well as the trusted ids are still listed.
Screenshot_5

@AstralNomadED
Copy link
Author

/homes = Found 0 homes(s).
/home = [Error] 404 - Home not found :(
/visit welcome = 'An internal error occurred while attempting to perform this command' - This island was/is owned by me

@aleksilassila
Copy link
Owner

aleksilassila commented Oct 28, 2020

Was due to islands.yml containing old values from earlier plugin versions, the issue is now resolved. Flow issue is now patched.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants