Here's mine. It's a very old picture, looks different now. Ignore the low brightness and odd wallpaper.





Here's my specs:

Add a forum games section. Would be useful in numerous ways.

tipo le features

hai semuanya o/

Yo,? can anyone pass me the link to samp unofficial discord, thanks in advance!

Smart Command Processor BETA

Latest Version: 0.3.2 beta (25th December 2017)



Important Issues:

1. YSI related includes must be included before SmartCMD for it to work.
   
   

• Command IDs
  
  SmartCMD assigns a unique ID number to each command to enhance the overall performance. By using command ids instead of command names, costly string comparisons can be avoided.
  
  
  
  
  
  
• Delete/Undelete commands
  
  Delete and un-delete commands at runtime.
  
  
  
  
  
  
• Command Flags
  
  A command flag is just a variable associated with each command. You can store crucial information about each command in its flag. Flags are optional. Unlike most command processors, command flags can be assigned right next to the command declaration during compile time.
  
  
  
  
  
  
• Alternate Command Names
  
  Unlike iZCMD/ZCMD, creating alternate command names does not take any extra CPU. Using the alternate command is as fast as using the parent command. The include provides a simple one liner method to set alternate commands. It also allows you to customize these commands like normal commands.
  
  
  
  
  
  
• Command Modes/States
  
  You can have more than one command function associated with each command.
  
  
  
  
  
  
• Iterating through commands
  
  Given that the command ids are continuous and the include stockpiles information about every command, it allows iterating through all commands with specific properties. If you'd ever need to implement per-player command permissions or need to store special information specific to each command, it'll take you less than 5 minutes to set things up using this include.
  
  
  
  
  
  
• Reassign Command Functions
  
  You can modify command behavior at runtime! The include provides facilities to change a command's function at runtime.
  
  
  
  
  
  
• Super-friendly include
  
  SmartCMD allows you to set command properties such as flags, alternate names during compile time while declaring/defining the command itself so that you don't have to fill your OnGameModeInit/OnFilterScriptInit with trash. You can also access command ids and command flags by a simple variable fetch; no need to bloat your code with GetCommandID or Get/SetCommandFlags function calls.
  
  
  
  
  
  
• Extensible
  
  The include provides several low level functions which allows anyone to customize the include without directly editing the include. This makes updating easier as your customized functionality is not a part of the include: you won't have to tweak your custom feature code when you update SmartCMD and no code copy-pasting is required.
  
  
  
  
  
  
• Documentation
  
  Detailed documentation (with example cod) for every function is present in the include itself. Other aspects of the include have been covered in detail in this topic with several examples.
  
  

1. Open Find & Replace Dialog (Ctrl H)
   
   
2. Provide search term as "(playerid, params[])"
   
   
3. Set the replacement text to "(cmdid, playerid, params[])"
   
   
4. Click on Replace All
   
   

1. Go to your OnPlayerCommandReceived declaration if it exists
   
   
2. Change the declaration to "OnPlayerCommandReceived(cmdid, playerid, cmdtext[])"
   
   
3. Go to your OnPlayerCommandPerformed declaration if it exists
   
   
4. Change the declaration to "OnPlayerCommandPerformed(cmdid, playerid, cmdtext[], success)"
   
   

1. Add "ALT:alternate_name = CMD:original_name;" anywhere in your script outside executable blocks (functions).
   
   
2. Remove the old iZCMD/ZCMD type alternate command
   
   

1. Open Find Dialog (Ctrl F)
   
   
2. Search for "cmd_"
   
   
3. Replace "cmd_urcmd(playerid, params)" with "cmd_urcmd(cid_urcmd, playerid, params)".
   
   

• cmdid: Command ID of the command used by the player. If the entered command does not exist, cmdid will be set to INVALID_COMMAND_ID.
  
  
• playerid: ID of the player who used the command
  
  
• cmdtext: The exact text which the player had typed in the message bar (for example, "/ban 0 test")
  
  

• cmdid: Command ID of the command used by the player. If the entered command does not exist, cmdid will be set to INVALID_COMMAND_ID.
  
  
• playerid: ID of the player who used the command
  
  
• cmdtext: The exact text which the player had inputted into the message bar (for example, "/ban 0 test")
  
  
• success: The value returned by the command function if it was existed. If it did not exist, success will be set to CMD_FAILURE by default.
  
  

• command which creates a list of commands which updates itself when a command is added or removed
  
  It is a boon for all of us if we had a /cmds command which updates itself when a new command is added. You can make such smart commands with SmartCMD. The /acmds command is supposed to list all administrative commands available in the server. We mark all administrative commands with the ACMD flag which /acmds uses to prepare a list of all admin commands.
  
  
  
  
  Code:

  #define ACMD 1

CMD<ACMD>:ban(cmdid, playerid, params[])

{

????? //Ban Code

????? return CMD_SUCCESS;

}

CMD<ACMD>:kick(cmdid, playerid, params[])

{

????? //Kick Code

????? return CMD_SUCCESS;

}

CMD<ACMD>:acmds(cmdid, playerid, params[])

{

???? static str[512], bool:need_frmt = true;

???? if(need_frmt)

???? {

????????? new altlist[32]; //A command can have a maxiumum of 32 alternate names? it is your script and you know it!

????????? for(new i = 0, j = GetTotalCommandCount(); i < j; i)

????????? {

??????????????? if(i == cmdid || IsCommandAlternate(i)) continue; //Lets not add /acmds itself to the list. And also let us not add alternate commands as separate commands.

??????????????? if(GetCommandFlags(i) == ACMD)

??????????????? {

????????????????????? new cmd[MAX_COMMAND_NAME];

????????????????????? GetCommandName(i, cmd);

????????????????????? strcat(str, cmd);

????????????????????? for(new j = GetAlternateCommands(i, altlist); j; j--)

????????????????????? {

??????????????????????????? strcat(str, ",");

??????????????????????????? GetCommandName(altlist[j], cmd);

??????????????????????????? strcat(str, cmd);

????????????????????? }

????????????????????? strcat(str, "\n");

??????????????? } ?

????????? }

????????? need_frmt = false;

???? }

???? return ShowPlayerDialog(playerid, ACMDS_DIALOG, DIALOG_STYLE_LIST, "Admin Commands", str, "Select", "Cancel");

}
  
  
  
  
  
  
• Restricting access to administrative commands
  
  This is another boon to all of us. You don't have to check the player's admin level in each and every admin command. You need to do just one check in OnPlayerCommandReceived. We mark all admin commands with the ACMD flag. When a player sends a command, OnPlayerCommandReceived is called before the command function is executed. Therefore, we check the flags of the command to see if it is an admin command in OnPlayerCommandReceived. If it is an admin command, we then check if the player is an admin. If the player is an admin, we let the command function to execute. If the player isn't an administrator, we send an error message informing the player that he cannot use the command.
  
  
  
  This is faster as the command function won't even be called if the player is not an administrator unlike other command processors where the admin level checks are done inside the command function. Moreover, it keeps your code neat.
  
  
  
  
  Code:

  enum (*=2)

{

????? ACMD = 1

}

CMD<ACMD>:ban(cmdid, playerid, params[])

{

????? Ban(playerid);

????? return CMD_SUCCESS;

}

public OnPlayerCommandReceived(cmdid, playerid, cmdtext[])

{

???? if(GetCommandFlags(cmdid) == ACMD)

????????? if(!IsPlayerAdmin(playerid))

????????? {

?????????????? SendClientMessage(playerid, RED, "You are not allowed to use this command.");

?????????????? return 0; //Do not execute the admin command

????????? }

??? return 1; //Execute the command

}
  
  
  
  
  
  
• Disabling commands in-game (Error message for disabled commands)
  
  By using the DisableCommand function, you are essentially deleting the command.
  
  
  
  
  Code:

  CMD<ACMD>:disablecmd(cmdid, playerid, params[])

{

????? switch(DisableCommand(GetCommandID(params)))

????? {

???????????? case -1: return SendClientMessage(playerid, RED, "The entered command does not exist.");

???????????? case 0: return SendClientMessage(playerid, RED, "The entered command is already disabled.");

???????????? case 1: return SendClientMessage(playerid, RED, "The entered command has been disabled.");

????? }

}

CMD<ACMD>:enablecmd(cmdid, playerid, params[])

{

????? switch(EnableCommand(GetCommandID(params)))

????? {

???????????? case -1: return SendClientMessage(playerid, RED, "The entered command does not exist.");

???????????? case 0: return SendClientMessage(playerid, RED, "The entered command is already enabled.");

???????????? case 1: return SendClientMessage(playerid, RED, "The entered command has been enabled.");

????? }

}
  
  
  
  
  
  
• Disabling commands in-game (Disabled message for disabled commands)
  
  In the previous example, by disabling the command, you were deleting it. When a player uses the command, it will treated as if he typed an invalid command. This example is more user friendly. Instead of deleting the command, we change the command function of the command. We first create a dummy command function which sends a message to the player informing him that the command has been disabled. We then assign the dummy command function to the command that has to be disabled. Hence, whenever a player uses the disabled command, the dummy command function will be called, which sends the disabled message.
  
  
  Code:

  forward disabled(cmdid, playerid, params[])

public disabled(cmdid, playerid, params[])

{

????? return SendClientMessage(playerid, RED, "The command has been disabled.");

}

CMD<ACMD>:disablecmd(cmdid, playerid, params[])

{

????? switch(ReassignCommandFunction(GetCommandID(params), "disabled"))

????? {

???????????? case -1: return SendClientMessage(playerid, RED, "The entered command does not exist.");

???????????? case 0: return SendClientMessage(playerid, RED, "The entered command is already disabled.");

???????????? case 1: return SendClientMessage(playerid, RED, "The entered command has been disabled.");

????? }

????? return CMD_SUCCESS;

}

CMD<ACMD>:enablecmd(cmdid, playerid, params[])

{

????? new cmd_func[MAX_FUNC_NAME], cid = GetCommandID(params);

????? GetCommandFunctionName(cid, cmd_func);



????? switch(ReassignCommandFunction(cid, cmd_func))

????? {

???????????? case -1: return SendClientMessage(playerid, RED, "The entered command does not exist.");

???????????? case 0: return SendClientMessage(playerid, RED, "The entered command is already enabled.");

???????????? case 1: return SendClientMessage(playerid, RED, "The entered command has been enabled.");

????? }

????? return CMD_SUCCESS;

}
  
  
  
  
  
  
• Custom Invalid Command Message
  
  Since SmartCMD lets you know if a command is invalid in OnPlayerCommandReceived itself, some processing time is saved since attempting to call the command function and then calling OnPlayerCommandPerformed is avoided.
  
  
  
  
  Code:

  public OnPlayerCommandReceived(cmdid, playerid, cmdtext[])

{

???? if(cmdid == INVALID_COMMAND_ID)

???? {

?????????? SendClientMessage(playerid, RED, "The command you entered does not exist. Use /cmds to obtain a list of commands");

?????????? return 0; //No need to call OnPlayerCommandPerformed.

???? }?????? ?

???? return 1; //Execute the command

}
  
  
  
  
  
  
• Logging command crashes & player-friendly crash messages
  
  You can use SmartCMD to log command function failures, crashes, etc with essential information such as date/time, command name, player name and the exact command text. By saving the player's name, you can talk to the player next time you meet to collect more information.
  
  
  
  
  Code:

  public OnPlayerCommandPerformed(cmdid, playerid, cmdtext[], success)

{

???? if(cmdid != INVALID_COMMAND_ID && !success) //command exists but it failed

???? {

?????????? new str[256], cmd[MAX_COMMAND_NAME], day, month, year, second, minute, hour;

?????????? GetCommandName(cmdid, cmd);

?????????? getdate(year, month, day);

?????????? gettime(hour, minute, second);

?????????? format(str, sizeof(str), "[%d:%d:%d - :%d:%d:%d][COMMAND CRASH] Command Name:%s Player:%s(%d) Cmdtext:%s", day, month, year, hour, minute, second, cmd, PlayerInfo[playerid][Name], cmdtext);



?????????? new File:crashlog = fopen("cmd_crashes.txt", io_append);

?????????? fwrite(crashlog, str);

?????????? fclose(crashlog);



?????????? SendClientMessage(playerid, YELLOW, "Oops! Sorry! The requested command failed to execute properly.");

?????????? return 1;

???? }?????? ?

???? return 1;

}
  
  
  
  
  
  
• Per-player command permissions
  
  
  Code:

  new PlayerDefaultCommandPermission[MAX_COMMANDS]; //Default permissions - note that even this can be edited in-game

new PlayerCommandPermission[MAX_PLAYERS][MAX_COMMANDS]; //true = allowed, false = not allowed



pubic OnPlayerConnect(playerid)

{

???? memcpy(PlayerCommandPermission[playerid], PlayerDefaultCommandPermission, MAX_COMMANDS*4); //Set player command permissions to default command permissions

???? return 1;

}

CMD<ACMD>:disablepcmd(cmdid, playerid, params[])

{

????? new pid, cid, cmd[MAX_COMMAND_NAME];

????? if(sscanf(params, "us["#MAX_COMMAND_NAME"]", pid, cmd)) return SendClientMessage(playerid, GREY, "Correct Usage: /disablepcmd [playerid/name] [command name]");



????? cid = GetCommandID(cmd);

????? if(cid == INVALID_COMMAND_ID) return SendClientMessage(playerid, RED, "The command you wished to disable for the player does not exist.");



????? PlayerCommandPermission[pid][cid] = false;

????? return SendClientMessage(playerid, GREEN, "The given command has been disabled for the given player.);

}

CMD<ACMD>:enablepcmd(cmdid, playerid, params[])

{

????? new pid, cid, cmd[MAX_COMMAND_NAME];

????? if(sscanf(params, "us["#MAX_COMMAND_NAME"]", pid, cmd)) return SendClientMessage(playerid, GREY, "Correct Usage: /enablepcmd [playerid/name] [command name]");



????? cid = GetCommandID(cmd);

????? if(cid == INVALID_COMMAND_ID) return SendClientMessage(playerid, RED, "The command you wished to enable for the player does not exist.");



????? PlayerCommandPermission[pid][cid] = true;

????? return SendClientMessage(playerid, GREEN, "The given command has been enabled for the given player.");

}

public OnPlayerCommandReceived(cmdid, playerid, cmdtext[])

{??? ?

???? if(cmdid != INVALID_COMMAND_ID && !PlayerCommandPermission[playerid][cmdid])

???? {

?????????? SendClientMessage(playerid, RED, "You are not allowed to use this command.");

?????????? return 0;

???? }

???? return 1;

}
  
  
  
  
  
  
• Making a /help [cmd] command
  
  
  Code:

  CMD:report[help](cmdid, playerid, params[]) return SendClientMessage(playerid, -1, "Reports the player to an administrator.");

CMD:report(cmdid, playerid, params[]) {...}



CMD:pm[help](cmdid, playerid, params[]) return SendClientMessage(playerid, -1, "Sends a private message to the given player.");

CMD:pm(cmdid, playerid, params[]) {...}



CMD:help[help](cmdid, playerid, params[]) return SendClientMessage(playerid, -1, "Access server help topics.");

CMD:help(cmdid, playerid, params[])

{

????? new success;

????? ExecuteCommand(params, help, playerid, success, "");

????? switch(success)

????? {

?????????? case INVALID_COMMAND_ID: return SendClientMessage(playerid, RED, "The specified command does not exist.");

?????????? case 0:? return SendClientMessage(playerid, RED, "The specified command does not have a help description.");

?????????? case 2: return SendClientMessage(playerid, RED, "The specified command does not exist."); //command was deleted

//case 1: handled by the command which was executed, i.e: a description message was sent to the player

????? }

????? return CMD_SUCCESS;

}
  
  
  
  
• Using flags as bitmask
  
  As said earlier, the flags are just variables/cells like any other. You can store anything in the flags in any fashion.
  
  
  
  
  Code:

  enum (*=2)

{

??? CFLAG_ACMD = 1,

??? CFLAG_VIP,

??? ADMIN_LEVEL_0,

??? CALEVEL_1,

??? CALEVEL_2,

??? CALEVEL_3,

??? //store admin level of the admin command in these 3 bits; admin level can start from 0 and go upto 7

??? .

??? .

??? .

??? //total number should not exceed 32

}



//we will use CALEVEL_1, CALEVEL_2, CALEVEL_3 to store the admin level as a number

//if you understand how to write a decimal number in binary form, the following defines must be self explainatory

#define ADMIN_LEVEL_1 CALEVEL_1 //1<<3

#define ADMIN_LEVEL_2 CALEVEL_2 //2<<3

#define ADMIN_LEVEL_3 CALEVEL_2 | CALEVEL_1 //3<<3

#define ADMIN_LEVEL_4 CALEVEL_3 //4<<3

#define ADMIN_LEVEL_5 CALEVEL_3 | CALEVEL_1 //5<<3

#define ADMIN_LEVEL_6 CALEVEL_3 | CALEVEL_2 //6<<3

//and so on



stock GetAdminLevel(flags)

{

?????? return ((flags & (CALEVEL_1 | CALEVEL_2 | CALEVEL_3))>>>3);

}

CMD<ADMIN_LEVEL_2 | CFLAG_ACMD | CFLAG_VIP>:nitros(cmdid, playerid, params[])

{

????? //add nos code

????? return CMD_SUCCESS;

}

stock IsVIPCommand(cmdid)

{

????? if(GetCommandFlags(cmdid) & CFLAG_VIP) return true;

????? return false;

}
  
  
  
  In this way, you can store more than one information in flags.
  
  
  
  
  
  
• Restricting access to administrative commands based on the player's admin level
  
  For those who are completely new to bit manipulation, here is a simple way to use the command id system to associate every administrative command with an administrative level. If you are not using flags for any other purpose, you can use the flags itself as a access level indicator (i.e: use flags of every command to store the admin level as an integer).
  
  
  
  
  Code:

  flg_kick = ADMIN_LEVEL_2;

flg_ban = ADMIN_LEVEL_3;
  
  
  
  but using the above method wont allow you to use the flags for any other purpose. Therefore, it is advisable not to use the whole flags to store the admin level as an integer so as to future proof your code.
  
  
  
  So here is another way.
  
  
  
  
  Code:

  enum (*=2)

{

??? VIP_CMD = 1,

??? RCON_CMD,

??? ACMD1,

??? ACMD2,

??? ACMD3,

??? ACMD4,

??? ACMD5

}



new AdminLevel[MAX_COMMANDS] = {0,0 ,0, ...};



CMD<ACMD1>:spectate(cmdid, playerid, params[])

{

????? return 1;

}

CMD<ACMD2>:kick(cmdid, playerid, params[])

{

????? return 1;

}

CMD<ACMD3>:ban(cmdid, playerid, params[])

{

????? return 1;

}

CMD<ACMD4>:banip(cmdid, playerid, params[])

{

????? return 1;

}

CMD<ACMD5>:setlevel(cmdid, playerid, params[])

{

????? return 1;

}



public OnGameModeInit()

{

????? for(new i = GetTotalCommandCount()-1; i >= 0; i--)

????? {

???????????? new flags = GetCommandFlags(i);

???????????? if(flags & ACMD1) AdminLevel[i] = 1;

???????????? else if(flags & ACMD2) AdminLevel[i] = 2;

???????????? else if(flags & ACMD3) AdminLevel[i] = 3;

???????????? else if(flags & ACMD4) AdminLevel[i] = 4;

???????????? else if(flags & ACMD5) AdminLevel[i] = 5;

????? }

}



public OnPlayerCommandReceived(cmdid, playerid, cmdtext[])

{

??????? if(cmdid == INVALID_COMMAND_ID) return SendClientMessage(playerid, RED, "You typed an invalid command. Use /cmds to obtain a list of commands.");



??????? if(PlayerAdminLevel[playerid] < AdminLevel[cmdid]) return SendClientMessage(playerid, RED, "You are not allowed to use this command."), 0;

}
  
  
  
  
  
  Here is another way to do the same. (the best method in my opinion)
  
  
  Code:

  enum (*=2)

{

??? VIP_CMD = 1,

??? RCON_CMD,

??? PLAYER_CMD.

??? ACMD1,

??? ACMD2,

??? ACMD3,

??? ACMD4,

??? ACMD5

}



#define



CMD<ACMD1>:spectate(cmdid, playerid, params[])

{

????? return 1;

}

CMD<ACMD2>:kick(cmdid, playerid, params[])

{

????? return 1;

}

CMD<ACMD3>:ban(cmdid, playerid, params[])

{

????? return 1;

}

CMD<ACMD4>:banip(cmdid, playerid, params[])

{

????? return 1;

}



CMD<ACMD5>:setlevel(cmdid, playerid, params[])

{

????? return 1;

}



public OnPlayerCommandReceived(cmdid, playerid, cmdtext[])

{

???????? static AdminLevelFlag[6] = {?? ?PLAYER_COMMAND, //normal player command

?? ? ?? ??? ??? ??? ??? ??? ??? ??? ?PLAYER_COMMAND | ACMD1,

?? ??? ??? ??? ??? ??? ??? ??? ??? ?PLAYER_COMMAND | ACMD1 | ACMD2, //allow level 2 admins to use level 1 commands

?? ??? ??? ??? ??? ??? ??? ??? ??? ?PLAYER_COMMAND | ACMD1 | ACMD2 | ACMD3, //allow level 3 admins to use level 1 and 2 commands as well

?? ??? ??? ??? ??? ??? ??? ??? ??? ?PLAYER_COMMAND | ACMD1 | ACMD2 | ACMD3 | ACMD4,

?? ??? ??? ??? ??? ??? ??? ??? ??? ?PLAYER_COMMAND | ACMD1 | ACMD2 | ACMD3 | ACMD4 | ACMD5};



??????? if(cmdid == INVALID_COMMAND_ID) return SendClientMessage(playerid, RED, "You typed an invalid command. Use /cmds to obtain a list of commands.");



//Check if this particular admin level has access to the command

??????? if(!(GetCommandFlags(cmdid) & AdminLevelFlag[PlayerAdminLevel[playerid]])) return SendClientMessage(playerid, RED, "You are not allowed to use this command.") ,0



?????? return 1;

}
  
  

• Pointing command id: The id of the command to which the command points to. For example, the alternate command /spec points to /spectate. Note that reassignment of command function does not make it point to another command by default rather it just changes the command's command function.
  
  
  
  
• Actual/original command id: This is the command id of the command itself and is no way related to what it points. For example, /spec has its own command id and this is called the actual/original command id but it points to the /spectate command.
  
  

• Pointing function index: The index of the function the command points to. Both alternate commands and reassigned commands point to the function which it executes when used.
  
  
  
  
• Actual/original function index: This value is a number which gives the position of the command in a sorted list of commands. This function index is usually the index of the command function at startup. This is an intrinsic property of a command name and it never changed in run-time.
  
  

AntiAimbot

Version: E1 (experimental version)

DISCLAIMER:
- the plugin is still experimental and has undergone rigorous testing on artificial servers but hasn't been tested on a real server with a large player base
- works for M4/AK47/MP5 only

AntiAimbot is an aimbot detector which uses a combination of empirical methods and artificial intelligence to accurately identify players using any form of aim assist. Empirical methods such as high ratio on moving players are used to efficiently suspect players of using aimbot. The samples of players suspected of using aim assist tools are forwarded to a combination of AI machinery consisting of mainly a neural network and a support vector machine for further detailed analysis. The AI machinery investigates the samples and decides if the feat achieved is humanly possible or not by "probably" (they are all black boxes) analyzing how quickly the aim moves, how synchronized the aim was with the motion of the victim, how fast the player reacts to changes and many such features.

Quote:The submitted vectors go through a lot of stages.

stages of data flow:

data collection: a script collects shot vectors
pre-filter: carries out checks to eliminate unreliable shot vectors
transform: transforms shot vectors to a form suitable for feature extraction
pooling: pool together a variable number of transformed vectors to form a complete sample
extract features: extract features from the vector pool
post-filter: carry out basic empirical checks on the sample to check reliability and possible use of aim-assist; if suspicious, forward it to the AI machinery
detectors: run through different detectors and average the result


Some of the pre-filter conditions are:
- must use a M4/AK47/MP5 (other weapons are disabled because of their unreliability)
- the victim must be moving
- and many more

If a shot fails any of these conditions, the entire running pool is rejected and starts afresh.

After pooling many shots together, it goes through another filter. The filter decides if there is enough information that can be extracted from the pool; if not, it continues to collect more shot. Once there is enough useful information, it checks for reliability and estimates the use of aimbot, for example, by checking the pool's ratio (required to be high for last X number of shots where X is between 7 and 20).

It's only after this step the sample is said to be fully complete. This is when `submit_vector` returns 1. This sample is put in a queue for processing. The detectors are running in different threads. They pick a sample from the input queue, investigate it, dump it to the output queue. In the server's next tick cycle, results are pulled out of the output queue and the callback is triggered for each sample.

Hence, the callback is triggered only when there was enough suspicion and after it was processed by the AI machinery.

TL;DR:
- callback is triggered only when there is some suspicion, i.e. when the empirical methods suggest the use of aimbot
* however, the AI machinery can reverse the decision and say this may not have been an aimbot
- it's difficult to get the callback triggered without using an aimbot because most samples are rejected empirical methods
- callback is triggered every minute or so when an aimbot is used
* the callback being triggered does not imply that aimbot was used; you need to check the probabilities

1. install gcc-8, g, gcc-8-multilib, g8-multilib, cmake
   
2. clone the sampml repository
   
3. change directory to `examples/anti-aimbot/plugin`
   
4. create and enter `build` directory
   
5. generate build files using `cmake .. -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_COMPILER=gcc-8 -DCMAKE_CXX_COMPILER=g8`
   
6. build plugin using `cmake --build . -- -j <number of threads>`
   

1. clone the sampml repository
   
2. open `examples/anti-aimbot/plugin` directory in Visual Studio 2017
   
3. click on CMake->Build
   

1. move the plugin binary to the `plugins` directory
   
2. create a new directory `anti-aimbot` in the `plugins` directory
   
3. create a new directory `models` in `plugins/anti-aimbot` directory
   
4. copy three model files from `examples/anti-aimbot/training/models` to the models folder
   
5. [optional] create config.cfg in the `anti-aimbot` directory
   

1. Helium
   
2. Variable/H2O
   
3. Luzziz
   

veli sano et t??l on suomalaisii