Update Notes
Update notes:
==============================================================================================
SQL is now using prepaired statements and not raw sql this should help protect the database a bit.
Bukkit permissions support added See permissions table for details.
Regions are now stored in the server and are only reloaded from the database when a change is made to them
this cuts down on the number of SQL commands needed.
Entering and exiting regions messages have been added.
Pugin events table is now included in the docs
Removed a debug message from the code (less spam in the logs)
Added support for region names (via the nameregion command)
added support for multiworld, if you have an older version and updating to current please see the
"how to update SQL" doc
==============================================================================================
Docs
//////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
What are regions?
==============================================================================================
Regions are area of land protected by the system (even blocks that dont have an owner), this allows a region to be setup and then
shared to a list of players that can work inside of the region.
//example:
Red rock is a build a player has been working on that looks nice not wanting other players to mess the area around it up
a member of staff sets the area around it to a region, after doing so the staff member adds the player whos build it is to
the region so they can continue to work on it.
Player G enters the region where red rock is protected, without being op he/she can no longer cover the build in water/lava or just
cover it up with sand and stone.
==============================================================================================
Creating a region
==============================================================================================
To create a region a member of staff with permissions stands in the middle of the build (or as close to as they can)
and types
/addregion 10
this creates a 10 by 10 box around the build that is now protected, then the staff member add the player to the region
/addplayertoregion exampleplayername
now exampleplayername can continue to work on thier build without the risk of it being messed up while they are offline
==============================================================================================
Naming / Renaming a region
==============================================================================================
once you have created a region you can change the name of the region
/nameregion newname
if you have permission to the command the region will now be named
==============================================================================================
Finding the history of a block
==============================================================================================
a member of staff can right click on a block with a (Default:stick:280) in their hand to get who placed the block,
and region id/name it is in.
example:
X:241 Y:252 Z:642
Type: 1
Owner: Evildude21
Region: 1 / Example region
to get the owner of water / lava they can use [Lockedchest].
==============================================================================================
How to update SQL
==================================================================================================================================
Method A (Easy but loses all data):
1: Drop all tables
2: import the new SQL structure.
Method B (Harder but keeps all data):
1: upload and run the "update.3.3.sql" file on your SQL server
2: run the following commands swaping out [WORLDNAME] for the name of your world
UPDATE blocks SET worldname='[WORLDNAME]' WHERE id != '-1';
UPDATE regions SET worldname='[WORLDNAME]' WHERE id != '-1';
example [WORLDNAME] would be smmp
- Method b notes:
Any blocks or regions in the nether or other worlds would be usless as they are now counted as being in
the main world unless you go and edit the database to correct this (could take a long time)
==================================================================================================================================
Events table
==============================================================================================
Event | Level | Can stop the event
--------------------------------------------------------
PLAYER_INTERACT | Lowest | Yes
BLOCK_PLACE | High | Yes
BLOCK_BREAK | High | Yes
PLAYER_BUCKET_EMPTY | High | Yes
PLAYER_MOVE | Monitior | No
==============================================================================================
Permissions table
===========================================================================================================
Permission | Description | Default
-----------------------------------------------------------------------------------------------------------
vortexprotect.* | Full access to all vortexprotect commands | false
vortexprotect.removeplayerfromregion | Allows player to remove a player from a region | OP
vortexprotect.addplayertoregion | Allows player to add a player to a region | OP
vortexprotect.removeregion | Allows player to remove a region | OP
vortexprotect.addregion | Allows player to create a region | OP
vortexprotect.gethistory | Allows player to get the history of a block | OP
vortexprotect.nameregion | Allows player to name/rename a region | OP
===========================================================================================================
//////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
Comments