FOMO

FOMO

180 Downloads

Discord message doesn't show up in minecraft

MrtnsK opened this issue · 9 comments

commented

The message from minecraft can be seen in the discord channel, but the message from the discord server doesn't appear in minecraft. I didn't find any particular configuration on internet to fix this. Is there a certain way to make it work ?

also there's unwanted char that appear in the discord message :
image

thanks in advance

commented

About the unwanted characters, I am working on this. In case you're curious, it is because some plugins mess with name colors and then when FOMO gets the name it gets it with the colors and discord just reads those as plain text.

As for the D-M messages not working, I am not 100% sure why that is. Could you attach your config file (with token censored), Minecraft and server software version, and any logs/errors that happen when you send a message in Discord? There's not a lot I can do until I have more info

commented

*Also if you could attach FOMO version that would be awesome

commented

May a regex as filter would fix that ?

I'm using FOMO 0.4, Spigot server on 1.16.5 and Minecraft 1.16.5.
I also have EssentialX 2.18.2.0, WorldEdit 7.2.5 and WorldEdit Selection Visualizer 2.0.8
Capture d’écran 2021-05-13 131958

commented

Thank you for the suggestion I will give that a shot

As for the other issue, I could not replicate it. If you could double-check the values in your config, specifically channel id, and make sure that there are no errors as the plugin starts up.

commented

I have fixed the color codes issue, I will release it in the next patch as it's not the biggest issue

commented

im having the same problem but im using 1.16.4

commented

Nice about the color codes issue!
I double check the config file, everything is right
Here is the exact error :
image
to transmit the msg from discord to minecraft we don't have to use any prefix right ?
you juste have to write your message, not something like "!say "hello world"" ?

commented

Okay thank you for the logs

This is a known issue on v0.4, if you could try updating to v0.4.1 it should fix this issue!

commented

Re-open this issue if you have any more problems after updating