Bukkit

@ragan262:

Awesome thanks for the info.

Re: Pauses in the description -- I don't use NPCs for quest handlers, I just use CommandSigns to allow people to activate quests. You're right, though, about the pauses likely being awkward.

Really a better solution would be to have a way for people to re-read the dialog if they missed it. Currently the only way is for them to do /q quests to get the name of the quest and then do /q show <name> once they know the name of the quest.

How about if /q show just defaults to the active quest, like /q cancel does? Then I can just reply "/q show" instead of "type /q quests to get the name of your active quest and then type /q show <name_of_quest>" every time someone asks "What do I do next?"

Re: save on shutdown -- since quests can only be altered when they're toggled in 'off' mode, how about if instead of saving on shutdown it would save on /q toggle  ? Then users could edit the backend file and do /q reload to implement the changes, or they could use the in-game commands and then as soon as the quest was reactivated it would save to disk.

That said, is there any reason it can't be saved to disk as soon as someone makes a change to the config using in-game commands?

Thanks again

@ragan262:

I've tried just stopping the server, manually entering "delay: 2" into the event, and starting the server again.

With a 2 second delay the quests chain together for non-op users :)

So here's another delay question.. I have a long dialog at the start of each quest -- I'd like to be able to stick a delay in there so it doesn't all flash by super fast. I'm guessing that functionality isn't already part of Quester but for a future release would it be possible to add something like $delay_<time> to strings? So the desc could be like:

PersonA: Blah blah blah bliggity blah!\n $delay_5 PersonB: I also think blah blah!

...to achieve a 5 second delay between person A's speech and person B's speech, thus creating a natural flow of dialog that can be read at a more comfortable pace.

That possible at all? If so, is it something that would be easy enough to do that it's worthwhile? :)

Also, side note - it would be great it we could edit the config and then just do /q reload to have the config changes read into the plugin.. Not sure why, but when I try to do /q reload it overwrites the changes I've saved into the yml with the config that was there previously

@ragan262:

Thanks very much, that was actually the first thing that occurred to me when I saw that "DEL:" there but the documentation doesn't explain how to implement a delay. Can you explain that relatively easily? If not it can wait til tomo

Thanks again

@ragan262:

Yeah I'm baffled too... Quests chain together just fine for me when I attempt them as Op but when non-op users attempt them they have to manually start each quest within the chain, none of them auto-start like they do when I try as Op.

Is there an IRC chan or something I could meet you in for troubleshooting?

@ragan262:

Good call, thanks.

However I'm having a problem triggering the next quest as an event on completion. I have a quest chain set up so that when the objective in quest 2 completes it activates quest 3, when quest 3 is completed quest 4 should automatically begin, etc.

Here's my quests.yml file with the lengthy descriptions snipped.

http://pastebin.com/4BHYGZp6

When users manually do /q start (blah) they are able to start the next leg of their quest, but it doesn't start automatically as I would expect. What am I doing wrong?

Thanks

PS - Using dev version 0.6.3.4

[SOLVED] - For EpicBoss functionality with Quester you need to download the DEV build that specifies "EB Fix" in the filename.

This seems like the kind of info that would be very useful to have on the documentation page for the BOSS objective! Would save people a lot of hours of frustration!

@ragan262:

Hi, having trouble linking Quester and EpicBoss together.. I have a quest made with the only objective being to kill a specific boss type "Ogre" and I have Ogre on an EpicBossesRecoded timer to respawn 10 minutes after death.

I start the quest, travel to the ogre, and kill the ogre. It says that I killed the ogre, and then nothing else happens.

This is the only objective in my quest, so I would think that when I kill the boss it should end the quest and trigger the -3 event, but when I kill the boss all that happens is the boss dies and the respawn timer starts for the next boss spawn.

If I then do /q progress 0 it shows that my current objective is still to kill the ogre.