AntiMineChat prevents the use of MineChat clients through several features. MineChat uses Mojang's official login protocols so it is impossible to differentiate between a MC client and MineChat. However, AntiMineChat provides ways to detect if a player might be using MineChat through several features, and can then kick that player.
- Kick players for saying certain phrases when logging in.
- Customise the kick phrases.
- Force players to have to move before speaking.
- Force players to have to move before running commands.
- Customise the speak and command error messages.
- Kick players if they don't move for a certain amount of time after logging in.
- Customise the kick time.
- Customise the kick messages.
- Bypass permission to bypass all AntiMineChat features.
Drag and drop AntiMineChat.jar into your servers plugin directory.
View the default configuration here.
antiminechat.bypass - Bypass all AntiMineChat features.
Thanks, I will be! =)
This is a really great plugin! :D I hope you will continue to keep it up to date.
MineChat clients can run a command when they join the game. If the client was to run /spawn on connect, it would have seen them as moving, and would not kick them from the game, rendering this plugin useless. That's why it works this way.
If a player joins the game and teleports somewhere they should be able to speak/command. It does not let me. I would only like it to take effect on the initial spawn in.
Again, this is already a function. If a player joins the game and teleports somewhere, they still won't be able to speak and run commands as long as you have "MoveToSpeak" and "MoveToCommand" set to true. The plugin will take into account if they teleport around.
could you do the same for - chat/commands "my mistake on my last comment I meant the chat and commands after spawning."
Reworded for you to understand easier: Can you only initiate this for joining the server on the first time. Like if you use /spawn whilst in the server and stay still, you cannot speak or run commands.
I'm sorry, since when is it customary to do so, and why would you suggest it? Last I checked customary doesn't mean required.
It is customary to post the source code of projects. I suggest you do so.
I'll take a look, it should only be kicking them on first join, and once they move they should be exempt from being kicked in that session.
EDIT: After taking a look, everything was working as expected and I wasn't able to recreate what you were describing. If a player joins the server and doesn't move but teleports to anywhere on the server, their location will be updated to that spot, and they will be kicked if they continue not to move. However if they've been moving around on the server already and teleport anywhere, they should never be kicked for not moving. Can you explain a little further, and maybe show me a list of your plugins? Thanks!
I'm not sure what you're trying to say here.
My Spigot version had moving checks to detect stuff other than a message, just never got around to updating the documentation, feel free to decompile it and see for yourself.
Can you only initiate this for joining the server on the first time. Like if you use /spawn whilst in the server and stay still, you will be kicked.
People who pay for the app can remove that login message, so I had to throw in other ways to counter that. I actually tried googling plugins first and never come across yours, but it's good to see others had this idea first.
Looks a lot like my plugin with like 2 differences - http://dev.bukkit.org/bukkit-plugins/minechatban/
Thanks! I realised I forgot this right after I uploaded the file =P
I shall get that done for the next version!
Wicked plugin, thanks a bunch, could you support colour codes via the kick message please.