Post by Todge on Jun 21, 2019 18:39:37 GMT -8
So, does it add in another post after a player makes a post that triggers it, or is it meant to be a scenario where an admin posts a creature hunt event thread and other players reply? Either way though, I can understand not wanting to load keys onto it
I have no issues with adding extra keys, I'm just thinking of those that want to use it and may not want to use up 4 keys on a single plugin. But, there have been suggestions that plugin keys are more available after V6 arrives, so in the future, you never know..
The plugin functions like this...
An admin creates a thread in board that is set aside for creatures to appear. During the thread creation the admin has options available, to add a creature, and if so to chose a creature group, after which post the creature should appear, and the chance that said creature does appear after that post. So, if post 3 was selected, and the chance set to 50%, then there would be a 50/50 chance of the creature appearing after every reply AFTER reply 3.. But the creature can only appear once, so once it does appear, it is open to attack by every member that posts in that thread.
Attacks are made via posting. When a member posts in a thread that a creature has appeared in, they have the option to attack or retreat. Attacking the creature can obviously cause damage to that creature, but will also open you up to receiving damage in return. Retreat and you will not cause damage to the creature, but the creature can still attack you, but with less chance of being successful.
This continues until the creature is dead, after which the thread continues as a standard thread.. No more creatures, unless the admin edits the first post and replaces the dead creature.
The plugin keeps track of users hit points, which are displayed in the ini-profiles, and a few other stats that are displayed in the users' profile pages.
Members can recover hit points, or heal, by posting in a creature thread and not receiving any damage.
There are an array of options in the plugin that are way too much to detail here, but are listed elsewhere, and everything is explained in the plugin settings pages.