Wrong message ID for messages sent from client about tmi.js

[Durss]

There's no more /commands available since Twitch disabled them all (except for /me) last fabruary,.
You now need to use the API to delete a message:
https://dev.twitch.tv/docs/api/reference/#delete-chat-messages

Here is a migration guide for every /command
https://dev.twitch.tv/docs/irc/chat-commands/#migration-guide

[iSlammedMyKindle]

Same issue over here ^ - we're working around this in our codebase by playing a game of telephone, which isn't ideal >.<

[Durss]

If that can be of any interest for anyone, I fixed this issue on this fork:
https://github.com/Durss/tmi.js

I generate a temporary ID, send it with the message in its "client-nonce" tag, wait for receiving a message ID, check if its client-nonce tag matches one of the sent messages, if so, I emit the new message event with the proper message ID.
This means that if twitch does not send back the real message ID, tmi.js will never emit the "message" event. Which may actually be a good idea as that may mean the message hasn't been sent.

(needs further testing to make sure it's ok tho)

[vivimouret29]

This issue is still open, I shall hope it will be done soon
We still can't delete a message with the command /deletemessage

I forked the work's @Durss but it didn't resolved the problem
Even if the UUID message is well relatable, it isn't erased from the tchat