Betonquest: Reuse of a Citizen NPC

[JD1992]

We really wanted to do a Advent calender for this years christmas. So we wanted to use a Citizens NPC as the Santa. But this NPC should have a different conversation for different days. The players have to do the Quests in order (Day 1, Day 2, ... ).

So we tried:

1. Use multiple packages and in every main.yml we used the ID of the NPC. Than we used a tag out of the package of the first day, to start the conversation of the second day (also with packageName.tagName).
2. Use multiple conversation files files in one package and in the main.yml we tried to assign the multiple conversation files. And with the tags we ried it like in 1.
3. '20': day1
4. '20': day2

Of course we could put all in one file, but over the whole days of december, this would be a big file and pretty messy.

Also we thought about how to manage it with the different days. So that on 1st December the first conversation will be active and on the 2nd December the first and the second day would be available, but in order.

[HollishKid]

Hello,

Just wanted to make some simple suggestions (I love trying to figure things out with BQ).

• To make different conversations "available" on a specific day you could use a block counter (setblock event). In other words, make a static event place a block in a row, conditionned on there being a block in the previous place (day). Thus your static event will count +1 for every 24h.
• You could then reuse the block presence as a condition to make the next part of the conversation available.
• If you really want to seperate every day in a different file, simple use one conversation for the NPC and make this "central" conversation launch the "conversation of the day" based on the previously implemented conditions.
• To make the conversations available in order, simply use tags. In order to launch the conversation of day 2, require tag_day1 etc.

Hope this helps.

[JD1992]

Thank you for your suggestions. I tried it out today and it seems to work. I needed a few tries, but it works like we intended.

So thanks for your fast help.