Core/Commands: Added TrinityString instead of hardcoded string

This commit is contained in:
Lopin
2011-08-22 12:07:27 +02:00
parent 6e79510bc5
commit b92d6f3d20
3 changed files with 7 additions and 2 deletions
@@ -0,0 +1,4 @@
DELETE FROM `trinity_string` WHERE `entry`=1136;
INSERT INTO `trinity_string` (`entry`,`content_default`,`content_loc1`,`content_loc2`,`content_loc3`,`content_loc4`,`content_loc5`,`content_loc6`,`content_loc7`,`content_loc8`)
VALUES
(1136,'Character %s has never been banned!',NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL);
+1 -1
View File
@@ -3106,7 +3106,7 @@ bool ChatHandler::HandleBanInfoCharacterCommand(const char *args)
PreparedQueryResult result = CharacterDatabase.Query(stmt);
if (!result)
{
PSendSysMessage("Character %s has never been banned!", name.c_str());
PSendSysMessage(LANG_CHAR_NOT_BANNED, name.c_str());
return true;
}
+2 -1
View File
@@ -804,7 +804,8 @@ enum TrinityStrings
LANG_BANLIST_CHARACTERS_HEADER = 1133,
LANG_ALLOW_TICKETS = 1134,
LANG_DISALLOW_TICKETS = 1135,
// Room for more level 3 1136-1199 not used
LANG_CHAR_NOT_BANNED = 1136,
// Room for more level 3 1137-1199 not used
// Debug commands
LANG_CINEMATIC_NOT_EXIST = 1200,