Bukkit

@Dopplizzle

Selection is assigned to a player. Quester is using console to execute commands, which is not a valid sender.

@MrSheepSheep

What feature ? Group questing ? Yes, it will be added eventually.

@Babibab

I'm not sure how I'm supposed to handle that. There's just too much that would need to be added to support all WE operations. I guess I could add command event that would execute commands as fake OP player somewhere in the world. It would need some investigation, though.

@willkiller1234

1. Yes, there are few special location arguments mentioned in the documentation.
here - takes your current location
block - takes the location of the block you are looking at
player - takes the location of the player at the moment of execution (usable with events)

There is also one special argument for world name
this - takes the world you are currently in (e.g. 100;70;250;this)

2. No, there is no group system yet, but is planned.

@TheDavroar

It does not say it is outdated, it says the it matches version 0.6.2. That does not mean it changed since then. QuestHolders should really work as described in the documentation. And I think spotlight by Hmmcrunchy is accurate as well. You can rely on the documentation even if it says it matches slightly older version, unless you use 0.7 alpha. If you use 0.7, there is no proper documentation other than 0.7alpha page and comments on that page, some things work as before, some do not.

It may appear that documentation is lacking, and I'm sorry about that. I'm still working on new version and once I have done that, I'll populate wiki with proper (I hope) documentation.

@willkiller1234

No, probably not. I didn't expect it to be very important, you can remove old one and create new. I might add it if people request it, though.

@TheDavroar

http://dev.bukkit.org/bukkit-plugins/quester/pages/documentation/

Look at QuestHolder and NPCs and Signs.

Edit: This system is somewhat lacking and will be reworked very soon.

@ceoepts

API for that is only in 0.7 and is still in development, so it may change. But basically like that. Then you need to register your class in quester by doing:

Quester plugin = you know what goes here;
plugin.getElementManager().register(ExampleCondition.class);

You can look up the rest on github, since documentation is not present yet.

Edit: Sorry, I failed a little there, "key.getString("amount", null)" in load method should be "key.getString("prefix", null)". Pardon any mistakes you find, I was writing it right in pastebin window.

@ceoepts

Here's the text from faq:
'Most probably because you are OP or you have quester.admin perm. It that case, you bypass all conditions. It is possible to check if conditions are met by using "/q show questname". Conditions that are met are green.'

Is that your case ?