Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.

Question --- Is there a whar to insert the toons name that is sending the text to discord
for example when i see a msg like " H****** says, 'hello' it would be niceto knowwho sent it rather than toggleing through each toon.
.#*# the only way to wildcard or can we use regex to customize? Regex could help with a few issues I've seen commented about, such as determining who is sending a given chat message.anyone got "You are not authorized to issue commands on this channel" when you were issue a "/" command to channel after migrated to MQNext?
No, this works for me, but it is a little buggy because discord will make it so you can’t unload. But I can confirm commands work, double check your setup.
Aye, even using the current build, I am unable to send any commands through discord into the game. I wasn’t able to track down specifically when it started but I know it was maybe a month or so ago, sometime in early June.Well, for sure it was broken in MQNext for a bit because I redid how all of the library stuff works. Have you had that experience on the last couple builds? (Like the current build)
I got it.I've been seeing the same thing actually. I still receive notifications fine, but have been unable to actually issue any commands through Discord into the game. I do not even get the error message you are showing, it just does nothing.
I've tried:
- Recreating my discord bot
- Resetting all MQ2Discord settings
- Making a new discord server/channel
Do you think you could post your setup/yaml so we can compare? It was working fine for me for months, but not sure if it was MQNext swap over or something else that broke it.
You can do this one of two ways, if you’re allowing something like:Is there a way to send says of players to discord but not mobs?
Can we add a TLO condition or something.
Currently I get a lot of
A relocated wyvern says, 'This will be your last stand, mortal.'
And then I block "A relocated wyvern" for each mob that says stuff.
But ideally I would be able to only send it was said by a player.
allowed:
- "#*#says,#*#"
blocked:
- "#*# #*# says,#*#"
- "#*#says, 'I have no need for this, #*#. You can have it back.#*#"
- "#*#says, 'Thanks for the #*#, #*#."
- "#*#says, 'Guarding with my life, oh splendid one#*#"
- "#*#says, 'As you wish, oh great one#*#"
- "#*#says, 'I beg forgiveness, Master#*#"
- "#*#says, 'Following you, Master#*#"
- "#*#says, 'Sorry, Master... calming down#*#"
notify:
- "[MQ2Say]#*#"
[Settings]
SaveByChar=1
AlertPerSpeaker=1
[Default]
AlertCommand=/discord process [MQ2Say] ${SayWnd.LastSpeaker} says: ${SayWnd.LastSay}
Yeah, it would have started when I changed out the libraries while fixing a different issue, but it should be fixed. I think it's going to be something in your configuration now (or I have another bug that I don't know about). Make sure if you're doing edits you're doing them to the yaml file in Next since alynel changed it over to yaml from json. Outside of that, we probably need to do some troubleshooting.Aye, even using the current build, I am unable to send any commands through discord into the game. I wasn’t able to track down specifically when it started but I know it was maybe a month or so ago, sometime in early June.
This sounds like you've got the channel name and group names instead of the IDs here. Below is an example with explanations:I still got some error like below:
[MQ2Discord] Error: Channel id YourChannelForTellsHere in all looks wrong
[MQ2Discord] Error: Channel id YourGroupChannelHere in group YourGroup looks wrong
[MQ2Discord] Config not loaded due to errors, please fix them and /discord reload
token: abcdefg123456789 # This is the token you got when following the instructions to setup your bot. It will never change.
user_ids:
- 123456789 # These are the user IDs that are allowed to send messages to your bot. Right click on yourself in Discord and say "Copy ID" to get this.
characters:
firiona_Bobthebuilder: # This is the character you want the settings to be loaded on in the format of servername_Charactername. Discord will tell you if it can't find your character and this is what it's talking about.
- name: auctions # This is the name of the configuration, most people are only going to have one, but you can have as many as you'd like.
id: 9876543210123456 # This is the channel ID you want messages to go to, you can get this by right clicking on the channel in Discord and doing "Copy ID"
allowed: # Allowed tells you what you want to see, though you don't need something in both Allowed AND Notice
- "#*# auctions, #*#"
blocked: # Blocked tells you what to skip if it matches an allowed or notify and also matches the block. These won't be shown.
- "Thatjerk auctions, #*#"
notify: # Notify tags @everyone in the channel when this matches. Good for getting notices on things you really want to know about without having notices turned on for everything in the channel.
- "#*#WTS My Soul#*#"
prefix: "" # If you want to prefix the message in Discord with anything. Like putting your character name in front of it if you share channels between characters.
send_connected: false # Should Discord tell you when you connect. If you're troubleshooting turn this on, but I usually leave it off.
allow_commands: true # Whether you can receive commands through this channel (commands will still only be accepted by the above user_ids). For most this is probably true
show_command_response: 2000 # After you send a command from Discord to EQ, MQ2Discord automatically sends all chat messages back to Discord. This is how long in milliseconds you want it to do that. Longer is great for viewing chat, horrible for combat spam. Default is 2 seconds and of course you can always keep it going with /echo hi repeatedly
You can do this one of two ways, if you’re allowing something like:
YAML:allowed: - "#*#says,#*#"
Then you want to block anything with spaces in it, and you're also going to have to block all the merchant text, pet text etc. (but the first line below is blocking anything with spaces in it)
Note the above list isn't complete and I just made it up so it might be wrong.YAML:blocked: - "#*# #*# says,#*#" - "#*#says, 'I have no need for this, #*#. You can have it back.#*#" - "#*#says, 'Thanks for the #*#, #*#." - "#*#says, 'Guarding with my life, oh splendid one#*#" - "#*#says, 'As you wish, oh great one#*#" - "#*#says, 'I beg forgiveness, Master#*#" - "#*#says, 'Following you, Master#*#" - "#*#says, 'Sorry, Master... calming down#*#"
However, the way I do it, and what my recommendation would be is to pick up MQ2Say which already does NPC checking and then create an allow or notice for:
YAML:notify: - "[MQ2Say]#*#"
And then in your MQ2Say configuration (note I have SaveByChar off because I use the same settings for all Characters, but you don't have to do it that way, you can do the setting under each):
Since MQ2Say already does NPC checks and the like this will severely limit false positives.INI:[Settings] SaveByChar=1 AlertPerSpeaker=1 [Default] AlertCommand=/discord process [MQ2Say] ${SayWnd.LastSpeaker} says: ${SayWnd.LastSay}
Yeah, it would have started when I changed out the libraries while fixing a different issue, but it should be fixed. I think it's going to be something in your configuration now (or I have another bug that I don't know about). Make sure if you're doing edits you're doing them to the yaml file in Next since alynel changed it over to yaml from json. Outside of that, we probably need to do some troubleshooting.
This sounds like you've got the channel name and group names instead of the IDs here. Below is an example with explanations:
YAML:token: abcdefg123456789 # This is the token you got when following the instructions to setup your bot. It will never change. user_ids: - 123456789 # These are the user IDs that are allowed to send messages to your bot. Right click on yourself in Discord and say "Copy ID" to get this. characters: firiona_Bobthebuilder: # This is the character you want the settings to be loaded on in the format of servername_Charactername. Discord will tell you if it can't find your character and this is what it's talking about. - name: auctions # This is the name of the configuration, most people are only going to have one, but you can have as many as you'd like. id: 9876543210123456 # This is the channel ID you want messages to go to, you can get this by right clicking on the channel in Discord and doing "Copy ID" allowed: # Allowed tells you what you want to see, though you don't need something in both Allowed AND Notice - "#*# auctions, #*#" blocked: # Blocked tells you what to skip if it matches an allowed or notify and also matches the block. These won't be shown. - "Thatjerk auctions, #*#" notify: # Notify tags @everyone in the channel when this matches. Good for getting notices on things you really want to know about without having notices turned on for everything in the channel. - "#*#WTS My Soul#*#" prefix: "" # If you want to prefix the message in Discord with anything. Like putting your character name in front of it if you share channels between characters. send_connected: false # Should Discord tell you when you connect. If you're troubleshooting turn this on, but I usually leave it off. allow_commands: true # Whether you can receive commands through this channel (commands will still only be accepted by the above user_ids). For most this is probably true show_command_response: 2000 # After you send a command from Discord to EQ, MQ2Discord automatically sends all chat messages back to Discord. This is how long in milliseconds you want it to do that. Longer is great for viewing chat, horrible for combat spam. Default is 2 seconds and of course you can always keep it going with /echo hi repeatedly
lol -- I don't actually recall, but it's a good question. When you find out, let us know~

- name: Sending Commands
id: 5##############2
allowed:
[]
blocked:
- "#*# begins singing #*#"
- "#*# begins casting #*#"
- "#*# healed #*# for #*#"
- "#*# tries to punch #*#"
- "#*# tries to kick #*#"
- "#*# kick #*# for #*#"
- "#*# kicks #*# for #*#"
- "#*# hit #*# for #*#"
- "#*# hits #*# for #*#"
- "#*# slash #*# for #*#"
- "#*# slashes #*# for #*#"
- "#*# crush #*# for #*#"
- "#*# crushed #*# for #*#"
- "#*# crushes #*# for #*#"
- "#*# punches #*# for #*#"
- "#*# struck by #*# for #*#"
- "#*# pierced by #*# for #*#"
- "#*# is struck by #*#"
- "#*# missed #*#"
notify:
[]
prefix: ""
send_connected: false
allow_commands: true
show_command_response: 500
# AM
I use it on Next.So MQ2Discord haven't been ported to MQNext yet?
It has and its awesome. Few things have changed in it. Not sure the old INI will work in the Next versionSo MQ2Discord haven't been ported to MQNext yet?
Yeah i do see some JSON files, changed them to ini extension and all working again, thanks guys.The old one was json, not ini. Possible I don’t copy json files using the migrator. I’d have to look. Check to see if your MQNext config folder has your discord json files and if not copy them over from your old folder.
