Betonquest: Quest GUI Example

[doitliketyler]

I read the documentation on how to do this but was wondering if you could provide a working example?

[joblo2213]

There is one...
Just install the plugin and look in the default package.

[Co0sh]

@joblo2213 Tyler is talking about this, it's not in the default quest.

@doitliketyler I'm sorry, but I don't have enough time to do it right now. I'll leave this issue open so maybe someone else has an example they're willing to share.

[joblo2213]

Oh another feature of the new Version i didn't knew about :D

[Co0sh]

It's not new, it's just a way of using inventory GUI conversations to do something else than I designed them for. BetonQuest has a lot of those "hidden usages" 😜

[doitliketyler]

Alright. I still need help with this:

"If you want your players to be able to choose a quest everywhere, every time, then you can create a conversation which can be started with an item. This one is a little hacky but it shows flexibility of BetonQuest. First you need a conversation which behaves as a quest choosing GUI. Name the NPC "Quester", add one option for each quest etc. Now you need an objective which will start this conversation using conversation event. It should be action objective, set to right click on any block. Add hand condition to make it accept only clicks with a specific item and make the objective persistent (so players can use it multiple times). The item used here should be marked as Quest Item so players can't drop it. Now define new global location covering your whole map and using it start the objective and give players the item. This way all players (existing and new) will get the quest item, which opens a GUI with quests when right clicked."

I've spent countless hours trying to figure this out and It would probably only take you 5 minutes to share a working example. Please do this.

[joblo2213]

So I created a example especially for you: questGUIExample.zip
Hope it helps. To get it working you just have to replace the world name in the main.yml.

If you are not using dev builds you have to make sure that default_conversation_IO: in your config.yml is set to chest as conversationIO: 'chest' in a conversation.yml does only work in the latest dev builds.

I'll also add this to the wiki...

[doitliketyler]

Thank you very much. That was very kind of you.