Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

/glist banip not kicking a player if their IP matches #2166

Open
peclarke opened this issue Jun 19, 2018 · 4 comments
Open

/glist banip not kicking a player if their IP matches #2166

peclarke opened this issue Jun 19, 2018 · 4 comments

Comments

@peclarke
Copy link

Not sure if this is a design thing or an actual bug - I thought it might be worthwhile to post it.
On banning a player today using /banip, I found I had to kick them after the banip had gone through in order for it to work. It might be handy if banip would kick the player if their IP matched the ban.

Cheers, Filez.

@Wild1145
Copy link
Member

Your IP is only checked when you login to the server so when you run the /banip command it would only ban the user when they login the next time. Why would you not use /gtfo if you're banning someone who is on the server?

@peclarke
Copy link
Author

I think I had a mind snap or similar and decided to use /banip instead. I guess I was a little surprised when it didn't kick him and he was banned. It might be an idea to put a kick functionality in there, but I can also see why you wouldn't. Either way, I will leave it to the developers to decide.

@berwil-1
Copy link

berwil-1 commented Jul 6, 2018

Did I miss something?
I'm pretty sure this happens for /gtfo, /tempban and all other forms of punishments.
Correct me If I'm wrong.

@Wild1145
Copy link
Member

Wild1145 commented Jul 6, 2018

It does happen with most other forms of punishment, however /glist was originally intended for banning offline players as I recall.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants