Scribd Logo
Upload

Welcome to Scribd!

  • 7 views

    Hacker Menu

    Uploaded by

    Jeroukos (Jeroukos)
    The document contains SQL statements to create several tables for tracking hackers and banning players in a game. The tables created include hacker_ban to store ban records with player details and reasons, hacker_info to store player profile information, hacker_priority to track player power levels, hacker_vmenu to log virtual menu access, and some incomplete table definitions.

    Copyright:

    © All Rights Reserved
    Download as TXT, PDF, TXT or read online from Scribd
    Flag for inappropriate content

    You might also like

    Hacker Menu

    Uploaded by

    Jeroukos (Jeroukos)
    7 views2 pages
    The document contains SQL statements to create several tables for tracking hackers and banning players in a game. The tables created include hacker_ban to store ban records with player details and reasons, hacker_info to store player profile information, hacker_priority to track player power levels, hacker_vmenu to log virtual menu access, and some incomplete table definitions.

    Original Description:

    Original Title

    Hacker_menu

    Copyright

    © © All Rights Reserved

    Available Formats

    TXT, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    The document contains SQL statements to create several tables for tracking hackers and banning players in a game. The tables created include hacker_ban to store ban records with player details and reasons, hacker_info to store player profile information, hacker_priority to track player power levels, hacker_vmenu to log virtual menu access, and some incomplete table definitions.

    Copyright:

    © All Rights Reserved
    Download as TXT, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as txt, pdf, or txt
    7 views2 pages

    Hacker Menu

    Uploaded by

    Jeroukos (Jeroukos)
    The document contains SQL statements to create several tables for tracking hackers and banning players in a game. The tables created include hacker_ban to store ban records with player details and reasons, hacker_info to store player profile information, hacker_priority to track player power levels, hacker_vmenu to log virtual menu access, and some incomplete table definitions.

    Copyright:

    © All Rights Reserved
    Download as TXT, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as txt, pdf, or txt
    of 2

    CREATE TABLE IF NOT EXISTS `hacker_ban` (

    `identifier` varchar(25) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin NOT NULL,


    `license` varchar(50) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin DEFAULT NULL,
    `liveid` varchar(21) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin DEFAULT NULL,
    `xblid` varchar(21) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin DEFAULT NULL,
    `discord` varchar(30) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin DEFAULT NULL,
    `playerip` varchar(25) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin DEFAULT NULL,
    `targetplayername` varchar(32) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin NOT
    NULL,
    `sourceplayername` varchar(32) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin NOT
    NULL,
    `reason` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin NOT NULL,
    `timeat` varchar(50) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin NOT NULL,
    `expiration` varchar(50) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin NOT NULL,
    `permanent` int(1) NOT NULL DEFAULT 0,
    `BanID` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin NOT NULL,
    PRIMARY KEY (`identifier`)
    ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

    CREATE TABLE IF NOT EXISTS `hacker_info` (


    `id` int(11) NOT NULL AUTO_INCREMENT,
    `identifier` varchar(25) COLLATE utf8mb4_bin DEFAULT 'no info',
    `license` varchar(50) COLLATE utf8mb4_bin DEFAULT 'no info',
    `liveid` varchar(21) COLLATE utf8mb4_bin DEFAULT 'no info',
    `xblid` varchar(21) COLLATE utf8mb4_bin DEFAULT 'no info',
    `discord` varchar(30) COLLATE utf8mb4_bin DEFAULT 'no info',
    `playerip` varchar(25) COLLATE utf8mb4_bin DEFAULT '0.0.0.0',
    `playername` varchar(32) COLLATE utf8mb4_bin DEFAULT 'no info',
    PRIMARY KEY (`id`)
    ) ENGINE=InnoDB AUTO_INCREMENT=6 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_bin;

    CREATE TABLE IF NOT EXISTS `hacker_priority` (


    `SteamID` varchar(255) NOT NULL DEFAULT '',
    `Power` int(3) NOT NULL,
    `Adder` varchar(255) NOT NULL DEFAULT '',
    `Date` datetime NOT NULL DEFAULT current_timestamp(),
    `Expire` varchar(255) NOT NULL DEFAULT '0',
    `SteamName` varchar(255) NOT NULL,
    PRIMARY KEY (`SteamID`)
    ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

    CREATE TABLE IF NOT EXISTS `hacker_vmenu` (


    `SteamID` varchar(255) NOT NULL,
    `Type` varchar(255) NOT NULL,
    `SteamName` varchar(255) NOT NULL,
    `Expire` varchar(255) NOT NULL,
    `Date` timestamp NOT NULL DEFAULT current_timestamp() ON UPDATE
    current_timestamp(),
    `Adder` varchar(255) NOT NULL,
    PRIMARY KEY (`SteamID`)
    ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

    CREATE TABLE IF NOT EXISTS `hacker_time.' (


    `Timeset` varchar(230) NOT NULL DEFAULT '',
    `WeatherOption` varchar(214) NOT NULL DEFAULT '',
    `TimeFreeze` varchar(230) NOT NULL DEFAULT '',
    `WeatherFreeze` varchar(214) NOT NULL DEFAULT '',
    )
    CREATE TABLE IF NOT EXISTS `hacker_`

    You might also like