Skip to content
This repository was archived by the owner on Nov 5, 2019. It is now read-only.

Conversation

@TheComputerGeek2
Copy link
Member

We shouldn't be notifying staff when a player repeats the ticket creation command to update their ticket with the exact same message. This commit corrects the flawed notification behavior.

// But only if the ticket has been changed
if (update && MUtil.equals(msender.getMessage(), message))
{
msg("<b>Please do not spam our ticket system. Someone will be with you shortly.");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this really the best way to do it? It could be seen as a bit passive-agressive, and it would also make people realise that the message hasn't been forwarded which makes it easier to trick the system by changing it ever so slightly.
Perhaps just act normally towards the player and not send a message to the moderators?

if (update && MUtil.equals(msender.getMessage(), message))
{
msg("<b>Please do not spam our ticket system. Someone will be with you shortly.");
return;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a question of preference, but you could also throw a MassiveException with the message.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I had originally thrown a massive exception, but then I realized that we don't seem to do that very often in the commands here, so I went with the message to conform.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants