Bukkit

For all those that struggle with character limit using quester commands, there's a temporary solution - Long Commands. Quester is not related to it in any way and I never tested it, but it looks like it's worth a shot.

I am planning to include this functionality in quester. (quester commands will have this functionality by default)

@Zarkilor

If you want to see what I'm doing, you can always take a look at commits. Right now I'd like to focus on identifying and fixing bugs to make the plugin more stable, finalizing custom messages and full localization support, (there are still few things about it that require my attention) and properly implementing triggers.

I will slowly change all elements that use block/item ids to use names instead and quester on 1.8 should be fine.

Even if I added mythic mobs support now, you would need to use latest dev build on your server to use it, and even if it might not cause any issues it's not something I recommend just yet. (unless you are adventurer (bug reports are always nice (in a way))))

@Ban5

If there are any issues with loading quests, quester creates a backup. If the yaml file is invalid, it fails to load properly and it can be erased by quester next time it saves. (since no quests are loaded) Making sure yaml syntax is valid is the responsibility of the person editing the file.

What happened to your quest files? I can't think of anything else. Could it be something external? This just does not sound like a feature quester should ever need. I'd rather look into fixing the issue if the files were actually wiped by the plugin itself.

@Zarkilor

http://dev.bukkit.org/bukkit-plugins/quester/?page=2#c2281

@tremby90

Quester should automatically convert old quest files. (in most cases) If any errors pop up, submit a bug report.

@Intangir

No, I actually do not recommend using latest version on github. I do not even recommend using uuid version yet, but the one you will not even be able to use is at the point where I moved quester npc support to a different plugin that is not even on github yet. As I mentioned in the previous comment, build #5 should be the latest "stable" dev build.

Yes, I will keep supporting citizens2, I think I will probably even support some other npc library. (I am currently testing remoteentities) I will also be implementing dialogue trees at some point.
The biggest change done to npc support is probably removing the need to left click to select a quest when a holder contains only one quest available for that particular player at that time.

@Intangir

Okay, let's all calm down and realize what is actually happening.

0.6.3.6 is the latest displayed release because it is the latest release. Even though it has few bugs here and there, it is unlikely to corrupt your data in any way. With 0.7, I decided to change the code in a major way, and it may as well be released as 1.0, because there's way too many changes.

I believe you already discovered 063 branch on github, so we can move on. I am not adding anything or fixing any minor bugs in 0.6, because they might have already been fixed in 0.7 or are not even existing because code that created them no longer exists.

About the important issues, there is only single bug report on github (submitted by you) where I am still waiting for a response. I recall fixing something related to event manipulation long time ago in 0.7, and I'm not sure if it is your issue, but it might be. Just to be clear, the issue is not going to get fixed in 0.6. There are no other issues reported.

Git is slightly ahead of jenkins, because building process changed in the last few commits and there were some other major changes I want to test before I even put the dev build up. However, dev build #5 should be working well enough. I am responsible for running very similar build on one server and so far it's been working just fine.

You might think newest version is horribly broken and I don't blame you, because it is not documented at all. There is only one page I created shortly after I moved to 0.7. Most noticeable change has actually been done to commands, and it's exactly what you are having trouble with. As you can see on the page I linked above, all arguments consisting of multiple words have to be quoted. It means the command you use in your latest bug report would change from
/q create Mushroom Stew
to
/q create "Mushroom Stew" or /q create 'Mushroom Stew'
Command help is now generated which means it always contains only the newest info about all commands in the plugin at that time, so it's a very good source of information. (/q help for help, /q help -d for deep help, /q help [args] -d for partial deep help (for example /q help event -d))
Permissions changed a little bit too, you can see all permissions and their hierarchy here. It should be pretty self-explanatory, but if there are any questions, feel free to ask.
Format of the quests.yml changed a bit too, so if you are interested in creating quests directly in the quests.yml, you can find most recent documented version of the format here.
Oh, and quest flags are now called quest modifiers, (maybe not everywhere) so don't be scared if you run into those.

I apologize for a wall of text, but I felt like it was needed. If there are still any questions, ask. If the new dev version is still not working, submit a report.

@jajamic

- Yes, MythicMobs support will most likely come in form of an extension. It is still less important than few other tasks. (I know I promised to add this)
- WorldGuard support can be added. The only thing I need to know is what you mean by that.
- Yes, additional mob data will be supported along with additional item data.
- I will continue for sure. Only variable here is development pace.

Most of what you asked would just be extensions to existing feature set, I will start adding those once I am happy with the plugin core. With 0.7 I've been mostly working on better performance, robustness and extensibility.