First, a little history snippet for those of you who weren't around back when /setmsg command was disabled:


Now, after a long discussion the team had on the subject recently, and a thorough review of its effect on the server gameplay since its removal, we feel complete removal of this feature is too big of a price to pay just to prevent people from "/l1 /l2ing" hostile ships. As a result, the command is once again enabled on Discovery GC, but with the following adjustment made to the server rules:

Quote:

3.1 [...] aggressors are not allowed to destroy a ship before allowing sufficient time to respond. [...]

This rule, which previously only applied to piracy interactions, is now extended to apply to any type of interaction. In simple, the new adjustment would require players to provide a reasonable amount of time for target(s) to actually respond to their roleplay before going in for the kill, and seeing as this is basically what any reasonable player already does, it's not that big of a change in practice and is only there to prevent setmsg-related instakills, which were one major part of the problem back in the day.

We understand this adjustment does not completely fix the issue of misuse of /setmsgs, however, hopefully this should help reduce it to the bare minimum and allow this command to be used again on the server with not as much problems and concerns as before.

P.S: Since /setmsg and /chattime are basically defined under the same plugin, having setmsgs disabled was also causing problems with the chattime command. Now that /setmsg is enabled again, the issue with /chattime is also fixed.