[Solved] Bug Report - Jumbled Conversations

FroZeN wrote:Well the problem is not this, I did everything what you've written, but used /setconvtrigger. After everything is done, the NPC starts conversation. But the problem is, if you remove that NPC, the conversation is still there, which got replaced with other after removing it. It's totally hard to find which NPC is just sending msgs.

Here are two things I was going to suggest:

- Add a way to check every NPCs, which were set to conversations, via /setconvnpc and triggered with /setconvtrigger. The cmd will look like /showallconvnpcs.

- If a NPC is triggered for conversation, and later on if you remove that NPC, it should set the NPC to default settings, so that other NPC which will be replaced to it, won't trigger the conversations.

I don't think so that these things are available.

VK.Angel.OfDeath wrote:

FroZeN wrote:Well the problem is not this, I did everything what you've written, but used /setconvtrigger. After everything is done, the NPC starts conversation. But the problem is, if you remove that NPC, the conversation is still there, which got replaced with other after removing it. It's totally hard to find which NPC is just sending msgs.

Here are two things I was going to suggest:

- Add a way to check every NPCs, which were set to conversations, via /setconvnpc and triggered with /setconvtrigger. The cmd will look like /showallconvnpcs.

- If a NPC is triggered for conversation, and later on if you remove that NPC, it should set the NPC to default settings, so that other NPC which will be replaced to it, won't trigger the conversations.

I don't think so that these things are available.

I do not recommend using /setconvtrigger and /setconvnpc like I said. You can do it using /setnpcpickup instead. (There is a setting for detecting NPCs).

The old conversation system is a mess and has been replaced by the pickup variant. You will not have these problems if you use this.