alias.dll build 10


Future:
+ Add NetBIOS Name ping for additional alias data (impress the newbies by telling them their parents' names:)
+ Add *info's ConnectType as additional alias data


Warnings:
REQUIRES SysOp to function at all.


Please note that all methods of "tagging" a player with the alias bot,
can produce false-positives just like when you ban someone.  I hold no
responsibility for all the terrible things that may happen as a result
of these false-positives.  So nyah:p

ID tagging that looks like this: :Catid:ID
MachineId numbers sometimes are shared between computers.
You shouldn't automatically assume that the players are the same person, but it's the most solid evidence.
If they also shared DELT (check with !whois), it's 99.9999% positive.

IP tagging that looks like this: :Catid:IP
If the !seen time for the player is not close to the !seen time for his alias, it's a false positive.
Otherwise it's very solid proof he's playing from the same network as the alias, if not on the same computer.

Sub-net IP tagging that looks like this: :Catid:~IP
This may be a false alarm.  The bot reports this so you can do your own investigation.

Netblock IP tagging that looks like this: :Catid:~~IP
This is probably a false alarm.  The bot reports this so you can do your own investigation.

DELT tagging that looks like this: :Catid:(67; 5 min. difference)
The first number, the lower the better, it won't be reported at all if it's above 150.
Time difference is critical.  If the number is huge positive or negative, it's most likely a false positive.
If both players are online at the same time and their IP's are different, DELT is a false positive.
There is a 1/100000 chance that DELT's will coincide.
It happens more often than MachineId's coinciding, but for different reasons.

The ban features use MachineId, last known IP addresses and DELT and uses the same database as the aliases.
The ban features are also meant to be used for the short-term only.  This is why they are not stored to disk,
and why there is a low limit on the number of minutes you can ban/spec/shutup a player for.


About:
This bot plugin will allow you to link together player aliases.

Player data is stored to alias.dat.  File format available on request,
of course, in case you decide to write a parser for it:)


Installation:
In spawns.txt, use alias.dll instead of blank.

If you have several public arenas in your zone, it would be wise to have a
different bot spawn in each arena.  When you spawn two bots from this DLL,
they share the same alias database.


Commands:
SysOp- *info
SMod- 
Mod- *tinfo *shutup *spec *kill


Issues:
Closing the bot with Ctrl+C *might* lose/corrupt some player data.

Be careful about reading the !alias output.
Players may put delimiter tokens in their names.

This won't work at all when the billing server is down.  Sorry.


Exported commands:

// Player+
!about - about this bot
!seen <player> - show time in GMT for when a player was last seen

// Mod+
!alias <name> - display player aliases along with how they were tagged

!zip -bsct <name> - ban/spec/shutup player for a certain amount of time, or change an existing zip
!unzip <name> - remove ban/spec/shutup
!listzip - list all zipped players in a cool tabular format
!zipchan - send zip-events to channel 1?

!ban -t <name> - shortcut for "!zip-bt=time <name>"
!speclock -t <name> - shortcut for "!zip-ct=time <name>"
!silence -t <name> - shortcut for "!zip-st=time <name>"
NOTE: You can speclock and silence players with the !zip command only: "!zip-cst=time <name>"

// SMod+
+!version - dll name/maker/version
!findid <machine id> - find all known player profiles matching the given machine id
!findtime <DELT> - find all known player profiles matching the given DELT
!whois <name> - display all known information aside from last seen date

// SysOp+
!findip <ip range> - find all known player profiles in the specified IP range. (!findip * = all profiles)