Core/Players: Added support for single character bans

Core/Commands: Renamed .ban character to .ban playeraccount (.ban character will ban only the player, not account)

This revision reaches 10000, congratulations and thanks to everyone who contributed!

--HG--
branch : trunk
This commit is contained in:
Shauren committed 2010-09-19 17:02:14 +02:00
1 parent 639a906664
commit 97aeb251b8
16 files changed
+359 -37

No files matched your search

@@ -0,0 +1,10 @@
DROP TABLE IF EXISTS `character_banned`;
CREATE TABLE `character_banned` (
`guid` int(11) NOT NULL default '0' COMMENT 'Account id',
`bandate` bigint(40) NOT NULL default '0',
`unbandate` bigint(40) NOT NULL default '0',
`bannedby` varchar(50) NOT NULL,
`banreason` varchar(255) NOT NULL,
`active` tinyint(4) NOT NULL default '1',
PRIMARY KEY (`guid`,`bandate`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 ROW_FORMAT=DYNAMIC COMMENT='Ban List';
+4
View File
@@ -0,0 +1,4 @@
DELETE FROM `command` WHERE `name` IN ('ban character','ban playeraccount');
INSERT INTO `command` (`name`,`security`,`help`) VALUES
('ban character',3,'Syntax: .ban character $Name $bantime $reason\nBan character and kick player.\n$bantime: negative value leads to permban, otherwise use a timestring like "4d20h3s".'),
('ban playeraccount',3,'Syntax: .ban playeraccount $Name $bantime $reason\nBan account and kick player.\n$bantime: negative value leads to permban, otherwise use a timestring like "4d20h3s".');
@@ -0,0 +1,5 @@
DELETE FROM `trinity_string` WHERE `entry` IN (1131,1132,1133);
INSERT INTO `trinity_string` (`entry`, `content_default`) VALUES
(1131, 'The following characters match your query:'),
(1132, 'Currently Banned Characters:'),
(1133, '| Character | BanDate | UnbanDate | Banned By | Ban Reason |');