This is the Readme file for Admin Mod Beta 2.50.55-beta This beta version comes as a stripped down Admin Mod package, i.e. it comes without installer or configuration files. To install the beta files copy them to their respective locations by hand. This implies that you know where which files go. If you don't then please do not use this beta version and wait for the full version to the released. Don't ask about how to install these beta files in the Admin Mod forums, you will get no answers. Following is a list of important changes in this beta to pay attention to: * Support for all six types of Authentication IDs (plus WON IDs). Steam and DoD Retail should now work with server versions 1.1.1.0, 1.1.1.1 and 1.1.1.1c, on Inet servers and LAN servers. DoD Retail users should be granted proper access rights and keep them over map changes. * The Small AMX and compiler have been updated to version 1.8.4. This version is compatible with the last version, i.e. AM scripts do not have to be recompiled. * Admin Mod can now load both Windows and Linux format .amx files, converting them on the fly when necessary. The formats are still different and if you like to prevent the extra conversion on loading, you can still convert your .amx files with the AMX converter tool. But Linux servers should no longer crash when accidently loading Windows format scripts and vice versa. * The kicking of players has been changed to circumvent the problem introduced with the server kick command in version 1.1.1.1. This should not be an issue since Valve corrected the bug in the 1.1.1.1a update but some people seem still to have problems. * Fix in admin_ban when banning by IPs. It was still banning by ID instead. * Scripting functions centersay() and typesay() (and thus admin_csay and admin_tsay) now wrap long lines at a fixed width. Some other bugs with the Xsay() commands were fixed which could potentially screw output. * Support for three different methods of password encryption. Admin Mod passwords can now be encrypted with either Unix crypt() or MD5 hashes, on both Windows and Linux servers. The MySQL version also supports the encryption of passwords with the MySQL PASSWORD() method. The method is chosen by setting the encrypt_password cvar to: 0 to disable password encryption, 1 to use Unix crypt() encryption, 2 to use MD5 hash encryption, 3 to use MySQL PASSWORD() encryption (MySQL only). * A commandline utility called "encrypt" is available in the tools directory. This can be used to encrypt a password into either Unix crypt() or MD5 hash format. MySQL version: * The mysql_use_sqlPASSWORD cvar has been obsoleted by the new value '3' for the encrypt_password cvar which will turn SQL PASSWORD() encryption on. The cvar mysql_use_sqlPASSWORD has been removed. If you had the cvar mysql_use_sqlPASSWORD set to 1, set encrypt_password to 3 instead. * The use of the MySQL PASSWORD() encryption has been fixed. In certain situations MySQL queries could have failed and brought the communication with the MySQL server out of sync when PASSWORD() encryption was turned on. In addition password encryption queries get cached, reducing client-server traffic. * A new cvar "mysql_database" has been added. It can be used to set the database that Admin Mod should use for lookups. So instead of mysql_dbtable_users "adminmod.amusers" you can now choose to set mysql_database "adminmod" mysql_dbtable_users "amusers"