Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CJ to delete his response if the request message was deleted #41

Open
IstuntmanI opened this issue Sep 11, 2017 · 1 comment
Open

CJ to delete his response if the request message was deleted #41

IstuntmanI opened this issue Sep 11, 2017 · 1 comment
Labels

Comments

@IstuntmanI
Copy link

Now users can spam '/whois' and similar mentioning commands for user info, then they can delete their messages, so CJ will look bugged/creepy if you forget that users can delete their posts. Solutions to this (I don't know if they are possible):

  1. "Store" the requesting-message ID somehow in the message CJ sent and if that message ID was deleted, let CJ delete his message too.
  2. Just add a mention in CJ's response message to the guy that requested that info.
  3. I don't think that it is possible to block users to delete/modify their messages, but it would be great to prohibit editing/deleting messages that requested a response from CJ. This would also solve the issue where someone requests other guy's info and then edits his request message and mentions somebody else, it can be confusing.

1 or 3 would be awesome if possible, 2 is pretty noobish and would look pretty bad.

P.S.: CJ you busta

@Southclaws
Copy link
Owner

I just checked, unfortunately 3 is not possible.

I think 1 could be the best.

However, I was considering doing something similar to 2 a while ago: mentioning the command user and force-deleting the command, just to prevent chat clutter - think of a normal SA:MP server, everyone's commands aren't broadcasted to the rest of the server!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants