Home
#Welcome to the Regios wiki!
Regios, originally developed by Adamki11s and currently being developed by johnnyzerox7, is a highly advanced and customisable region plugin similar to WorldGuard or Residence, yet different in many ways. Regios provides the core features most servers are looking for such as protection with exceptions and whitelist/blacklist modes. However Regios does not just stop there; Regios offers many more advanced and cool features such as custom health regeneration, automated lightning strikes, custom speed vector manipulation, permission node manipulation, entry and exit control, password protection and much, much more! Regios is multi-world compatible!
##Donate
If you enjoy this plugin then please consider a donation! I do this for free to help the community and as a hobby. All donations are much appreciated!
##Commands & Permission Nodes
###Other
Convert a region into a plot. This command will protect the Region, expand it from bedrock to world max height and put it up for sale under the default price in the configuration files.
/regios plot <Region> [regios.data.plot]
Authorize yourself to enter/exit a password protected Region.
/regios auth <Password>
Get basic information about a Region.
/regios info <Region> [regios.data.info]
-- ##How do permissions work?
Regios currently supports all permissions systems supported by Vault. If Vault is not found then command execution will be decided on whether the player has the Bukkit Permissions node or is an OP on the server. An OP can access all commands regardless of permission nodes, OP will be the final fallback if no permissions are found.
###Groups
There is also a hierarchy within Regios which you need to be aware of. There are 4 main groups.
- Overriders (OP usually)
- Owners
- Sub Owners
- Exceptions
- Players
When trying to edit Region properties the player must be in group 1 - 3, players in group 3 can not modify what are classified as 'main' settings which include protection and entry control.
Tiers inherit each other.
EG, 1: A Player who is in group 2 (Owner) will have the same permissions/rights as players in groups 3, 4 & 5 + the permissions/rights or group 2.
EG, 2: An OP will be in group 1 (Overriders) and so will have the permissions of all groups (1, 2, 3, 4 & 5)
1) Anyone in the Override group will satisfy one or more of the following criteria:
- They are an OP.
- They have the permissions node: regios.override.all
- They have the permissions node: regios.override.regionname
- They are the owner of the region.
- They are the sub owner of a region (Cannot modify 'main' settings)
2) Anyone in the Owners group will satisfy one or more of the following criteria:
- They are in Group 1
- They are the owner of a Region
3) Anyone in the Sub Owners group will satisfy one or more of the following criteria:
- They are in Group 1 or 2
- They are the sub-owner of a Region
4) Anyone in the Owners group will satisfy one or more of the following criteria:
- They are in Group 1, 2 or 3
- They are an exception for the region.
5) Anyone in the Players group will satisfy one or more of the following criteria:
- They are in Group 1, 2, 3 or 4
- Default
###Override Nodes
These nodes will allow any player with them to bypass region protection and to edit region properties freely.
These nodes are as follows:
- regios.override.regionname- Region Specific
- regios.override.all- Applies to all Regions
###Bypass Nodes
Along with the override nodes there are also bypass nodes (Same format, override replaced by bypass) which will not allow players to edit Region properties but to bypass protection such as chest & door locking, block protection, entry/exit control etc.
The nodes are as follows:
- regios.bypass.regionname- Region Specific
- regios.bypass.all- Applies to all Regions