Update Plot System

pietru 2025-03-01 23:18:46 +01:00
parent 7e215cce74
commit bcfe75dcd3

@ -13,6 +13,7 @@ Zones can have parent, if zone has defined parent zone it will take permissions
Regions priority defines which zone is more important. \ Regions priority defines which zone is more important. \
Zones are first sorted based on which area has bigger priority, and after that based on which has smaller size. Zones are first sorted based on which area has bigger priority, and after that based on which has smaller size.
### Area config file
Area json file can contain: Area json file can contain:
- `enabled` - is area enabled, turned on - default true. - `enabled` - is area enabled, turned on - default true.
- `protect` - is area protected from deletion and etc - default false. - `protect` - is area protected from deletion and etc - default false.
@ -36,3 +37,12 @@ Area json file can contain:
- `pvp` - can players damage players, turned on - default false. - `pvp` - can players damage players, turned on - default false.
- `pve` - can players be damaged by enemies, turned on - default true. - `pve` - can players be damaged by enemies, turned on - default true.
- `laser_damage` - can lasers damage players, turned on - default true. - `laser_damage` - can lasers damage players, turned on - default true.
Those options are ones that are available at moment of writing this wiki page.
### Area Player Perms
Player Area Perm file needs to have `player_id` value which is unique player identifier, each area should have example player perms generated.
Player Area Perm file can also have `type` defined, setting it to `owner` makes somebody owner of that area giving them permissions to modify other people permissions inside area.
> **Note**
> Even throu example player perms might generate with all perms, only ones that will work at this point in time are `place`, `break`, `interact`, `laser` and `enter`.