Thread: Testing checklist

Originally Posted by Ewok

If an admin doesn't have power "config" he cannot use "ls_reload_configs", and if he does he can
If an admin doesn't have power "kick" he cannot use "ls_kick" and the kick option does not show up in his menu
ls_ban only works when you have the "ban" power. Make sure that if the admin has power "tempban" but not "ban", ls_ban does not work
ls_tempban only works if you have the power "ban" or "tempban".[/list]
The permanent ban menu option only shows up when you have the "ban" power. Make sure that if the admin has power "tempban" but not "ban", the option still doesn't show up[/list]
The 1 hour ban menu option only shows up when you have the power "ban" or "tempban".

All tested all working.

A point of clarification, would it be too much to ask for a printed feedback when ls_reload_configs is executed? Just a simple message like "LoneStar Config files reloaded" or something. Since it is a fairly major command it's a little freaky not to get any feedback from the mod.

I added tempban into the admin powers and documentation in admingroups.txt, double check it to make sure it is ok... Everything worked right so I assume I did it right.

Thanks

All of those are now marked off

ls_reload_config now prints back a message to the user saying the configs were reloaded. I'll push this to the test server later today.

your doc changes look good, i'll incorporate them

Jabber and I just tested a number of things. Since we couldn't make the server crash again we tested the ls_reload_configs

Originally Posted by Ewok

• Use ls_reload_configs to make sure changes in admins.txt are applied (admin->reg and reg->admin)
• Use ls_reload_configs to make sure changes in reservists.txt are applied (reservist->reg and reg->reservist)
• Use ls_reload_configs to make sure changes in mapcycle.txt are applied
• Change the map to make sure changes in admins.txt are applied (admin->reg and reg->admin)
• Change the map to make sure changes in reservists.txt are applied (reservist->reg and reg->reservist)
• Change the map to make sure changes in mapcycle.txt are applied
  
• admin pm works (when a non-admin does normal chat with @). Make sure the player sees his special chat message ("Sent to Admins: message") and the admins see the PM ("To Admins: player: message")

All worked perfectly. Using ls_reload_configs is a very very nice way to make changes to the various .txt files on the fly without requiring the server to restart.

"stopmusic" most definitely works.

6:02 CST: So I was trying to ban Jabber permanently and every time I would open the admin menu -> Player management -> Perm ban -> Jabber. His name would flash and the menu would disappear but he wouldn't be banned. Then, until i disconnected I could not open the admin menu either through the bound key or through console.

Originally Posted by Arreo

Jabber and I just tested a number of things. Since we couldn't make the server crash again we tested the ls_reload_configs

Originally Posted by Ewok

• Use ls_reload_configs to make sure changes in admins.txt are applied (admin->reg and reg->admin)
• Use ls_reload_configs to make sure changes in reservists.txt are applied (reservist->reg and reg->reservist)
• Use ls_reload_configs to make sure changes in mapcycle.txt are applied
• Change the map to make sure changes in admins.txt are applied (admin->reg and reg->admin)
• Change the map to make sure changes in reservists.txt are applied (reservist->reg and reg->reservist)
• Change the map to make sure changes in mapcycle.txt are applied
  
• admin pm works (when a non-admin does normal chat with @). Make sure the player sees his special chat message ("Sent to Admins: message") and the admins see the PM ("To Admins: player: message")

All worked perfectly. Using ls_reload_configs is a very very nice way to make changes to the various .txt files on the fly without requiring the server to restart.

marked off

Originally Posted by jabberwock

"stopmusic" most definitely works.

marked off

Originally Posted by Arreo

6:02 CST: So I was trying to ban Jabber permanently and every time I would open the admin menu -> Player management -> Perm ban -> Jabber. His name would flash and the menu would disappear but he wouldn't be banned. Then, until i disconnected I could not open the admin menu either through the bound key or through console.

I'll check the logs and post back... this might have to do with the menu bug TF2 started having last week.

Ok permaban from the menu should work now (server updated).

As a side note, apparently ls_ban was checked off when nobody has tested it, so it's now unmarked so it needs to get tested too.

Originally Posted by Ewok

As a side note, apparently ls_ban was checked off when nobody has tested it, so it's now unmarked so it needs to get tested too.

Use ls_ban to perm ban someone from the console?

No, I don't think anyone has tested that.

ALERT!

Someone has tried to register using the IP Address 124.134.52.127 which is MATCHED IN THE RBL DATABASE of the proxies.dnsbl.sorbs.net RBL.

This registration attempt has been allowed and the account has been permanently banned.

Registration Details: seolin794 ( AizawaChisa36@hotmail.com )