For MR most of us can see the mute command is kinda useless it can be bypass by rejoining.The spam bot won’t care about when we use mute they can still spam in our private chat.You can add a code for the mute when the player got mute 3 times they will get auto kick/ban form the server.
2 Likes
Josh has already addressed that he will fix the mute command, and he will released it on the same day where the kick command is being removed. Others including him were already look into the issue and has fixed, they just need to wait for the right time to push these updates.
3 Likes
For real.
1 Like
Please don’t do this. I love the kick command because it works and people can just do !rejoin to evade a mute. If he reworks the mute command at least use a datastore to save that you were muted so youc an’t talk when you rejoin.
Mute evasion = another mute. We already know this issue well and we used to continue with our procedure if they bypassed the mute, and I didn’t really have a problem with it, so. 
Are they able to use the ip stuff for the rejoin then instant mute or maybe go straight for the user like if leave before the time mute end will add back when they are back.I don’t know just a proposal.
Sadly, ROBLOX dosen’t let us have access to anything which touch to IP (which is logic for some reason). So no, we can’t do anything with this.
Howewer, theres could be a table (name of a data storage system) which stock usernames of muted user during their mute, and if they rejoin, the system can detect us again since their name is in there, and mute them again. 
Sadly!? What do you mean sadly? Would you want random developers having access to your IP address and an estimate guess to where you are?
Okok for sure that you might think ip out is danger right? So why don’t we just use the user id then that won’t be any personal information like up will out.
Guys, you know that Jaminio Forums aren’t used anymore, right…? 
WHAT For real?
BRUH.
Here you go. c: