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.
@Florian28600
About qst:false: It is most likely related to comment #2571.
About command error: It would be nice if you provided console output as well.
@ragan262
Thanks
/q con add item 1
Failed to create element, check console for more info
@Tanguy72
Je pense que tu es français pour faire 2 quĂȘtes en meme temps c'est possible Il faut que tu modifie le fichier de config
max-ammount: 1
Ensuite dl la version 0.7 de quester qui corrige des bug que j'ai eu avec les autres version (voir mes commentaires dans les autres pages) le lien est dans le message de ragan #2573 en page 2 des commentaires
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.
It is possible to do two quest at a time? I mean, without doing the /q switch command? Because It would be very cool, a player could do a quest wich request to kill spider without having to do the /q switch command :)
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
@Tanguy72
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.
@ragan262
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!!!
@Tanguy72
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.
@Florian28600
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'.
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
'0':
item: '352'
amount: 20
type: ITEM
@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: http://pastebin.com/auNzUFPU
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: http://pastebin.com/auNzUFPU You can see here that the questnot condition I have doesn't works
@Tanguy72
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.
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
@ragan262
Thanks you
The new version need to recreate all Sign Quests (all desactivated)
Good Day
@Florian28600
Edit: After reading your comment again, I think you are saying that shift clicking sings does not give you multiple quests. It is working correctly in 0.7 version of the plugin. You can download it here.
Here's the old reply, I will leave it here since someone might find it useful:
I can't say I understand what you are trying to say, but I will try to explain how having multiple quests at once works.
max-amount setting determines how many quests you can start at once. Let's say you have one to collect wood, and one to collect stone. Let's say one npc has both quests.
So max-amount only tells you how many quests you can start at once, not how many quests can be active at once. You can only have one active quest at a time and you can change which one of your quests is active at any time. I hope this explains how multiple quests in quester work.
I have problem
It's Ok with the NPC no with the sign "If you want to have more quests at once, hold shift while accepting the quest. If you want to prevent this, just do max-ammount: 1" .
First Exemple First quest selected with NPC Ok Second quest selected with NPC Ok or the Sign Nok
Second Exemple First quest selected with Sign Ok Second quest selected with NPC Nok or the Sign Nok
For me max-ammount: 5
I'm Sorry I'm French
Jan 16, 2016 at 10:42 - 0 likes
Hello
We can do the quests one by one
Even putting the value 5 that does not work
quests: max-amount: 5 ======
@Locorunner21
You might not know about quest item functionality in quester 0.7.
Every item that has Quest Item as the first or the last line of the lore is considered special quest item by quester. (color is ignored) These items can't be dropped and are persisted when player dies.
Item objective can only accept quest items if you add flag -q to creation command, or add questitem: true into configuration of that objective.
Similarly, item event can add or remove quest items if you add flag -q to creation command, or add quest: true into configuration of that objective.
If you want to be able to create more fancy items or mobs, you can use quester extras plugin. You will find small documentation inside its jar.
You can get whole package here: https://copy.com/cnAAHbBH64uyi9Yi
@Locorunner21
I agree with you, it would be very useful thing.
Custom Lore
Probably mentioned already, but this would be a very handy feature. I could probably create an ugly work-around for this but would prefer not to. Do you think, perhaps, you could implement a custom objective/event item. Even if the item it looks for is just the "custom" name. All the extra lines of lore could be ignored.
For example: in the file I had a look at how the items are recorded, and it is simply 'item: #' would it be such a stretch for the item to instead look for the title and not the id? Like, if you needed a piece of dirt, I could just rename an apple to "Dirt" and it would work the same. This could be harmless for non-lore servers but also a huge advantage to those of us that use lore. (I'm using Supavitax' ItemLoreStats plugin, but the way)
If this could be planned for your next update, I would tip my hat to you and get this plugin cranking all the way.
@Scratchy741
Thanks you
@mcat95
Well, you can, but can only recognize if it's bone or paper - for example. Not two papers with different names (AFAIK).