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
2010-09-19 17:02:14 +02:00
parent 639a906664
commit 97aeb251b8
16 changed files with 359 additions and 37 deletions

View File

@@ -488,6 +488,33 @@ LOCK TABLES `character_aura` WRITE;
/*!40000 ALTER TABLE `character_aura` ENABLE KEYS */;
UNLOCK TABLES;
--
-- Table structure for table `character_banned`
--
DROP TABLE IF EXISTS `character_banned`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
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';
/*!40101 SET character_set_client = @saved_cs_client */;
--
-- Dumping data for table `character_banned`
--
LOCK TABLES `character_banned` WRITE;
/*!40000 ALTER TABLE `character_banned` DISABLE KEYS */;
/*!40000 ALTER TABLE `character_banned` ENABLE KEYS */;
UNLOCK TABLES;
--
-- Table structure for table `character_battleground_data`
--