BetonQuest
BetonQuest is advanced and powerful quests plugin. It offers RPG-style conversations with NPCs and a very flexible quest system. Instead of being limited to creating "quest" objects with taking requirements and rewards upon completion, BetonQuest allows you to freely define what should happen (events), if it should happen (conditions) and what needs to be done for it to happen (objectives). Your quests don't have to look like "kill, bring, get reward": you can create multi-threaded stories, narrated with NPC conversations, with multiple endings affecting the player's gameplay in many ways.
@IrusVirus
The first bug is fixed (I will release new version a little bit later, so we can catch and fix all bugs).
The second one is strange though. I couldn't reproduce it but I will try to find a solution. I had the same problem about a month ago but it fixed itself so I didn't bother to find out what was causing it.
Bug report:
and I found another one, in the journal it cuts the text:
journal.yml =
quest_stadt1finden: 'Ich muss STADT 1 finden... Sperber sagte es ginge da vorne zu deren Baugebiet.'
@IrusVirus
Well, it wasn't approved yet so I didn't want to break any rules :P
@Co0sh
You forgot the link ;)
http://dev.bukkit.org/bukkit-plugins/betonquest/files/13-beton-quest-v1-5-2/
@Bastikeks
Fixed in 1.5.2 which is being approved :3
@Vertigoz
Spigot doesn't support @p with custom commands so I cannot "fix" this, sorry :(
@Bastikeks
Oh... that's a serious bug. Purge that player and don't teleport to other worlds with active Location objective. I didn't thought about multiple worlds when I was writing it. I will fix this and release v1.5.2.
this spammes the console million times: http://pastebin.com/LcRMUzpe
error is this: Caused by: java.lang.IllegalArgumentException: Cannot measure distance between flat and m4
(flat and m4 are the maps between the person teleported himself)
@Vertigoz
Honestly I have no idea. I have to take a look at this as I've never used selectors before. I will try to make it work but I'm not promising anything.
/q event [eventName] [playerName] now works when typed in the console!
However when I setup a command block to run this command:
q event [eventName] @p
or
q event [eventName] %player% it doesn't work!
Could you make it work? :d
@Bastikeks
That's strange... The journal is just a regular book, the plugin updates its content only on some rare occasions (like a journal event), so it shouldn't conflict in any way. Maybe it has something to do with the content itself? Does any of these errors come from BetonQuest?
for a random player i guess. not all... never saw that issue again since posting before (restarted 3 times and tested it)
another bug: WOAHWOAHWOAAAH *stunned* .... when teleporting with the journal (in hand) into another world errors are exploding the console XD
@Bastikeks
Have you tried reloading the server again? Does this happen for all players or just particular one? If so you could try to /q purge this player and see if it helps.
got this error sometimes when reloading/restarting the server and a player joins:
http://pastebin.com/mhZ8gdTF
@IrusVirus
Yes, it is. You just need to separate them with commas. They will be checked one after another, and the first that meets all conditions will be used.
The example you just showed will work (except the "bla bla bla" part of course xD).
Is it possible to have more than one defaultstarts in a conversation?
Exampel in innkeeper.yml =
@IrusVirus
It's not possible now but it's a good idea, I will add it.
Is it possible that I can add more than one 'tag remove' with a comma?
Example:
events.yml =
welcome_end: 'objective delay delay:1 events:remove tag:welcome_end'
remove: 'tag remove welcome,abc,123,morethanthis'
otherwise I must add so many events =S
@Vertigoz
Thanks, adding it to my list of bugs.
And there were errors on the wiki page. "<eventID>" and similar variables didn't show up, I had to escape "<" and ">". Now they all are visible. Check the page about commands again to see them.
@Co0sh
/q event [playerName] - fires an event (playerName is optional)
Cannot type /q event [playerName] in the console :3
(can type /q in console)
Ok, I have these three things done for v1.5.1:
Tomorrow I will add titles for journal updating message. If you'll find any more bugs please post them here so I can fix them before releasing v1.5.1 :3