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.
Hello there !
I've got a question for you. I try to make an objective with time but i have some problems with.
Example: Actually, the player have to do an ACTION objective on a furnace (To take out something, he need to right click on it only). But he have time for that, because if he don't click, there is a cancel event after 3 seconds. BUT, I wanted that if he click less than 3 seconds, it will not cancel the quest. Actually, even if he click at the good time, the cancel event will start.
My question is simple: Is this possible to cancel a cancel event ?
P-S: There is an option to select trigger on objective (/q obj trigger add [OBJNUMBER] <trigger1>), but what are theses triggers, the plugin didn't want to auto complete, and there is anything on the documentation.
@Pepytow
Hello,
command objective can only be completed when with admin command
/q runaction <player> <index>
where index is special keyword defined in each particular command objective.
It can be used to define objectives that are increased by something outside of quester.
For example:
You use a magical plugin and you want to make objective to cast a spell. It is normally not possible, but if you can configure runaction command to be run each time spell is cast, you can use comand objective for that.
Your comand objective would be set to index 'myspellcast' and each time your the spell is cast, command
/q runaction <caster> myspellcast
would need to be run. That would trigger objective with the same index for player who cast the spell and they would progress with their quest.
Hope this helps.
Hi !
I use this plugin for a very long time ago ! And thanks for this incredible work dood ! You are great ! I saw a new objective : 'cmd'. I think it's for the user do a command and he complete the objective. But I think it doesn't work .. I tryed with an essentials's command, and an other plugin's command, but still don't work ..
Do you have an answer for me ? 'cause it really help me if you have ! ^^
Have a great day, and may you could help me.
Ok thx !
I have see Sentry is dead, but replace by Sentinel. It's work?
@jajamic
Set use-metrics in config to false.
Hi i have this error:
[12:00:52 WARN]: Exception in thread "Craft Scheduler Thread - 549" [12:00:52 WARN]: org.apache.commons.lang.UnhandledException: Plugin Quester v1.0.1 generated an exception while executing task 111 at org.bukkit.craftbukkit.v1_10_R1.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:56) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.NoSuchMethodError: org.bukkit.Server.getOnlinePlayers()[Lorg/bukkit/entity/Player; at me.ragan262.quester.mcstats.Metrics.postPlugin(Metrics.java:335) at me.ragan262.quester.mcstats.Metrics.access$400(Metrics.java:57) at me.ragan262.quester.mcstats.Metrics$1.run(Metrics.java:223) at org.bukkit.craftbukkit.v1_10_R1.scheduler.CraftTask.run(CraftTask.java:71) at org.bukkit.craftbukkit.v1_10_R1.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:53) ... 3 more
@vivi902
Flags are simply boolean values in config. This should help http://pastebin.com/TLdVrEQh
I saw on the Quest Example page that you can create hidden objectives by using the flag -h, and that it is possible to use a variety of different flags with commands in-game. How would I set these flags up in the quest.yml file?
@Imxxboredxx
Prerequisites are separated by semicolon.
Hello, is there a way to add multiple prerequisites to an objective in the quests.yml file? I am aware it can be done in game using commands but I would prefer to do it in the file itself. Adding a space to separate the objectives (as it does in game) does not work.
@stun23
Try it and let me know.
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.
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.
Example:
/q event add 0:12 CMD playsound entity.horse.armor master @p xyz
@p just means the nearest player by the way.
@ragan262
Here's a pastebin with all the information: http://pastebin.com/qtWiHiNE
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)
@ragan262
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.
@user_550497
If you are on 1.9 try these.
Prior to 1.9, try these.
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 entity.horse.armor 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 entity.horse.armor 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.
@ragan262
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.
@user_550497
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.
@ragan262
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.