sorry for my anger outburst in the last topic, i can't really take criticism, but i will try to accept it gracefully this time
This is basically what the title states, Quest events! Now you can have an organized system of Quests without using VCE or some external event content. This supports features for giving your quest beginning and ending a neat little description to tell the user what they will do, and how they did in the end, and there is an objective system so the user must complete a certain number of objectives or tasks before officially completing the real quest.
Here is a reference for the events, and what they do:
OUTPUT createQuest - [QUEST NAME] [A SHORT, SIMPLE QUEST DESCRIPTION] [TOTAL NUMBER OF OBJECTIVES TO COMPLETE[]
OUTPUT completeObjective - [OBJECTIVE'S QUEST NAME] [LOCK, SO USER CANNOT ACTIVATE THIS OBJECTIVE ANYMORE]
OUTPUT endQuest - [END QUEST'S QUEST NAME] [A SHORT, SIMPLE DESCRIPTION, LIKE ON THE CREATE QUEST]
INPUT onQuestBegin - [CALLED WHEN THE USER ACCEPTS A QUEST]
INPUT onObjectiveComplete - [CALLED WHEN THE USER COMPLETES A QUEST OBJECTIVE]
INPUT onQuestEnd - [CALLED WHEN THE USER ENDS A QUEST]
I have tested this at my server, and it works just fine on my end. If you have any problems then please tell me. I haven't coded alot in a while so, yeah.
Download!