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.

Wiki Dev builds GitHub Old main page

Using 0.7 ? Proceed to the wiki. (currently empty :( ) Using 0.6 ? Proceed to the old main page.
(Old main page is the rightmost link.)

Need quick help? Try your luck in channel #Quester at
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 version is working with MC 1.7/1.8. See dev builds. Link broken at the moment, latest builds here.

You must login to post a comment. Don't have an account? Register to get one!

  • Avatar of Tanguy72 Tanguy72 Feb 14, 2016 at 11:15 UTC - 0 likes

    Being op or having quester.admin permission doesn't allow me to bypass conditions. It isn't really a problem for me, but maybe you'll consider it as a but, so I report it.

    Last edited Feb 14, 2016 by Tanguy72
  • Avatar of Tanguy72 Tanguy72 Feb 14, 2016 at 10:51 UTC - 0 likes

    Yes, I found that we had to put quotes yesterday, after posting my comment, so thanks for all your help, now, everything works pretty good and I'll be able to do my 40+ quests :D

  • Avatar of ragan262 ragan262 Feb 14, 2016 at 00:34 UTC - 0 likes

    @Tanguy72: Go

    About /reload: it can break quester, so I'd use it very sparingly.

    About quest names. Since 0.7, you need to quote every single command argument that has more than one word. For example:
    /q description set "This needs to be quoted"
    /q con a quest 'This is fancy quest name that is also quoted' -i

    PS: "/q con a questnot <quest>" = "/q con a quest <quest> -i"
    You can see in config that questnot conditions do not exist anymore, and are just inverted quest conditions.

  • Avatar of Tanguy72 Tanguy72 Feb 13, 2016 at 23:24 UTC - 0 likes


    Sometimes, I use the /reload command for other plugins who haven't got it, I never use it for quester itsellf. I said you that I used only commands, so that I can't modify active quest and I know the /q toggle command. For your "last thing": I can't use name for questnot: If I type /q condition add questnot Ou suis-je? I've got this in the /q info: Conditions: [0] QUEST: Ou (-i) The questnot command doesn't take the entire name of the quest. EDIT: I did /q condition add questnot "Ou suis-je?" and it works perfectly now!!! thank you for all your help, and to be so present to answer at questions like that!!!

    Last edited Feb 13, 2016 by Tanguy72
  • Avatar of ragan262 ragan262 Feb 13, 2016 at 22:17 UTC - 1 like

    @Tanguy72: Go

    First things first. NEVER do /reload. There's a quester command to reload quests. It's "/q reload -q" (it only reloads quest config).

    Secondly, never modify active quests. Whenever you are modifying quests in config, disable them first. Command to disable and enable quests is "/q toggle".

    Last thing, QUESTNOT works with quest NAME, NOT ID. I'm not sure if it used IDs in 0.6, but in 0.7, it's using names.

  • Avatar of ragan262 ragan262 Feb 13, 2016 at 22:12 UTC - 0 likes

    @Florian28600: Go

    command is

    /q obj add item 352 20 -q

    Command flags are enclosed in brackets in command help. For example: (-xyz) means there are 3 flags available 'x', 'y', and 'z'. It is possible to join them all together '-xyz', or have them separately '-x -y -z'.

  • Avatar of Florian28600 Florian28600 Feb 13, 2016 at 21:11 UTC - 0 likes

    Three questions ?

    create obj

    /q obj add item 352 20

    after /q info

    [0]ITEM:BONE[352]; AMT:20;QST:false

    QST ? It's possible to change? What command?

    Or quests.yml


    item: '352'

    amount: 20

    type: ITEM

    Last edited Feb 13, 2016 by Florian28600
  • Avatar of Tanguy72 Tanguy72 Feb 13, 2016 at 14:33 UTC - 0 likes

    @ragan262 If you don't want to read that long comment, just read that paragraph: I resolved a part of my problem by doing /q save, as you said me in my ticket. Only the questnot condition doesn't works. logs and quest here:

    Sorry to have sent a comment like that, but I was a bit hungry to have spend so much time on quests... And I must say your plugin is the only one wich correspond to what I want, so I'll have to do with it and not to rage on you, because it's only a beta test... I'll test your solutions and send you logs You must know that all problems I have where present in last version (that's why I uptaded mine) but I think all these are only one:

    When adding something to a quest, do /reload, then if you do do /info <quest id>, the thing added doesn't apear, but if you do /info without the id, the quest is how you modified it. But: during reload, the quest was reactivate, and changes wich were made doesn't works (so there is a bug when doing /q info) The quest also unselect herself. The /q save, like you wrote me in my recent ticket, works perfectly to resole objectives and location removes! Also the activation of the quest is resolved! My only last problem is the questnot condition. I must precise that I do all with commands. here my quest and my logs: You can see here that the questnot condition I have doesn't works

  • Avatar of ragan262 ragan262 Feb 12, 2016 at 19:27 UTC - 0 likes

    @Tanguy72: Go

    Enable debug mode in config and look into startup logs. Unfortunately few things changed in quester, so old files may not be 100% compatible. Flags are now also called 'modifiers', which might have caused confusion.

    If you send me your quest file and startup log with debugging enabled, I might be able to help you more. Problems you are describing are most likely caused by migration, not by new version of plugin being broken. I've been using that version for quite some time, and never encountered anything like that.

  • Avatar of Tanguy72 Tanguy72 Feb 12, 2016 at 13:58 UTC - 0 likes

    I've got a problem with the newest version: where are flags?? We can't create them but old flags are still registered in our quests. And all quests objectives seems to disapear after every server restart, after /q reload, after /reload. Conclusion: that plugin doesn't works, I can't use it while doing any reload or restart!!! Oh, and the questnot condition doesn't work

    Last edited Feb 12, 2016 by Tanguy72

How did you find Quester ?

  1. Choice:

  1. Results
  2. 11 comments


Date created
Jul 25, 2012
Last update
Jul 29, 2013
Development stage
GNU General Public License version 3 (GPLv3)
Curse link
Recent files