Quester

Quester is highly customizable plugin handling all kinds of quests. From simple "gather to get reward" quests, to complicated forked story-telling quests. What is even better, everything is customizable on-the-fly directly in game ! No more restarting/reloading your server every time to change something. Localizable messages, plenty of different, highly-customizable objectives, conditions, events and flags. NPC and sign support. All this together creates almost unlimited possibilities.
Found a bug? Have a suggestion? Sumbit a ticket.
Don't forget to specify Quester version you are using and label the ticket appropriately. Tickets without label will take longer to review or be ignored completely.
Latest DEV version should be working with recent minecraft versions. See dev builds.




-
View User Profile
-
Send Message
Posted Oct 31, 2013Hey, Which steps should I follow to edit a quest from config file while server is running ? Editing the quest in quests.yml then using /q reload doesn't work :/
(using CraftBukkit R2.0 + Quester 0.6.3.6)
-
View User Profile
-
Send Message
Posted Oct 30, 2013@ForsakenSpitfire
Quest 1: can be done only once
- condition QUESTNOT Quest 1
Quest 2: can be done only once, Quest 1 has to be done first
- condition QUESTNOT Quest 2
- condition QUEST Quest1
-
View User Profile
-
Send Message
Posted Oct 30, 2013How would I set it so they can only do the quest once, and they have to do said quest before doing the next quest in the holder? I also want multiple people to be able to do this quest, but each of them only once.
-
View User Profile
-
Send Message
Posted Oct 30, 2013@tremby90
Use DEATHCANCEL flag. (in 0.7 it's called modifier, so /q mod ...)
-
View User Profile
-
Send Message
Posted Oct 30, 2013hey im trying to make a thieves guild quests where once finished all of them you become a thief but before they can do that they only get temp picklock.use permissions anway how do i make it so if the player dies the quest gets canceled ?
-
View User Profile
-
Send Message
Posted Oct 28, 2013@NemesisMate
Quester disables all quests that are changed on startup, but it still has to load profiles afterwards, to find out that they do not match. Just treat the error messages about invalid progress in profiles like "Hey, this player should not have this quest, I will cancel it for him.". If you disable the quest in game, it will get cancelled for the player before changes are made, which is not possible on startup. It's not the issue, really, it's just different handling of the same thing.
However, if it happens where it shouldn't, (quest wasn't changed or failed to save/load for no reason) then we are dealing with the real issue.
Edit: And if you are editing quests in config during the game and then just reload, you should naturally disable the ones you modified before you reload.
-
View User Profile
-
Send Message
Posted Oct 28, 2013@ragan262
Couldn't you fix that by checking changes on config reload?, so if a quest is modified it disable that quest and then do the changes?, it would prevent that kind of issues.
-
View User Profile
-
Send Message
Posted Oct 27, 2013@NemesisMate
Yes, if you want to change something in the quest in game, it needs to be deactivated, so there will be no conflicts with players on that quest. However, if you change it directly in the config, or quest fails to load properly, errors like that can pop up.
There is no API for 0.6, so you will have to make one if you need it. I can guarantee you I won't be releasing anything new in 0.6, but you are always free to fork it and actually add that event yourself. (branch "063")
-
View User Profile
-
Send Message
Posted Oct 27, 2013@ragan262
I mean on Quester code, I'm trying to integrate another plugin and do something when a quest is completed. On 0.7 I can use a QuestCompleteEvent handler (or that I think) but I want to make the same on 0.6 (I can't see any event fired on quest complete).
The issue is with that quest: http://pastebin.com/7jfmFh50. I think is that the problem comes if a step of the quest is removed and a player has it assigned but I'm only supposing.
-
View User Profile
-
Send Message
Posted Oct 27, 2013@NemesisMate
QuestCompleteEvent ? I'm not sure what you are talking about.
Anyway, is your issue caused by migrating from 0.6 to 0.7 ? Could you please send me your quest config ?
-
View User Profile
-
Send Message
Posted Oct 27, 2013@ragan262
Is there a way to have the equivalent of: 0.7 "QuestCompleteEvent" but on 0.6?. (I'm having lot of problems with 0.7 when creating new quests, trying and modifying them after trying: http://pastebin.com/LkbfgY7U, if I restart instead of reloading: http://pastebin.com/vxp5FagH).
-
View User Profile
-
Send Message
Posted Oct 26, 2013@tremby90
I did not think about custom npc names back then, so it's impossible. It is fixed in 0.7, where you can surround the name with quotes. I am not going to push another 0.6 version out, so you will either have to wait until 0.7 is out, or use development version.
-
View User Profile
-
Send Message
Posted Oct 25, 2013how do i define space like if I have an objective to kill bob cool for example how do i define the space between bob and cool without having to rename his Bob_Cool
-
View User Profile
-
Send Message
Posted Oct 25, 2013@cloud_strife_91spain
Modifier REPEATABLE is for visual purposes only. If you mark quest as repeatable, its color in quest list of the player will be adjusted accordingly. Oh and it is also present only from version 0.7. (I think)
If you want to make certain quest non-repeatable, give it questnot condition without time limit pointing to the same quest.
-
View User Profile
-
Send Message
Posted Oct 25, 2013@Ban5
Sweet, thanks for that
-
View User Profile
-
Send Message
Posted Oct 25, 2013@frol1
if using 0.7 yes, without the < > of course, the " " is for quests with more than one word.
ie;
/q condition add quest Cookies -i
/q condition add quest "Lost Treasures" -i
-
View User Profile
-
Send Message
Posted Oct 25, 2013@Ban5
So If I do /q condition quest <"quest name"> -i that mean that the player could only do that quest once right?
-
View User Profile
-
Send Message
Posted Oct 23, 2013@cloud_strife_91spain
depending on the version
0.6.x
/q condition add questnot <quest name>
0.7
/q condition add quest <"quest name"> -i
-i means inverted which conforms to the "questnot" condition from 0.6.x
that should get your stuff cleared up.
edit: sorry forgot the "add" in both examples :( v0.6.x /q condition add questnot <quest name> - v0.7 /q condition add quest <"quest name"> -i
-
View User Profile
-
Send Message
Posted Oct 23, 2013@cloud I don't know if this works but try /q condition add questnot t:-1
-
View User Profile
-
Send Message
Posted Oct 23, 2013@tremby90
Thanks but I also need to make non-repeatable missions.
in the wiki "Quester" information is erroneous and does not work the Modifier norepeteable