DB/Strings: Fix a .npc info crash

Fixes #17066

2 files changed, 2 insertions, 0 deletions

diff --git a/sql/updates/world/6.x/2016_05_01_02_world_2016_05_01_00.sql b/sql/updates/world/6.x/2016_05_01_02_world_2016_05_01_00_world.sql
index 5a4d6c3197e..5a4d6c3197e 100644
--- a/sql/updates/world/6.x/2016_05_01_02_world_2016_05_01_00.sql
+++ b/sql/updates/world/6.x/2016_05_01_02_world_2016_05_01_00_world.sql
diff --git a/sql/updates/world/6.x/2016_05_02_00_world.sql b/sql/updates/world/6.x/2016_05_02_00_world.sql
new file mode 100644
index 00000000000..2aad74cc49d
--- /dev/null
+++ b/sql/updates/world/6.x/2016_05_02_00_world.sql
@@ -0,0 +1,2 @@
+-- was "NPC currently selected by player: DB GUID: %u, current GUID: %u. Faction: %u..."
+UPDATE `trinity_string` SET `content_default` = 'NPC currently selected by player: DB GUID: %u, %s. Faction: %u. npcFlags: %u. Entry: %u. DisplayID: %u (Native: %u).' WHERE `entry` = 539;