(3.0.0 - 3.25.6) 2.1.2 (3.0.0 - 3.25.6) 2.1.1 (3.0.0 - 3.25.6) 2.1.0 (3.0.0 - 3.25.6) 2.0.0 (3.0.0 - 3.25.6) 1.1.3 (3.0.0 - 3.25.6) 1.1.1 (3.0.0 - 3.25.6) 1.1.0 (3.0.0 - 3.25.6) 1.0.9 (3.0.0-ALPHA10 - 3.25.6) 1.0.8 (3.0.0-ALPHA10 - 3.25.6) 1.0.7 (3.0.0-ALPHA10 - 3.0.0-ALPHA11) 1.0.4-11 (3.0.0-ALPHA10 - 3.0.0-ALPHA11) 1.0.2-11 (3.0.0-ALPHA10 - 3.0.0-ALPHA11) 1.0.0-11
Create a festival with this custom area events plugin for Pocketmine Server ALPHA10+:
Please use the latest version 1.0.2-11 wich has some important bugs squashed and 2 new cool features: fast toggle flags command + new barrier flag
issues @ github and/or reviews @ poggit
Credits for most area protection code go to iProtector creator LDX-MCPE and all other iProtector devs.
Standard Plugin installation; Upload .phar file (or .zip if you have latest devtools installed), restart the server, go to folder plugins/Festival;
Edit config.yml; set the defaults for any area and the defaults for area's in specified worlds.
first select position 1, then select position2, the endpoints of the longest diagonal in the area
/fe pos1
/fe pos2
/fe create <AREANAME>
/fe flag(f) <AREANAME> <god/build/touch/msg/barrier> <true/false>
/fe <god/build/touch/msg/barrier> <AREANAME> (<true/false>)
/fe here
/fe list
/fe tp <AREANAME>
/fe desc <AREANAME> <DESCRIPTION>
/fe whitelist <AREANAME> <add/list/remove(del,delete)> <PLAYERNAME>
/fe delete(del,remove) <AREANAME>
/fe command <AREANAME> <add/list/edit/event*/del> <COMMANDID> <COMMANDSTRING/enter*/leave*/center*>
To add a command you need at least;
- an areaname,
- an unique id for the command
- make sure the command works! (when you are op).
/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 the new command to
the given eventtype: i.e. /fe command <areaname> center <commandid> <commandstring>
/fe command <AREANAME> list
/fe command <AREANAME> edit <COMMANDID> <COMMANDSTRING>
/fe command <AREANAME> event <COMMANDID> <enter/center/leave>
/fe command <AREANAME> del <COMMANDID>
The Festival plugin is in active development.
20 2 2018
- info/readme update
- barrier flag
- area act as barrier when flag is true
- whitelisted and ops allowed
- short commands for flags
- f for flag: /fe f <AREANAME> <flag> <true/false>
- fast toggle: /fe <touch/edit/god/msg/barrier> <AREANAME>
13 2 2018
- Pre-release
- version 1.0.0-11
- submitted plugin to Poggit
- Festival area setup and protection based on iprotector
- area enter, leave en center event detection/messages
- area object extended with commandlist and eventlist
- Commands to add custom events
- add multiple commandstrings with id attachted to enter, leave or center area event
- list area extended info and manage event commands
[x] area protection and flag management is stable (core iProtector, 9876ca3 Dec 2017)
[x] Area messages and msg/description management are stable
[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
[x] Submit to poggit
[x] Testing expected possibilities; use as portals and shields, design a minigame park, create a quest/parcour..
[x] Barrier flag; turning the area into a barrier, no one in, no one out.
[ ] iProtector area tranformer method - using or copying iProtector areas for Festival events
[ ] More area event types
[ ] Develop a method to sync/log other plugins/Multiplayer/Timeline/Story/Minigame attachted events in given areas
[ ] Add UI Panel - Help with creating a nice UI panel would be really cool!
If you like to help improve this plugin;
or send an email to msg @ genboy.net
Thank you in advance!
The area code derives from the iProctector plugin. All credits for the area creation and protection code go to the iProtector creator LDX-MCPE and other iProtector devs.
In a first fork from poggit-orphanage 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.