Merge pull request #3 from genboy/refinements

Refinements up to PMMP alpha 11

README.md

@@ -23,7 +23,7 @@ The Festival plugin: manage and run commmands on specific events attachted to a
 
 /fe create AREANAME  
 
-/fe flag AREANAME god/build/touch/msg
+/fe flag AREANAME god/build/touch/msg set true/false
 
 /fe here
 
@@ -40,48 +40,69 @@ The Festival plugin: manage and run commmands on specific events attachted to a
 
 
 #### Extended area features
+command to attach commands to an area
 
 /fe command AREANAME add(1)/list/edit/event(2)/del COMMANDID COMMANDSTRING/enter/leave/center 
 
-(1) 'add' is the default for attaching a command on the 'enter' event. Using 'enter', 'center' or 'leave' instead of 'add' attaches a new command to the given eventtype: /fe command <areaname> center <commandid> <commandstring>
+To add an command you need at least an areaname, an unique id for the command and make sure the command works! (when you're an op).
 
-(2) Change the event type for a command: /fe command <areaname> event <commandid> <enter/center/leave>
+Usage:
+
+	add a command on area enter:
 
+		/fe command AREANAME <add> COMMANDID COMMANDSTRING
 
+		'add' is the default for attaching a command on the 'enter' event. 
+		Using 'enter', 'center' or 'leave' instead of 'add' attaches a new command to 
+		the eventtype: i.e. /fe command <areaname> center <commandid> <commandstring>
 
-sum up:
-
-/fe <pos1/pos2/create/list/here/tp/desc/flag/delete/whitelist/command> <areaname> <add/enter/leave/center/list/event/edit/del> <cmdid> <cmdstr/enter/leave/center>
-
+	edit a command:
+
+		/fe command AREANAME <edit> COMMANDID COMMANDSTRING
+
+	change command event:
+
+		/fe command AREANAME <edit> COMMANDID <enter/center/leave>
+		
+	remove command from area:
+
+		/fe command AREANAME <del> COMMANDID
 
 
 
 
 ## In progress
 
 The plugin is in active development; 
-1. [x] area protection and flag management is stable (core code from [iProtector](https://github.com/poggit-orphanage/iProtector) Latest commit [9876ca3](https://github.com/poggit-orphanage/iProtector/commit/9876ca3acd48830599b3715346a1cf8ac964bdbd) on 11 Dec 2017) 
+  - [x] area protection and flag management is stable 
+  (core code from [iProtector](https://github.com/poggit-orphanage/iProtector) 
+  Latest commit [9876ca3](https://github.com/poggit-orphanage/iProtector/commit/9876ca3acd48830599b3715346a1cf8ac964bdbd) on 11 Dec 2017) 
 
-2. [x] Area messages and msg/description management are stable
+  - [x] Area messages and msg/description management are stable
 
-3. [x] Commands can be attachted to specific events at the area: 
+  - [x] Commands can be attachted to specific events at the area: 
   - [x] enter: on entering the area
   - [x] center: when in the center of the area
   - [x] leave: when leaving the area
-  - [ ] ?: more area event types
-
-=> Now testing the unlimited possibilities;
+  - [ ] ?: more area event types to consider
+
+  - [ ] Submit to poggit
+
+  - [ ] Gather code and concept suggestions 
+
+	=> Testing possibilities;
     - design a minigame park
     - create a quest/parcour
     - use stable wormholes
     - .. Endless right? This step will take a while :)
 
-4. [ ] Develop a structure to sync/log Multiplayer events in specific area's
+  - [ ] we can try to add an area tranformer method - using or copying iProtector area's for Festival events 
 
-5. [ ] Test with an advanced economy plugin and an external database
+  - [ ] Develop a method to sync/log other plugins/Multiplayer/Timeline/Story/Minigame attachted events in given area's
 
+
 
 ### History
 
-The area code derives from the [iProctector plugin](https://github.com/LDX-MCPE/iProtector), in a first fork from [poggit-orphanage](https://github.com/poggit-orphanage/iProtector) had the code was extending the area with enter and leave messages and lateron adding options to attach separate event-objects to an area and trigger specific events with commands. These test versons kept the core iProtector areas unchanged (to be able to use excisting area's).
-All worked well for a test plugin but the managing command with /area and /fe structure was not logical and separate event objects are only needed if the original area class should stay the same. So, for a better plugin command structure and performance the iProtector Area code was used to create the setup for hat now has become the Festival Plugin.
+The area code derives from the [iProctector plugin](https://github.com/LDX-MCPE/iProtector), in a first fork from [poggit-orphanage](https://github.com/poggit-orphanage/iProtector) the new code was extending the area with enter and leave messages and lateron also adding options to attach separate event-objects to an area and trigger specific events with commands. These test versions kept the core iProtector areas unchanged (to be able to use excisting area's).
+These first adjustments worked well being a test plugin but keeping iProtector area's while adding separate event data made me create a split command structure (wich isn't logical or handy) and separate event objects are only needed if the original area class should stay the same. So, for a better plugin command structure and performance the iProtector Area code was used to create the setup for what now has become the Festival Plugin.

plugin.yml

@@ -3,7 +3,7 @@ author: Genboy
 version: 0.0.1-10
 main: genboy\Festival\Main
 load: POSTWORLD
-api: [3.0.0-ALPHA10]
+api: [3.0.0-ALPHA10,3.0.0-ALPHA11]
 website: "https://github.com/genboy/Festival"
 commands:
   fe: