Betonquest: Citizens And BetonQuest

[InsanityGamer]

I Love the Versatility that BetonQuest Offers, Please never stop developing it.
But, Im kind of new to Owning a minecraft server and im having trouble assigning a quest i wrote, to an NPC i made using Citizens.
Namely I don't know how to do it. the resources at https://github.com/Co0sh/BetonQuest/wiki/Reference#npcs left me pretty lost. felt it was kinda vague. I guess, i just need a little help with this part.

[co221133]

Mouse-over the existing NPC, and type /npc select. Now type /npc, and you take note of its ID number (it'll probably be something low for you, like 1).

Now go to the main.yml file in the package you're using (probably default) and type " 'ID_HERE': CONVERSATION_NAME_HERE " under the npcs: option.

npcs:
'1': conversationname

For instance.

[InsanityGamer]

Thanks! I'll try that in the morning

[InsanityGamer]

21.02 19:51:14 [Server] ERROR [BetonQuest] Conversation doesn't exist: default.firstquest

Then i pulled this from main.yml so you could see what i did
npcs:
'0': innkeeper
'25': Porky

the ingame name of the NPC is Porky, he asks if you can get 15 raw pork chops for him.
Did i do it wrong?

[InsanityGamer]

Found a different problem: it wasn't the NPC i dont think
ERROR [BetonQuest] Error in FirstQuest conversation from default package: Starting options are not defined

[Namnodorel]

Okay, the ingame name of the NPC is Porky. But what is its name in the BetonQuest conversations (the name of the .yml-file you have the conversation put into)? You'll need to specify that one. Unless your yml for the conversation is named Porky.yml, BetonQuest won't know that you want it to use that conversation for the specified NPC. For example, the file where the conversation of the Innkeeper is kept is named innkeeper.yml, which is why that is defined in main.yml.

The second error you're encountering happens when you don't define a starting point for the conversation (just like the error message says). It needs to look like this:

quester: "MyAwesomeNPC"
stop: "false"
first: "start"
NPC_options:
  start:
    text: "I AM AWESOME!!!!1111"
    pointers: "done,nope"
  nope:
    [...]

Note that the 'first' argument points to the conversation option "start". This tells BetonQuest that the first thing the NPC should say when it gets clicked should be the "start" option, in this case "I AM AWESOME!!!!1111". If you don't tell BetonQuest the starting point, or one that doesn't exist, it has no idea what to do and throws the error you are encountering.

[InsanityGamer]

Oh i had defined a start, and i'm sorry to say that i took the lazy way out and bought betonquest-editor, the plugin is working perfectly now. Wish it had some more tutorial videos, but i'll figure it out. thank you for your replies!

[Namnodorel]

Don't be sorry, you're supporting the developer of BetonQuest! ^^ And the editor is really useful, too; I'd recommend it to everyone who wants to create many quests. Still good to know the basics of YAML-Quests, though.