- Admin
- #1
Discussion of upcoming feature.
Thanks to some new capabilities given to us by MiB, Iâm fairly certain we can remove reliance on AMX as a workaround for most bugs, including map crashes, lack of retention of bans, vote system, etc. etc.
AMX has been both a crutch and a curse for a long time now, as in addition to the large number of additional edicts it generates (adding to our already vicious edict problem), it has been amongst the top generators of cheats. Mostly due to the latter issue, with some reluctance, I want to axe it from servers on the [FN] network. This will be accomplished by listlib.gam verification - which will also eliminate ent_mod and other metamod related cheats.
Only major potential downside I see to this is that many professional level hosts use Metamodâs/AMXâs SQL server system to manage their servers. However, I figure any potential host thatâs picky about requirements for the gameâs it hosts, will dump MSC out of the insane CPU usage, and in two years of seeing MSC servers, Iâve yet to see one professionally hosted anyways, save for Hellsdiner, which has no such qualms.
Now, before we take that step, I want to be absolutely sure that MSCâs internal admin system can handle all the critical functions of AMX/X, preferably better than AMX itself does. Hence, the discussion thread.
Hereâs a list of the current functionality of the MSC admin system, and those features that I want to be sure are in by February:
⢠Crashed.cfg
- Map votes and transitions will be written to the crashed.cfg - replacing StevenLAFlâs crashed recovery plugin
⢠Admins
- Adminstrators can be defined for a server by adding their steam idâs to \admins.txt
- Administrative commands follow:
⢠admin_ban / admin_unban / admin_kick
- Permanent bans will be written to a special .cfg, or, optionally, direct to the server/listenserver.cfg
- Kicks/bans/unbans can be done by partial name, steam id, or status index
⢠admin_vote / admin_votemap / admin_say
- Admins can initiate generic votes, map votes (bypassing restrictions), and make global anouncements
⢠admin_help
- Lists admin commands to admins.
⢠chatlog
- Weâve a fully functional chatlog, that will create files based on month and year, and catalog certain server events, and administrative actions, in addition to chat. (Optional)
⢠MOTD (pending)
- This bit is pending, Iâve not decided whether or not to use the pop-up or the combat hud. (Duplicating the amx screen text method is problematic, in addition to ugly.)
⢠iMessages (also pending)
- I donât personally use the amx_imessage system, as I find it obnoxious, but for those that do, I think best method would likely be to run them through the combat hud at the desired interval, maybe allowing a neigh infinite number of them through additional motd#.txtâs
⢠Chatbug bot
- MiB added a fix for the chat bug, so thereâs no longer any need for a chatbug bot.
⢠Heartbeat for restarter
- MSC Admin system includes awareness of the HLDS restarter and is fully compatible with the AMX method it uses.
⢠Client votemap, votekick, voteban, votepvp
- All can be enabled/disabled and customized via cvars and initiated either via chat or console.
- (vote PVP is still pending, but if Iâm lucky, I might be able to make it take effect immediately, rather than after map change.)
Proposed cvars (and their defaults):
⢠ms_reset_if_empty 0
- Run quit on server 60 seconds after last player leaves (helps keep server fresh)
⢠msvote_map_type "all"
- Options are: all, root, and nonfn
- all = allows voting for all maps (save hidden/gauntlet/maze)
- root = restrict voting to only root towns and maps not connected to the world
- nonfn = same as all, but also allows voting for maps not legit on FN (for non-FN servers)
⢠msvote_farm_all_day 0
- Allow voting for the map the players are on
⢠msvote_map_enable 1 - allow players to vote for maps from chat or console
⢠msvote_kick_enable 1 - allow players to vote kick from chat or console
⢠msvote_ban_enable 1 - allow players to vote ban from chat or console
⢠msvote_ban_time 60 - time to ban person voted banned by players (0 = permanent)
⢠msvote_pvp_enable 1 - allow vote for pvp (pvp mode will engage/end 60 seconds after vote)
⢠ms_chatlog 1 - log chat and various server events to monthly chat log
⢠ms_admin_contact "[none given]" - Place e-mail contact here, it will appear to kicked/banned players
⢠ms_ban_to_cfg 1
- Write permanent bans to server.cfg/listenserver.cfg so they stay permanent
- Either way permanent bans are also written to msc_bans.cfg, which you can exec from your server.cfg, if youâd rather keep it clean.
Basically what I want to know is if there are any major AMX functions hosts feel they need that arenât covered here, so that I can deal with it before the end of the month.
Thanks to some new capabilities given to us by MiB, Iâm fairly certain we can remove reliance on AMX as a workaround for most bugs, including map crashes, lack of retention of bans, vote system, etc. etc.
AMX has been both a crutch and a curse for a long time now, as in addition to the large number of additional edicts it generates (adding to our already vicious edict problem), it has been amongst the top generators of cheats. Mostly due to the latter issue, with some reluctance, I want to axe it from servers on the [FN] network. This will be accomplished by listlib.gam verification - which will also eliminate ent_mod and other metamod related cheats.
Only major potential downside I see to this is that many professional level hosts use Metamodâs/AMXâs SQL server system to manage their servers. However, I figure any potential host thatâs picky about requirements for the gameâs it hosts, will dump MSC out of the insane CPU usage, and in two years of seeing MSC servers, Iâve yet to see one professionally hosted anyways, save for Hellsdiner, which has no such qualms.
Now, before we take that step, I want to be absolutely sure that MSCâs internal admin system can handle all the critical functions of AMX/X, preferably better than AMX itself does. Hence, the discussion thread.
Hereâs a list of the current functionality of the MSC admin system, and those features that I want to be sure are in by February:
⢠Crashed.cfg
- Map votes and transitions will be written to the crashed.cfg - replacing StevenLAFlâs crashed recovery plugin
⢠Admins
- Adminstrators can be defined for a server by adding their steam idâs to \admins.txt
- Administrative commands follow:
⢠admin_ban / admin_unban / admin_kick
- Permanent bans will be written to a special .cfg, or, optionally, direct to the server/listenserver.cfg
- Kicks/bans/unbans can be done by partial name, steam id, or status index
⢠admin_vote / admin_votemap / admin_say
- Admins can initiate generic votes, map votes (bypassing restrictions), and make global anouncements
⢠admin_help
- Lists admin commands to admins.
⢠chatlog
- Weâve a fully functional chatlog, that will create files based on month and year, and catalog certain server events, and administrative actions, in addition to chat. (Optional)
⢠MOTD (pending)
- This bit is pending, Iâve not decided whether or not to use the pop-up or the combat hud. (Duplicating the amx screen text method is problematic, in addition to ugly.)
⢠iMessages (also pending)
- I donât personally use the amx_imessage system, as I find it obnoxious, but for those that do, I think best method would likely be to run them through the combat hud at the desired interval, maybe allowing a neigh infinite number of them through additional motd#.txtâs
⢠Chatbug bot
- MiB added a fix for the chat bug, so thereâs no longer any need for a chatbug bot.
⢠Heartbeat for restarter
- MSC Admin system includes awareness of the HLDS restarter and is fully compatible with the AMX method it uses.
⢠Client votemap, votekick, voteban, votepvp
- All can be enabled/disabled and customized via cvars and initiated either via chat or console.
- (vote PVP is still pending, but if Iâm lucky, I might be able to make it take effect immediately, rather than after map change.)
Proposed cvars (and their defaults):
⢠ms_reset_if_empty 0
- Run quit on server 60 seconds after last player leaves (helps keep server fresh)
⢠msvote_map_type "all"
- Options are: all, root, and nonfn
- all = allows voting for all maps (save hidden/gauntlet/maze)
- root = restrict voting to only root towns and maps not connected to the world
- nonfn = same as all, but also allows voting for maps not legit on FN (for non-FN servers)
⢠msvote_farm_all_day 0
- Allow voting for the map the players are on
⢠msvote_map_enable 1 - allow players to vote for maps from chat or console
⢠msvote_kick_enable 1 - allow players to vote kick from chat or console
⢠msvote_ban_enable 1 - allow players to vote ban from chat or console
⢠msvote_ban_time 60 - time to ban person voted banned by players (0 = permanent)
⢠msvote_pvp_enable 1 - allow vote for pvp (pvp mode will engage/end 60 seconds after vote)
⢠ms_chatlog 1 - log chat and various server events to monthly chat log
⢠ms_admin_contact "[none given]" - Place e-mail contact here, it will appear to kicked/banned players
⢠ms_ban_to_cfg 1
- Write permanent bans to server.cfg/listenserver.cfg so they stay permanent
- Either way permanent bans are also written to msc_bans.cfg, which you can exec from your server.cfg, if youâd rather keep it clean.
Basically what I want to know is if there are any major AMX functions hosts feel they need that arenât covered here, so that I can deal with it before the end of the month.