edit - shinyfinder/chatot-smogon GitHub Wiki
Availability: All Guilds
Right click/long press on message > Apps > edit
Example:
Right click/long press on message > Apps > edit
- Chatot: None
- Users: View Channel, Send Message in channel of message; Ban Members
Summary: Edits a modpost.
At this time, the following posts may be edited with this command:
Right click/long press on the message you wish to edit, then expand Apps. Clicking edit will present you with a modal where you can enter the new message text. The modal will be populated with the current message text. If logging is enabled in the server, Chatot will also log the old content in the respective logging channel as a form of version control. Desktop users can hover over the code block containing the old message text and click the copy button in the top right corner of the block to quickly copy the old text. The old text is logged to channels of type All, Edits, Mod executed, or Message target.
Chatot will attempt to resolve any tags (user or role) and channel references into a pingable format if it detects you are trying to tag/link to them. For example, @shinyfinder will resolve to <@id> and ping. This is best effort; be mindful that puncuation may throw it off (i.e. send a message to @shinyfinder. will not resolve the user shinyfinder, because usernames can include periods. One way to solve this is add a space before the period.) and usernames will only resolve if they are in the server. If it fails, you can always edit it again. The most reliable method is to always use IDs when trying to ping or link to a channel, but this is here for convenience.
A common error for this is a Missing Permissions error, like the one shown below. This is slightly different than the same error response that you might see from Chatot, as it is sent directly by Discord (notice how the text is red). This error message will change to "The application did not respond" after 3 seconds and clicking off then back into the channel (message will still be red). There are two likely reasons for this error:
- The user does not have location permission to use the command in the channel (i.e. they have permissions to use the command, so it shows up, but not in that channel, so it errors). This can be fixed by reviewing your location settings in the Integrations menu.
- The user does not have Send Message permissions in the channel. This can be fixed via the Edit Channel settings.
