fCraft Forums

Real simple.

Sometimes we have kids use /say innapropriately. The Server OWNER is not often around, making it impossible to get to the server console to check.

Could there be a /sayidentify like command to let the user using the command know who uses say (if their rank can say and they are not outranked by the say-ee)

Or, possibly someone with a specific permission could see the /say's displayed like:

(say)PlayerWhoSays: Message

BobKare wrote:Or, possibly someone with a specific permission could see the /say's displayed like:

(say)PlayerWhoSays: Message

This wouldn't be any different then using normal chat then?

OfficerFlake wrote:Real simple.

Sometimes we have kids use /say innapropriately. The Server OWNER is not often around, making it impossible to get to the server console to check.

Could there be a /sayidentify like command to let the user using the command know who uses say (if their rank can say and they are not outranked by the say-ee)

Check the logfiles, search for /say ?

Intertoothh wrote:

BobKare wrote:Or, possibly someone with a specific permission could see the /say's displayed like:

(say)PlayerWhoSays: Message

This wouldn't be any different then using normal chat then?

It would only be for the highest ranks (specific permission), for example server admins that can't see the log files.

Intertooth wrote:

OfficerFlake wrote:Real simple.

Sometimes we have kids use /say innapropriately. The Server OWNER is not often around, making it impossible to get to the server console to check.

Could there be a /sayidentify like command to let the user using the command know who uses say (if their rank can say and they are not outranked by the say-ee)

Check the logfiles, search for /say ?

You can't see that in the WOM log files, and only the server host will have the ability.

OfficerFlake wrote:Sometimes we have kids use /say innapropriately. The Server OWNER is not often around, making it impossible to get to the server console to check.

The sole purpose of /say is to imitate server msgs. Hence your suggestion contradicts the cmds very nature.
If you've got significant problems with abuse of that command you could
restrict its usage and/or grant your moderators read access to the log files (eg via ftp).

Wundsalz wrote:The sole purpose of /say is to imitate server msgs. Hence your suggestion contradicts the cmds very nature.
If you've got significant problems with abuse of that command you could
restrict its usage and/or grant your moderators read access to the log files (eg via ftp).

Third time mentioned, but it should only be for the server owners/admins who doesnt need to see neutral, "official" server messages. At least they could be able to see who is sending them on their own server.

You could just ask

It's not about neutrality, this command is intended for server announcenents, it's not intended for personal use because that exactly leads to these problems. Inform your staff that /Say is too confusing to be used otherwise, it's not for chatting as "anon".

You might want to suggest some command to chat anonymously with, one that would be designed to cope with these problems.

If you have problems with abuse or mods that won't obey rules, I suggest taking higher measures like changing permissions or searching logs.

The point of /say messages is to make announcements/broadcasts, without identifying the source. If you have abuse problems, take Say permission away or use logfiles to identify the offenders.