Added:
default-max-home-count
- the default max homes for everyone who doesn't have a permission set for max homes.
Permission adjustments, if you have specific permission settings, please read
Basic functionality is now enabled by default. These permissions now are set to true
by default:
homes.commands.sethome
homes.commands.delhome
homes.commands.home
homes.commands.list
homes.bed
If you want a group not to have these permissions you will need to deny these
- Fixes issue where
homes.count.<num>
was not checked on/sethome
- Makes the config automatically add new options in
- Tested on 1.21.3
Adds a cache for the homes, preventing constant SQL queries every time someone tabcompletes, runs a command etc
(that's likely all that really matters for end-users, the rest is just code stuff)
- Adds a cache for the homes, preventing constant SQL queries every time someone tabcompletes, runs a command etc
- Simplifies the safety checks and changes to a bitmask
- Refreshes the cache on sethome, delete home, and the first time someone runs a home command
- Removes the cache when someone logs off
- Simplifies command logic and condenses duplicate code
- Preparation for expansion to allow more flags
-o
-override
flags should be able to be used in any order in the command now- setting a home when you have no homes set and you do not provide a home name will now set a home with a default name instead of erroring out
- Adds teleport delay option with these config options:
delay: # Delay after running the command to teleporting
enabled: false
time-in-seconds: 5
cancel-on-move: true
buffer: 0.5
- Adds
homes.delay.bypass
permissions - Adds CONSOLE-ONLY command
importhomes
- please look at The README for information on how to use this. - Adds bed home option, with this config:
bed-home: #set a home when interacting with a bed
enabled: false
- Adds
homes.bed
permission - Adds various locale messages
Tested on 1.21.3
- Fixes vague and confusing errors when trying to access or set homes when using MySQL
- Also fixes it not working properly with MySQL
- Tested on 1.21.3
Add 'lockout' functionality. Tested on 1.21.3
Adds this section to the config.yml:
# Should people be prevented from using homes they set before their permissions were adjusted to be lower? (i.e. they
# had permission to set 5 homes before, and now they only have permission to set 3)
lockout:
enabled: false
home: true
homelist: false
deletehome: false #dunno why you'd enable this unless you want people to be completely locked out but okay
Adds this line in the locale.yml, under 'errors'
cannot-use-command: "<red>You currently have more than <dark_red><bold><value></bold></dark_red> homes. In order to use <gray><command></gray> you must first delete some homes.</red>"
Players that have homes.count.bypass
will not be affected by this setting
Initial Release