Digital Paint Discussion Board
Development => Bugs, Feature Requests, and Feedback => Official Feature Votes => Topic started by: jitspoe on January 10, 2008, 03:10:12 AM
-
mute <playerid>
Disable chat text ability for those children who just cant control their mouths (or fingers).
http://dplogin.com/dplogin/featurevote/feature.php?id=10071
-
Hey quit taking pot shots at me!
-
Ahhhh this would resemble the Z mode on IRCX chat servers. Sometimes comes in handy
-
Really good idea, seconded.
But consider this. If that player is muted, instead of kicked because of his language, flaming, general behaviour etc., he will not know that he is indeed muted. Hence, he will come back to the same server, admin maybe wont be on at that time, so he will continue with his behaviour not knowing he was muted before. With kick/temp ban, admin states that that kind of behaviour will not be tolerated.
-
Really good idea, seconded.
But consider this. If that player is muted, instead of kicked because of his language, flaming, general behaviour etc., he will not know that he is indeed muted. Hence, he will come back to the same server, admin maybe wont be on at that time, so he will continue with his behaviour not knowing he was muted before. With kick/temp ban, admin states that that kind of behaviour will not be tolerated.
think that's why jits wants to make it mute *playerid* instead of userid, that way the person remains muted until the admin takes it off, even if that player reconnects
-
THen whenever the play attempts to talk, he will get the message that he has been muted, similar to when someone spam-floods caht.
-
What about when 'newbie' or 'noname' gets muted. How will you work around others using those same names not being muted also?
~MT
-
playerid is the global login id, whereas userid is the client number you're assigned when you enter a server. 'newbie' and 'noname' aren't registered nicks and therefore do not have a playerid -- so as i understand it, the mute command will not work on them unless they have a login account. a possible solution to this is to make another argument for sv_login (i.e., sv_login "3") that allows a player to play on the server without logging in, but not use any of the chat functions unless they login. <-- probably only a good idea if hints and tips are implemented since it would prevent new players from asking questions if they haven't taken the time to get an account yet.
-
Ahh I see.
Disregard my post.
~MT
-
Actually, playerid is just the id of the player on the server. Global login id would be the global login id. Perhaps it could store the IP, though, so a simple reconnect wouldn't get them unmuted, and it would also work for players that aren't logged in.
-
so that would mean they would be muted until the admin removes the IP from the log or whatever. what happens if the admin forgets to remove it and the player stays muted for days, if not weeks?
-
Ahhh... I was basing my assumptions of the difference between playerid/userid off of the default message for the "ignore" command without any arguments:
usage: "ignore <userid>" use ("players" to get userids)
nevermind what i said previously
-
so that would mean they would be muted until the admin removes the IP from the log or whatever. what happens if the admin forgets to remove it and the player stays muted for days, if not weeks?
Or the server can just keep it temporarily?
-
Im all about perma-mute.
-
Or the server can just keep it temporarily?
well that would obviously be the best choice. let the admins set the amount of time they wish the player should be muted based on what they were saying. just like temp-bans.
-
Actually, playerid is just the id of the player on the server. Global login id would be the global login id. Perhaps it could store the IP, though, so a simple reconnect wouldn't get them unmuted, and it would also work for players that aren't logged in.
Would it ban just that IP or range on extension?
For instance I have dynamic IP which is default in my country. To have static IP I would have to pay unreasonable ammount of money.
-
This isn't meant to be a permanent thing. I think you guys are looking into it too much. It's just a simple mute for a player saying inappropriate things.
-
Well in that case there should be something like instant message: U have been muted by admin for inapropriate behaviour.
-
This isn't meant to be a permanent thing. I think you guys are looking into it too much. It's just a simple mute for a player saying inappropriate things.
Well i think it should be like a kick / ban / temp-ban kind of system
kick-muted for the rest of the 20:00 or until you reconnect and apologize
temp-ban - temp-ban, no talking until its lifted by an admin
ban - youre done, plead it with the admin some other way =\
-
then what would be the point of muting? it's just supposed to be a mute, no kicking or banning involved. more useful for the new kids that love to spam binds every time they die.
-
How about a callvote system instead of giving the already bad admins there are more tools to abuse with? Nah, that'd be to fair.
-
All this is done under the assumption that admins will behave, or at least admin their server in a way they see fit. There should definitely be a notification (e.g. 'Player was muted by admin', or something along those lines), so that admins that would abuse it can't pretend nothing happened.
-
then what would be the point of muting? it's just supposed to be a mute, no kicking or banning involved. more useful for the new kids that love to spam binds every time they die.
i didnt mean bans as in bans. i meant bans from mm1/mm2-ing
-
How about a callvote system instead of giving the already bad admins there are more tools to abuse with? Nah, that'd be to fair.
Cobo needs to submit his idea for a customized voting system. With that in place, any admin command could be voted on if configured. Of course, your foul mouth and poor attitude will probably get you muted on nearly every server, be it by admin or player votes.
-
i didnt mean bans as in bans. i meant bans from mm1/mm2-ing
that is called muting.
-
we're talkin in circles coLa
-
lol. i love messing with you, that's all.
-
Would it ban just that IP or range on extension?
For instance I have dynamic IP which is default in my country. To have static IP I would have to pay unreasonable ammount of money.
hardware mutes, anyone? ;D
-
How about a callvote system instead of giving the already bad admins there are more tools to abuse with? Nah, that'd be to fair.
A callvote system could be abused just as easily as the new admin command.
I think that something a little more automatic like a filter command that can be disabled or enabled in the server config would eliminate the potential for any kind of admin or player abuse.
A base list of the most common abusive statements or language could be created. This list or data file should also be one that can be edited or added to by server owners.
The system should ALWAYS give 1 warning to the offender ("INAPPROPRIATE BEHAVIOR IS NOT TOLERATED ON THIS SERVER - YOU WILL BE MUTED FOR 24/48 HOURS FOR YOUR NEXT OFFENSE"). Then if they are abusive a 2nd time they'll be muted for a 24 to 48 hour period automatically.
Just a thought...
-
How would a voting system be abused? I'd find it hard to believe you would find that many people willing to abuse one person for no reason on a 16/16 server, or better yet a 32 max player server. When it only takes one of you to mute anyone you want.
-
This is only for public servers?
Because if someone does it in a matchserver, are you also muted in team_say?
-
This is only for public servers?
Because if someone does it in a matchserver, are you also muted in team_say?
Hmm, a valid concern. I guess it would depend on what login level is required to mute players, and what level people renting the server get.