Bukkit

@sakura_blades

I don't think I understood what you meant. Could you clarify? There is no "questers" file, and placing everything in a single file would be really challenging to read - some more complicated conversations can take hundreds of lines.

Also, you cannot write conditions like that, they have to be set in one line:

conditions:
      tag: !wood_started

I am planning to create a web-based editor, which will make it significantly easier to write quests. This will however take much time, as I have to do a lot of stuff in the plugin before.

@ZanDezaX

Not a problem ^^

@sakura_blades

Yes, take a look at "delay" objective :)

@ZanDezaX

Cloud you zip your config files and send them to me via PM? I'll try to figure out what's wrong.

@ZanDezaX

If it's not displaying any message at all, then check in your npcs.yml if it's written like the first one:

4: 'innkeeper'
'4': innkeeper

The second one won't work, I don't remember why. If the /q reload command won't update NPCs, then reload/restart the server. I will fix those issues in 1.6, so both syntaxes will be accepted and /q reload will reload conversations.

1.6 should be out by the end of the week, maybe few days later, depending of how much time I will have.

@sakura_blades

Unfortunately there is no way of doing this in 1.5. Points were designed as internal system, so the player shouldn't see them. I could however create something like an optional stats page in journal, which could display specified in configuration values (like only "foo" and "bar" categories, but no "baz", because it's internal). This will however delay the 1.6 release one more day :(

@RankDragons

It is because your server has set wrong encoding. I cannot fix this, because configuration files are handled by Bukkit, not my plugin. You should try to change your server's encoding, but it may be impossible for some servers.

@jpell1221

No, the forums are inactive and I personally like comments. I always hated when the author of the plugin I was interested in disabled the comments. It was hard to quickly decide if the plugin is working on the newest MC version, if it's active and so on.

@LastTulare

I've heard that newest MM builds don't work with 1.5.3, but didn't have time to check this. However if it is true I'm going to fix this in 1.6 version which should be done in about a week (I hope I will make it). So anyway, don't worry ^^

@RankDragons

I'm sorry, but I don't think I understood everything. You shouldn't be creating items in messages.yml file, it's for translation. Items should be defined in items.yml, and it should be done with "/q item <name>" command, for safety.