PHPAdmin Version 3.5 has been released for all the server admins out there, making the process of server administration just as easy as the Big Easy. Except there aren't any crazy Mardi Gras parties in Counter-Strike... yet. This new version of PHPAdmin introduces some new commands and fixes some nagging bugs. New and veteran server admins alike should hurry up and get to downloading the new version of PHPAdmin right away. More information about PHPAdmin can be found in this helpful FAQ page.[break="Click here for changelog"]
This release is mainly geared towards releasing the remaining in-server commands not released in the first version of 3.X.X and also to address and bug fixes since that version.
There were a couple of new features added and not mentioned in the changelog (however some of them are mentioned in the manual) because I wanted to wait until version 4 to "officially" announce them. HOWEVER, for those people whom are interested what they are:
The additional of an optional wave file for pa_bitchslap. the wave file was provided by Bob aka StinkyFingers here on Cy6.
A shortcut for pa_chat in which you can just type "chat: message" in say or team_say (without quotes)
The ability to privately message an admin in chat using "admin: message" (without quotes)
The official changelog is provided below:
1. [NEW] Added the remaining command set to PHPAdmin.2. [CHANGED] Faster detection for players using a banned ip or banned tag.
- pa_chat
- pa_lan
- pa_bury
- pa_unbury
- pa_switch
- pa_map
- pa_lo3
- pa_restartround
- pa_execclient
- pa_execall
- pa_rcon
3. [CHANGED] Improved code reuse as well as minimizing the number of mysql connections used; resulting in a performance increase and utilization of less memory.
4. [CHANGED] Addition of better mysql connection error checks and handlers to prevent server crashes caused from database timeouts.
5. [FIXED] Problem with server not re-executing the server.cfg after certain rounds causing temporary bans to not be tracked accurately.
6. [FIXED] Removed reference to "Cy6 admins" in the admin report feature. Was residue from using a merged project file.
7. [FIXED] Access level to ban was using the phpadmin_gag access level instead of its own.
8. [FIXED] Banning due to tag restriction would sometimes leave residual information behind that might cause a subsequent player to occupy that slot to be banned.
Comment