-
-
Notifications
You must be signed in to change notification settings - Fork 140
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
Permissions to use different island schematics #104
Labels
Status: Duplicate
Related to an existing issue.
Type: Enhancement
Improvement or modification which is usually a new feature.
Comments
That is possible by adding the required permission to the schematic section of the island in config.yml. |
Oh, sorry this is a bskyblock request. Yes, it's not available yet. |
tastybento
added
the
Type: Enhancement
Improvement or modification which is usually a new feature.
label
Oct 27, 2017
Closing for #378. |
tastybento
added a commit
that referenced
this issue
Dec 24, 2018
This will load all schems in an add-on's schem folder if it exists and associate them with this world set (overworld, nether and end). Schems can be named anything, but the partner nether or end worlds must be pre-fixed with "nether-" or "end-" in the filename. Additional schems can be added by the admin into the schem folder, or they can be stored in the jar file of the add-on. Both are supported. No changes are required to current add-ons. I.e., there is no API breakage here, but I would like to rename the SchemsManager method loadIslands(World world) to be loadSchems(World world) in the future. Related issues/PR: #104 #207 #378 #408
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Status: Duplicate
Related to an existing issue.
Type: Enhancement
Improvement or modification which is usually a new feature.
Depending on what permissions a player has, they get a different island when they type /island for the first time. Maybe the permission has to do with the name of the schematic put in the schematics folder
The text was updated successfully, but these errors were encountered: