Author Topic: Additional server commands for temporary banning and muting (Read 6036 times)

Bonecrusher · « **on:** January 05, 2013, 06:36:40 am »

So I thought of a few commands which would come in handy for server admins. Since the HWID was introduced we only have one command to deal with it which is 'banhw'. What I see happening is adding atleast two more commands containing hwid parameter.

1st:
/tempbanhw hwid time

2nd:
/gmutehw hwid time

EDIT: improved post subject

Mittsu · « **Reply #1 on:** January 05, 2013, 01:56:53 pm »

very needed!

also, /admhw hwid

Falcon` · « **Reply #2 on:** January 05, 2013, 02:27:30 pm »

that's dangerous, hwid can be forged if you've enough knowledge.

Bistoufly · « **Reply #3 on:** January 05, 2013, 03:12:46 pm »

/tempbanhw hwid time
and
/gmutehw hwid time
Would be pretty handy.

/admhw hwid
Is dangerous indeed.

Bonecrusher · « **Reply #4 on:** January 05, 2013, 03:14:35 pm »

Server admin will have to decide whether to give admin on hwid or not.

zakath · « **Reply #5 on:** January 05, 2013, 03:15:56 pm »

you can already create adminhw either with scripting or using admin console, but imho it doesnt hurt to have it builtin.

Bistoufly · « **Reply #6 on:** January 05, 2013, 03:20:35 pm »

Quote from: Bonecrusher on January 05, 2013, 03:14:35 pm

Server admin will have to decide whether to give admin on hwid or not.

Quote from: zakath on January 05, 2013, 03:15:56 pm

you can already create adminhw either with scripting or using admin console, but imho it doesnt hurt to have it builtin.

I'm not too sure about this one. After all some admins are not fully aware of that issue.
But sure I agree, it's their responsibility in the end.

Do what you think best, falcon.

Falcon` · « **Reply #7 on:** January 06, 2013, 06:09:56 am »

Why me? I don't have the last word, Shoozza does. Let him worry about it... a bit

Bonecrusher · « **Reply #8 on:** January 07, 2013, 08:59:55 am »

Also what about changing alt+f3 to something else? Its really close to alt+f4 so soldat could be shut down by accident. Also sometimes when someone asks where he can see his fps and I reply with alt+f3 he would say something along the lines of 'nice try but its alt+f4'.

Shoozza · « **Reply #9 on:** January 07, 2013, 10:34:03 am »

Wrong subforum (belongs to suggestions).
Please don't use the private subforums for anything unrelated, only use it for private beta related talk.
Stay on topic this is only about additional server commands ill ignore everything else.

Hmm long ugly commands

I think they could be useful but explain how they would work.

Would they ban/gmute the hwid only or also the ip?
How do the other ban commands work and how do the other gmute commands work? We should stay consistent and avoid surprises.

The hwid can be easily faked. It's like a public password. So I think /admhw wouldn't be a good idea.

Vos · « **Reply #10 on:** January 08, 2013, 11:43:17 am »

I support this idea, would like to have more hw id commands.

Mighty · « **Reply #11 on:** January 08, 2013, 04:23:01 pm »

F12. I had to make a script for that, and it's extremely useful when managing a public server.

Bonecrusher · « **Reply #12 on:** January 08, 2013, 06:14:00 pm »

Added a poll

Shoozza · « **Reply #13 on:** February 16, 2013, 02:44:17 am »

Waiting for a reply for my questions in my previous post before I can vote.

Bonecrusher · « **Reply #14 on:** February 16, 2013, 05:21:48 am »

Quote from: Shoozza on January 07, 2013, 10:34:03 am

Hmm long ugly commands
I think they could be useful but explain how they would work.

Would they ban/gmute the hwid only or also the ip?
How do the other ban commands work and how do the other gmute commands work? We should stay consistent and avoid surprises.

Let's take a look at those commands currently we have:
/banhw hwid | /unbanhw hwid[bans hwid permanently]
/ban id| /unban ip [bans ip and hwid for 30days]
/gmute id | /ungmute id [permanently mutes an id]

What is missing?
/gmute hwid /ungmute hwid
/tempban hwid time

I'm not sure whether or not /adm hwid would be necessary

Shoozza · « **Reply #15 on:** February 16, 2013, 06:10:52 am »

Quote from: Bonecrusher on February 16, 2013, 05:21:48 am

Quote from: Shoozza on January 07, 2013, 10:34:03 am
...

Let's take a look at those commands currently we have:
/banhw hwid | /unbanhw hwid[bans hwid permanently]
/ban id| /unban ip [bans ip and hwid for 30days]
/gmute id | /ungmute id [permanently mutes an id]

What is missing?
/gmute hwid /ungmute hwid
/tempban hwid time

I'm not sure whether or not /adm hwid would be necessary

Hmm i wonder why /ban only bans for 30 days.

One solution would be:
banlast - ban last leaving player ip and hwid forever banlastip - ban last leaving player ip forever banlasthw - ban last leaving player hwid forever tempbanlast time - ban last leaving player ip and hwid for time tempbanlastip time - ban last leaving player ip for time tempbanlasthw time - ban last leaving player hwid for time unbanlast - unban last leaving player ip and hwid unbanlastip - unban last leaving player ip only unbanlasthw - unban last leaving player hwid only ban name|id|ip|hwid - ban ip and hwid forever banip name|id|ip|hwid - ban ip forever banhw name|id|ip|hwid - ban hwid forever tempban name|id|ip|hwid time - ban ip and hwid for time tempbanip name|id|ip|hwid time - ban ip for time tempbanhw name|id|ip|hwid time - ban hwid for time unban name|id|ip|hwid - unban ip and hwid unbanip name|id|ip|hwid - unban ip only unbanhw name|id|ip|hwid - unban hwid only gmute name|id|ip|hwid - mute ip and hwid forever gmuteip name|id|ip|hwid - mute ip forever gmutehw name|id|ip|hwid - mute hwid forever tempgmute name|id|ip|hwid time - mute ip and hwid for time tempgmuteip name|id|ip|hwid time - mute ip for time tempgmutehw name|id|ip|hwid time - mute hwid for time ungmute name|id|ip|hwid - unmute ip and hwid ungmuteip name|id|ip|hwid - unmute ip only ungmutehw name|id|ip|hwid - unmute hwid only kick name|id|ip|hwid - kick player adm name|id|ip|hwid - add ip to remote admin ip list admip name|id|ip|hwid - add ip to remote admin ip list unadm name|id|ip|hwid - remove ip from remote admin ip list unadmip name|id|ip|hwid - remove ip from remote admin ip list

What the colors mean:
player needs to be ingame to work
will be partly ignored if player is not ingame
The other thing is in which order things should be matched:
1) name, id, ip, hwid (first check for name then id then...)
2) name, ip, id, hwid
3) id, ip, hwid, name
4) ip, id, hwid, name

NOTE: The current commands work differently:
ban name|id banip ip

They were made when no hwids existed so they don't know about them (except for those who where "updated").

Bistoufly · « **Reply #16 on:** February 16, 2013, 06:33:56 am »

Sounds good Shoozza!

Bonecrusher · « **Reply #17 on:** February 16, 2013, 06:54:37 am »

Will take a while to get used to them but after all it finally looks like a proper command system for server admins!

SyavX · « **Reply #18 on:** February 16, 2013, 07:52:10 am »

Once again, I suggest to use advanced time period format for temporary commands:

Quote from: SyavX on February 19, 2011, 07:54:16 am

[timeperiod] - optional "1w2d3h4m"-formatted string (w, d, h, m should be enough)

#w - weeks #d - days #h - hours #m - minutes

Default timeperiod could be 1-2 weeks or 30 days like it was with ban command.

Bonecrusher · « **Reply #19 on:** February 16, 2013, 07:55:56 am »

Time in minutes will be sufficient imo, you can always use google to calculate it.

News:

Poll

Do you like that idea?

Author Topic: Additional server commands for temporary banning and muting (Read 6036 times)