Core/ChatCommands: Fix a potential crash if a custom chat command does not have a specified help string

(cherry picked from commit 3ec98bf2410bb8fa73fe6b386a6e766bef575e97)

1 files changed, 6 insertions, 0 deletions

diff --git a/sql/updates/world/master/2022_02_28_19_world_2020_10_08_00_world.sql b/sql/updates/world/master/2022_02_28_19_world_2020_10_08_00_world.sql
new file mode 100644
index 00000000000..2208e456128
--- /dev/null
+++ b/sql/updates/world/master/2022_02_28_19_world_2020_10_08_00_world.sql
@@ -0,0 +1,6 @@
+-- 
+DELETE FROM `trinity_string` WHERE `entry`=196;
+INSERT INTO `trinity_string` (`entry`,`content_default`) VALUES
+(196, 'There is no detailed usage information associated with \'%.*s\'.
+This should never occur for stock TrinityCore commands - if it does, report this as a bug.
+If this is a custom command, use `trinity_string` to specify it. Look at cs_achievement.cpp for example usage.');