Luke
Veteran Member
Go home to your family, Neo
Posts: 1,124
|
kickip
Aug 3, 2019 13:05:34 GMT
via mobile
Post by Luke on Aug 3, 2019 13:05:34 GMT
Just a simple command that kicks every user online on one IP
An example would be if a mass spammer/bypasser joined on two accounts, a main and a sleeper. The main got banned, but we didn't realise there was a sleeper on, and that doesn't get banned and such
Another example would be if a user decided to have mutiple accounts online, and we had to ban one, it would be easier to kick all at the same time than manually kicking each
The only downside is that it could cause lag and spam. To solve the spam, maybe if there are 3+ users, it only broadcasts to admins?
I'm not too sure about the lag issue. Maybe if it works similarly to kicknoob, there won't be as much lag?
Just an idea
|
|
Lukas
Veteran Member
???????????? ????????????
Posts: 1,478
| Likes: 356
|
kickip
Aug 3, 2019 13:09:18 GMT
Post by Lukas on Aug 3, 2019 13:09:18 GMT
Vouch. I strongly believe that /GTFO should kick all online players with the same ips.
|
|
JagWire
Veteran Member
Woof
Posts: 3,734
| Likes: 2,143
|
Post by JagWire on Aug 3, 2019 13:10:15 GMT
Just a simple command that kicks every user online on one IP An example would be if a mass spammer/bypasser joined on two accounts, a main and a sleeper. The main got banned, but we didn't realise there was a sleeper on, and that doesn't get banned and such Another example would be if a user decided to have mutiple accounts online, and we had to ban one, it would be easier to kick all at the same time than manually kicking each The only downside is that it could cause lag and spam. To solve the spam, maybe if there are 3+ users, it only broadcasts to admins? I'm not too sure about the lag issue. Maybe if it works similarly to kicknoob, there won't be as much lag? Just an idea Vouch. At the moment the current solution is to ban the IP then kicknoob, but that doesn't always work. Or could glist banip not kick all players matching that IP |
|
Luke
Veteran Member
Go home to your family, Neo
Posts: 1,124
|
kickip
Aug 3, 2019 13:14:40 GMT
via mobile
Post by Luke on Aug 3, 2019 13:14:40 GMT
Just a simple command that kicks every user online on one IP An example would be if a mass spammer/bypasser joined on two accounts, a main and a sleeper. The main got banned, but we didn't realise there was a sleeper on, and that doesn't get banned and such Another example would be if a user decided to have mutiple accounts online, and we had to ban one, it would be easier to kick all at the same time than manually kicking each The only downside is that it could cause lag and spam. To solve the spam, maybe if there are 3+ users, it only broadcasts to admins? I'm not too sure about the lag issue. Maybe if it works similarly to kicknoob, there won't be as much lag? Just an idea Vouch. At the moment the current solution is to ban the IP then kicknoob, but that doesn't always work. Or could glist banip not kick all players matching that IP kicknoob kicks innocent players which is unfair on them |
|
WaaiFu
Veteran Member
haha floating heart goes brrr
Posts: 412
|
kickip
Aug 3, 2019 14:21:45 GMT
Post by WaaiFu on Aug 3, 2019 14:21:45 GMT
Vouch, I agree that /gtfo should kick all users on the same IP
|
|
StevenNL2000
Forum Admin 
Posts: 6,415
| Likes: 6,936
IGN: StevenNL2000
Timezone: UTC+01:00
Member is Staff. Need immediate assistance? Send a PM
|
kickip
Aug 3, 2019 15:11:12 GMT
Post by StevenNL2000 on Aug 3, 2019 15:11:12 GMT
Vouch for fixing the issue where other players on the same IP do not get kicked, object for creating a new command to do that.
|
|
|
|
kickip
Aug 4, 2019 8:54:17 GMT
via mobile
Post by Captainclimber on Aug 4, 2019 8:54:17 GMT
Vouch
Any punishment involving banning should really just kick everyone with the same IP.
|
|
_Windows
Club 4000 Member
Posts: 7,881
| Likes: 9,611
|
kickip
Aug 5, 2019 15:50:12 GMT
via mobile
Post by _Windows on Aug 5, 2019 15:50:12 GMT
Also maybe a command like /who -ip that shows who is online sorted by IP.
|
|
|
|
kickip
Aug 5, 2019 16:05:21 GMT
via mobile
Post by mychaeljkmax on Aug 5, 2019 16:05:21 GMT
Vouch. I agree with Steven.
|
|
Andoodle
Veteran Member
[F4:Andoodle]
Posts: 1,044
| Likes: 333
|
kickip
Aug 5, 2019 18:50:08 GMT
Post by Andoodle on Aug 5, 2019 18:50:08 GMT
I used to play on the server with my sister before I became an admin. I think I'd be annoyed if anything she did got me banned too. Why not have a separate command for it?
|
|
Luke
Veteran Member
Go home to your family, Neo
Posts: 1,124
|
kickip
Aug 5, 2019 18:55:24 GMT
via mobile
Post by Luke on Aug 5, 2019 18:55:24 GMT
I used to play on the server with my sister before I became an admin. I think I'd be annoyed if anything she did got me banned too. Why not have a separate command for it? in this scenario, your sister would be responsible for your IP. if you get banned due to her, that's her fault. |
|
Andoodle
Veteran Member
[F4:Andoodle]
Posts: 1,044
| Likes: 333
|
kickip
Aug 5, 2019 20:25:08 GMT
Post by Andoodle on Aug 5, 2019 20:25:08 GMT
I used to play on the server with my sister before I became an admin. I think I'd be annoyed if anything she did got me banned too. Why not have a separate command for it? in this scenario, your sister would be responsible for your IP. if you get banned due to her, that's her fault. I wonder whether it's fair to punish two people for the actions of one. I'm struggling to see the objection to having a separate command which doesn't rely on the principle that adding a new command is presumably more tricky to work out than editing an existing command. |
|
JagWire
Veteran Member
Woof
Posts: 3,734
| Likes: 2,143
|
kickip
Aug 5, 2019 20:29:03 GMT
Post by JagWire on Aug 5, 2019 20:29:03 GMT
in this scenario, your sister would be responsible for your IP. if you get banned due to her, that's her fault. I wonder whether it's fair to punish two people for the actions of one. I'm struggling to see the objection to having a separate command which doesn't rely on the principle that adding a new command is presumably more tricky to work out than editing an existing command. Well, we can do /glist nameban which bans the user rather than the IP. However, this isn't a viable option if they are smart enough to change usernames. |
|
Andoodle
Veteran Member
[F4:Andoodle]
Posts: 1,044
| Likes: 333
|
kickip
Aug 5, 2019 20:32:58 GMT
Post by Andoodle on Aug 5, 2019 20:32:58 GMT
I wonder whether it's fair to punish two people for the actions of one. I'm struggling to see the objection to having a separate command which doesn't rely on the principle that adding a new command is presumably more tricky to work out than editing an existing command. Well, we can do /glist nameban which bans the user rather than the IP. However, this isn't a viable option if they are smart enough to change usernames. I realise that I forgot to say that I like the idea of having a command which bans an IP. My only objection was to the idea of making /gtfo automatically ban an IP which seemed to be getting traction: Vouch for fixing the issue where other players on the same IP do not get kicked, object for creating a new command to do that. . I think a separate command would make it less of a blunt tool. |
|
Luke
Veteran Member
Go home to your family, Neo
Posts: 1,124
|
kickip
Aug 5, 2019 21:24:20 GMT
via mobile
Post by Luke on Aug 5, 2019 21:24:20 GMT
Well, we can do /glist nameban which bans the user rather than the IP. However, this isn't a viable option if they are smart enough to change usernames. I realise that I forgot to say that I like the idea of having a command which bans an IP. My only objection was to the idea of making /gtfo automatically ban an IP which seemed to be getting traction: Vouch for fixing the issue where other players on the same IP do not get kicked, object for creating a new command to do that. . I think a separate command would make it less of a blunt tool. ...gtfo already auto bans IPs...? this suggestion makes it so either a command gets added where everybody on 1 IP gets kicked or everybody on an IP gets kicked when gtfo gets used |
|
- Achieved Aug 2nd, 2016
- Achieved Jul 6th, 2017
- Achieved Nov 15th, 2017
- Achieved Nov 2nd, 2018
