Improve NPC goodbye message handling

[boscv]

Describe the solution you'd like

Something that always bothered me is this:

Task::TalkNPC::conversation_end called at ai npc_talk 'select'. 
Conversa com NPC Funcionária Kafra (0) finalizada. 
NPC Funcionária Kafra (0): Task::TalkNPC::DESTROY was called 
An unexpected npc conversation has started, auto-creating a TalkNPC Task Task::TalkNPC::new has been called with sequence ''. 
[Funcionária Kafra] A Corporação Kafra tem o enorme prazer em servir você.
Agradecemos por usar nossos serviços. 
Npc which started autotalk has automatically sent a 'npc_talk_done'. 
Client network buffer flushed out
Talking was initiated by the other side and finished instantly
Talking with NPC Funcionária Kafra (0) at (175,226), ID 1F 00 00 00 
NPC Funcionária Kafra (0): Sending talk cancel [id '31'] after NPC has done talking 

The task is immediately destroyed after chosing to end conversation, and then opens a new task to handle the goodbye message.
Maybe we can improve the task by letting the task wait for a goodbye message, before destroying it?

Additional context

No response

[Henrybk]

When I made the current talknpc I remember the npc not responding anything after a talk cancel (choice N of N in talk responses), is that what is happening here?

[boscv]

i'm actually talking about opening two tasks to handle the same npc.. the first one is destroyed immediately after choosing to end conversation, then a new task is created just to handle the parting message that some npcs send after conversation end.

taks is destroyed, then npc sends message:

[Funcionária Kafra] A Corporação Kafra tem o enorme prazer em servir você.
Agradecemos por usar nossos serviços.

kore creates a new task to end conversation again, as in current build it is not expecting a parting message..
this causes a duplicated task and "Conversa com o NPC # finalizada"
not really a problem, but can be smoother.

PS: I tried some mods, but just got beaten.. the shame..