Description:


Current behaviour:
Currently, the gossip options for these 2 NPCs are unresponsive, the do not open any new gossip page at all.
The gossip options also do not update as they should by being removed when you have visited those Elders named in the gossip option label text.
If you check the other Elders who are referencing in the gossip options those you now have visited, you will see that those gossip options get removed from the list as soon as you have completed the Elder quest and received the Coin of Ancestry from that referenced Elder.
Expected behaviour:
The gossip options belonging to the NPCs 15572 (Elder Runetotem) & 15579 (Elder Darkhorn) should open and show a gossip page describing where those NPCs are supposed to be.
Steps to reproduce the problem:
.go creature id 15572 and/or .go creature id 15579Branch(es):
3.3.5, maybe both (I have only tested on 3.3.5)
TC rev. hash/commit:
TrinityCore rev. a149261e94b6 2020-01-09 23:10:46 +0100 (3.3.5 branch) (Unix, RelWithDebInfo, Static)
Using SSL version: OpenSSL 1.1.1c 28 May 2019 (library: OpenSSL 1.1.1c 28 May 2019)
Using Boost version: 1.67.0
Using MySQL version: 8.0.18
Using CMake version: 3.13.4
Compiled on: Linux 5.3.0-1009-azure
Automatic database updates are enabled for the following databases: Auth, Characters, World
Worldserver listening connections on port 8085
Realmlist (Realm Id: 1) configured in port 8085
VMAPs status: Enabled. LineOfSight: 1, getHeight: 1, indoorCheck: 1
MMAPs status: Enabled
maps directory located in ./maps. Total size: 251987687 bytes
vmaps directory located in ./vmaps. Total size: 658130721 bytes
mmaps directory located in ./mmaps. Total size: 1997886944 bytes
Using enUS DBC Locale as default. All available DBC locales: enUS
Using World DB: TDB 335.19121
Operating system: Unix (https://tcubuntu.northeurope.cloudapp.azure.com/)
(I would have liked to suggest a DB update to fix these gossip options, but I haven't had time to rebuild my local core + DB setup, so I find it a bit difficult to research the DB contents of those gossips.)
``sql
UPDATEgossip_menu_optionSETActionMenuID= 21097 WHEREMenuID= 6815 ANDOptionID= 1;
UPDATEgossip_menu_optionSETActionMenuID= 21107 WHEREMenuID= 6815 ANDOptionID= 2;
UPDATEgossip_menu_optionSETActionMenuID= 21147 WHEREMenuID= 6815 ANDOptionID= 3;
UPDATEgossip_menu_optionSETActionMenuID= 21086 WHEREMenuID= 6899 ANDOptionID= 0;
UPDATEgossip_menu_optionSETActionMenuID= 21100 WHEREMenuID= 6899 ANDOptionID= 1;
UPDATEgossip_menu_optionSETActionMenuID= 21122 WHEREMenuID= 6899 ANDOptionID= 3;
UPDATEgossip_menu_optionSETActionMenuID= 21147 WHEREMenuID= 6899 ANDOptionID` = 4;
BTW we need someone to sniff all this gossips as they are custom.
Most helpful comment
``
sql UPDATEgossip_menu_optionSETActionMenuID= 21097 WHEREMenuID= 6815 ANDOptionID= 1; UPDATEgossip_menu_optionSETActionMenuID= 21107 WHEREMenuID= 6815 ANDOptionID= 2; UPDATEgossip_menu_optionSETActionMenuID= 21147 WHEREMenuID= 6815 ANDOptionID= 3; UPDATEgossip_menu_optionSETActionMenuID= 21086 WHEREMenuID= 6899 ANDOptionID= 0; UPDATEgossip_menu_optionSETActionMenuID= 21100 WHEREMenuID= 6899 ANDOptionID= 1; UPDATEgossip_menu_optionSETActionMenuID= 21122 WHEREMenuID= 6899 ANDOptionID= 3; UPDATEgossip_menu_optionSETActionMenuID= 21147 WHEREMenuID= 6899 ANDOptionID` = 4;