Script to improve admin work and bring QA into it

[boki]

v54 ET fellows!

 

 

Ever wanted to make your admin work easier? To bring some standard procedures everyone are familiar with and are easy to recognize? Well, I maybe just did one step forward to this.

 

Goal(s): to make admin work more easier and efficient, as to bring some quality assurance to it.

 

Solution: make standard messages and procedures everyone are aware of (with the time).

 

Implementation proposal: Writing standard messages and apply them through script (to ease the workload and procedure appliance). Using them in standard procedure so everyone can use them in the same manner. In order for this to work and bring the wanted full effect, admins must agree on standard messages, as their content and format

 

User base: this script is intended for ET admins only (lvl 4 and up). However, opinions of experienced ET gamers is welcome.

 

Proposed method of work: each admin should use 4 types of messages. The message types are:

1. [ Info Messages ] - selects Info message, 1st warning (inform players something has to be done)
2. [ Request Messages ] - selects Request msg, 2nd warning (inform players you are requesting it now)
3. [ Warning Messages ] - selects Warning msg, 3rd warning (inform players that next action will be taken by force)
4. [ Custom Messages ] - your own custom msg you want to apply, but not covered by standard messages

However, once these messages are standardized, it is forbidden to alter the messages and scripts. Admin may only alter the keys he wishes to bind, since this would be very inconvenient to enforce.

 

How to apply the script: bind MAIN script to a key of your choice. Alter other keys to your choice. There is one rule you must follow: each message, regarding the type, must be bound to the same key. An example: if u bind Info message "Even teams!" to ALT key, you must do the same for request and warning type messages also. All admins should use the same message content and format, otherwise there is not much point in this. After a while, users will quickly learn to visually recognize the messages and how to respond to them, since they are consistent.

 

 

Important: this is proposal only, yet to be discussed and eventually adopted. So far, players respond well to my way of work.

 

 

MAIN SCRIPT

// Fearless Aassassins Community - ADMIN BINDS - config by boki
wait
bind ALT "scores"
bind KP_PGUP "vstr demo_rec"                                                    // start or stop demo recording
  set demo_rec "vstr recordOn"
    set recordOn "record; !time; echo ^7[ ^6Recording started ^7]; set demo_rec vstr recordOff"
    set recordOff "stoprecord; set demo_rec vstr recordOn"

bind KP_RIGHTARROW "screenshotJPEG; echo ^6 ScreenshotJPEG"                     // Take a screenshot in JPEG format
bind KP_UPARROW "vstr guids1"
  set guids1 "clear; guids; bind KP_UPARROW "vstr guids2"; echo "^&.^7console ^&(^7CLEAR/GUIDS^&)""
  set guids2 "condump guidz.txt; bind KP_UPARROW "vstr guids1"; echo "^&.^7console ^&(^7CONDUMP GUIDS.txt^&)""
bind KP_DEL "team s; say [N] ^/is now a spectator"                              // Put yourself to spectators

bind KP_ENTER "vstr msg_type"        // Select message type - Info, Request, Warning or Custom
  set msg_type "vstr msg_type_cust"  // Default message type
    set msg_type_cust "exec binds-admin-cust.cfg;set msg_type vstr msg_type_info"
    set msg_type_info "exec binds-admin-info.cfg;set msg_type vstr msg_type_req"  
    set msg_type_req "exec binds-admin-req.cfg;set msg_type vstr msg_type_warn"
    set msg_type_warn "exec binds-admin-warn.cfg;set msg_type vstr msg_type_cust"

echo ^7[^5 ADMIN BINDS ^2executed ^7]

[ Info Messages ]

// [ Info Messages ] - selects Info message, 1st warning (inform players something has to be done)
wait
bind KP_SLASH "vstr teams"
  set teams "vstr info_team"
    set info_team "say ^2Admin info ^3>>> ^/Even teams, please! ^3(^/1st call^3); set teams vstr info_team_ok;echo ^7[ ^2Info msg ^/Teams ok ^2set ^7]"
    set info_team_ok "say ^2Admin info ^3>>> ^/Teams ok! ^3(^/After only 1 call, thank you!^3);set teams vstr info_team; echo ^7[ ^2Info msg ^/Even teams ^2set ^7]"
bind * "say ^2Admin info ^3>>> ^/Use only English language in main chat, thank you! ^3(^/1st call^3)"
bind KP_MINUS "say ^2Admin info ^3>>> ^/Stop messing with the team (harrasing teammates), thank you! ^3(^/1st call^3)"
bind KP_PLUS "say ^2Admin info ^3>>> ^/Please be polite and respect differences, no insults. Have fun! ^3(^/1st call^3)"
bind KP_HOME "say ^2Admin info ^3>>> ^/Do not touch the objective before 5 min. have passed, thank you! ^3(^/1st call^3)"
echo ^7[ ^2Info messages ^2loaded ^7]

[ Request Messages ]

// [ Request Messages ] - selects Request msg, 2nd warning (inform players you are requesting it now)
wait
bind KP_SLASH "vstr teams"
  set teams "vstr req_team"
    set req_team "say ^3Admin request >>> ^/Even teams, please! ^3(^/2nd call^3); set teams vstr req_team_ok;echo ^7[ ^2Info msg ^/Teams ok ^2set ^7]"
    set req_team_ok "say ^2Admin info ^3>>> ^/Teams ok! ^3(^/After 2 calls, thank you!^3); set teams vstr req_team; echo ^7[ ^3Request msg ^/Even teams ^2set ^7]"
bind * "say ^3Admin request >>> ^/Use only English language in main chat, thank you! ^3(^/2nd call^3)"
bind KP_MINUS "say ^3Admin request >>> ^/Stop messing with the team (harrasing teammates), thank you! ^3(^/2nd call^3)"
bind KP_PLUS "say ^3Admin request >>> ^/Please be polite and respect differences, no insults. Have fun! ^3(^/2nd call^3)"
bind KP_HOME "say ^3Admin request >>> ^/Do not touch the objective before 5 min. have passed, thank you! ^3(^/2nd call^3)"
echo ^7[ ^3Request messages ^2loaded ^7]

[ Warning Messages ]

// [ Warning Messages ] - selects Warning msg, 3rd warning (inform players that next action will be taken by force)
wait
bind KP_SLASH "vstr teams"
  set teams "vstr warn_team"
    set warn_team "say ^1Admin warning ^3>>> ^/Even teams! ^3(^/last call^3); set teams vstr warn_team_ok;echo ^7[ ^2Info msg ^/Teams ok ^2set ^7]"
    set warn_team_ok "say ^2Admin info ^3>>> ^/Teams ok! ^3(^/After 3 calls, I know you can do better ^3); set teams vstr info_team; echo ^7[ ^1Warning msg ^/Even teams ^2set ^7]"
bind * "say ^1Admin warning ^3>>> ^/Use only English language in main chat, thank you! ^3(^/last call^3)"
bind KP_MINUS "say ^1Admin warning ^3>>> ^/Stop messing with the team (harrasing teammates), thank you! ^3(^/last call^3)"
bind KP_PLUS "say ^1Admin warning ^3>>> ^/Please be polite and respect differences, no insults. Have fun! ^3(^/last call^3)"
bind KP_HOME "say ^1Admin warning ^3>>> ^/Do not touch the objective before 5 min. have passed, thank you! ^3(^/last call^3)"
echo ^7[ ^1Warning messages ^2loaded ^7]

[ Custom Messages ]

// [ Custom Messages ] - your own custom msg
wait
bind KP_SLASH "say ^/Server rules can be found on ^5http://fearless-assassins.com/wiki/index.php/W:ET_Server_Rules"
bind * "vsay Hi ^/Hi ET folks, [N] ^/is ^2online^/, questions welcome. Have fun!"
bind KP_MINUS "vsay GoodBye ^/That is all folks, dont do anything I would not do :-)"
bind KP_PLUS "vsay Thanks ^/You are (all) great, a big ^3Thank You ^/from [N]"

echo ^7[ ^6Custom messages ^2loaded ^7]

Questions and suggestions welcome!

 

EDIT: doing this, i had a solution in mind that will work for every mod out there, as the original ET ... if it is possible to put in vsays that only admins can use on every server, even better.

Edited January 16, 2016 by boki

[Shana]

This could be included in new quick say menu. The file would be in fa menu.pk3 and admins would use bind to open quicksay menu. Don't know if it's working 100% but going to test it soon.

I'm saying about quicksay cause admins'd have many binds to remember and we rather don't want to misclick and print wrong message.

I really like your idea but most of those are taken care of by fa quick say and some by lvl2+? with !teams !even, at least on noquarter #1.

[boki]

I made some changes into the script, which are more useful on jay mod than the one above:

// Fearless Aassassins Community - ADMIN BINDS - config by boki
wait
bind KP_PGUP "vstr demo_rec"                                      // start or stop demo recording
  set demo_rec "vstr recordOn"
    set recordOn "record;echo ^7[ ^6Recording started ^7];set demo_rec vstr recordOff"
    set recordOff "stoprecord;set demo_rec vstr recordOn"

bind KP_RIGHTARROW "screenshotJPEG;echo ^6 ScreenshotJPEG"        // Take a screenshot in JPEG format
bind KP_UPARROW "condump console.txt;^6Saved to a console.txt"    // save tekst from console to file	
bind KP_DEL "scores"                                              // Show scores

bind KP_ENTER "vstr msg_type"        // Select message type - Info, Request, Warning or Custom
  set msg_type "vstr msg_type_cust"  // Default message type
    set msg_type_cust "exec binds-admin-cust.cfg;set msg_type vstr msg_type_info"
	set msg_type_info "exec binds-admin-info.cfg;set msg_type vstr msg_type_req"  
    set msg_type_req "exec binds-admin-req.cfg;set msg_type vstr msg_type_warn"
    set msg_type_warn "exec binds-admin-warn.cfg;set msg_type vstr msg_type_cust"

echo ^7[^5 ADMIN BINDS ^2executed ^7]

[Barn!e]

You cannot add admin only Vsays without NOQ or etadmin or similar.

 

You can leave them out of the menu, but anyone who opens PK3 will be able to see them and use.

[RedBaird]

I keep telling Boki on the servers that he has the nicest "you killed me!" rotating binds that I have ever seen.  They make people want to kill him again, just to read the next one!