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 wd40bomber7 wd40bomber7 May 18, 2016 at 02:08 UTC - 0 likes

    So I figured out why all of our quests were constantly being broken on server launch. Quester was loading before multiverse, and throwing away any location related data on worlds that hadn't loaded yet. By adding a soft dependency on Multiverse-Core I fixed it for our server.

  • Avatar of user_550497 user_550497 May 10, 2016 at 03:51 UTC - 0 likes

    I was playing around with the commands in Quester, and finally found a way for the sound to play. I used a command (CMD) to play them, and it works just fine. Just don't forget to set the xyz.


    /q event add 0:12 CMD playsound master @p xyz

    @p just means the nearest player by the way.

  • Avatar of wd40bomber7 wd40bomber7 May 07, 2016 at 18:04 UTC - 0 likes


    Here's a pastebin with all the information:

    Three sections in the pastebin. Section #1 is quester loading and chewing up and destroying our quest file. Section #2 is me copying the old file out of backup and replacing quests.yml with it and then issuing /q reload Section #3 is one of the quests that quester chews up and destroys (in its intact form)

  • Avatar of user_550497 user_550497 May 07, 2016 at 16:01 UTC - 0 likes

    @ragan262: Go

    Thank you for the reply. We are using 1.9.2. I tried ENTITY_HORSE_ARMOR in the command line example I listed below, sound still does not play (/q event add 0:6 sound ENTITY_HORSE_ARMOR player 100 1). I also tried the lower case version, thinking rather than being case insensitive, it was instead case sensitive.

    Case sensitive is a factor when using /playsound. If I use the upper-case version it will not work, I need to instead use the lower case version. In addition, I need to replace the underscores "_" with periods "." it is only then the sound will play with the /playsound command.

    Last edited May 07, 2016 by user_550497
  • Avatar of ragan262 ragan262 May 07, 2016 at 14:06 UTC - 0 likes

    @user_550497: Go

    If you are on 1.9 try these.

    Prior to 1.9, try these.

  • Avatar of user_550497 user_550497 May 07, 2016 at 06:31 UTC - 0 likes

    Is there any way someone could provide the correct syntax for adding in sound for an event? I tried the link in the documentation, but it seems to be down at the moment.

    I am typing:

    /q event add 0:6 sound player 100 1

    So basically, after objective 0 is completed, 6 seconds later I want it to play the horse armor sound with a volume of 100 and a pitch of 1.

    There are a few event messages that play just prior to the sound playing in sequence, and they each work just fine, down to the giving of the currency, however the sound file does not play. It is supposed to simulate the sound of a small sack of coins being placed in the player's hand (best sound I could find).

    I did try playing the sound within Bukkit itself with /playsound master @a, and it worked just fine. So, I know the sound is there, it just must be my command that is off.

    By the way, a list of sounds can be found here for those of you who are looking for them.

    Last edited May 07, 2016 by user_550497
  • Avatar of user_550497 user_550497 May 07, 2016 at 00:34 UTC - 0 likes

    @ragan262: Go

    My apologies, it was an error in my format. I was typing /q desc set &2"description message here..." As you can see, my color change I was trying to achieve at the beginning isn't correctly formatted. It should look like /q desc set "&2"description message here..."" I wanted to add in quotes so that it appears as though the NPC was talking. I didn't realize I needed to surround everything in quotes. It was just something specific I was adding into my own quest lines. I encountered the same thing in the events, and I just needed to change it. The error was on my part, not yours. Quester is a wonderful plugin ragan262, I really appreciate you making it. I may need to learn some things again, but I honestly believe it is worth it. Thank you again for all of your help, and expedient replies.

  • Avatar of ragan262 ragan262 May 06, 2016 at 22:37 UTC - 0 likes

    @user_550497: Go

    You either found a bug or are doing something wrong, as it should definitely be possible to quote description and you should in no way be forced to use specific message formatting. Use help command, that might shed some light on your issue. You can use flag "-d" at the end of help command to display complete list of command in specified branch. (Example: "/q help desc -d" or "/q help obj -d")

    I'd also like to see exactly what command you executed that produced too many arguments error. I've been using v0.7+ for quite some time now and I haven't come across the issue you are describing yet, so any details would be appreciated.

    Last edited May 06, 2016 by ragan262
  • Avatar of user_550497 user_550497 May 06, 2016 at 21:34 UTC - 0 likes

    @ragan262: Go

    I understand, but there seems to be gaps within that functionality. For instance, I am able to quote the title of a quest so that I can use spaces (ex: /q create "Quest Title") but I am unable to quote a description and use spaces (ex: /q desc set "Quest description here..."), as it returns with the error "too many arguments." I instead have to use the underscores to make the plugin recognize the statement (ex: /q desc set "Quest_description_here..."). Quester seems to lack the user-friendly functionality that it once had. I just miss that.

  • Avatar of ragan262 ragan262 May 06, 2016 at 20:33 UTC - 0 likes

    @user_550497: Go

    "New" Quester changed a lot, but mostly under the hood. As you can see, the version you were using until now was released 3 years ago, around time I completely stopped using this site to publish new releases. Many new builds have been released since then.

    There's this very old page that has been created when 0.7 was very fresh. It mentions change in command system that requires you to quote every argument that consists on multiple words. Since description is a single argument, it needs to be quoted if you want to have spaces in it.

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
Reverse relationships
Recent files