Whitelist Through SQL

Adds a new configuration option: whitelists_on_sql. If enabled, it starts looking through the client's whitelist_status var to see if a person is whitelisted for heads of staff (always a bit value of 1), or an alien (values stored in the ss13_whitelist_statuses table).

SQL/feedback_schema.sql

@@ -61,6 +61,7 @@ CREATE TABLE `ss13_player` (
   `ip` varchar(18) NOT NULL,
   `computerid` varchar(32) NOT NULL,
   `lastadminrank` varchar(32) NOT NULL DEFAULT 'Player',
+  `whitelist_status` INT(11) UNSIGNED NOT NULL DEFAULT '0',
   PRIMARY KEY (`id`),
   UNIQUE KEY `ckey` (`ckey`)
 ) ENGINE=InnoDB  DEFAULT CHARSET=latin1 ;
@@ -117,4 +118,4 @@ CREATE TABLE `ss13_privacy` (
   `ckey` varchar(32) NOT NULL,
   `option` varchar(128) NOT NULL,
   PRIMARY KEY (`id`)
-) ENGINE=InnoDB  DEFAULT CHARSET=latin1 ;
+) ENGINE=InnoDB  DEFAULT CHARSET=latin1 ;