• You've discovered RedGuides, an EverQuest multi-boxing and scripting community 🧙‍♀️⚙️. We want you to play several EQ characters at once, come join us and say hello! 👋

  • A TLP without truebox has thawed (Very Vanilla ready)
    Frostreaver
MQ2Discord

Release MQ2Discord

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.
 
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.

I asked that same question :D.
Someone said to use separate channels for each discord user.
 
That is the feature in the newer version, but alynel never got that to Live. The beta of it is that one posted earlier, but it hasn't been compiled in a while.
 
I receive messages but I cant send commands and text. What is my problem please ?

Regards,

Mick.
 
Think that probably has something to do with your discord bot permissions, but I don't know really. I had to get a discord bot. I totally suck at making them myself.
 
In your json file:

"user": "7XXXXXXXX0"

In mine, this is set to my discord account ID and not the bots ID

Check there. (IRC this was my problem with a similar issue)
 
Can someone explain how the wildcards in the allow/block sections works? Is #*# 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.
 
anyone got "You are not authorized to issue commands on this channel" when you were issue a "/" command to channel after migrated to MQNext?

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

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.

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.
 
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)
 
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.
 
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)
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.
 
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.
I got it.
the config file changed from "MQ2Discord_servername_charname.jason" to "MQ2Discord.yaml" after migrated to MQNext!
but when I filled all info to "MQ2Discord.yaml" and reload it. 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

the "MQ2Discord.yaml" format different from "MQ2Discord_servername_charname.jason"

can anyone help to explain how to config it?


here is MQ2Discord.yaml below:


token: YourTokenHere
user_ids:
- YourUserIdHere
characters:
servername_charname:
- name: CharChannel (This field is ignored)
id:
YourCharacterChannelHere
allowed:
[]
blocked:
[]
notify:
[]
prefix: ""
send_connected: true
allow_commands: true
show_command_response: 2000
servers:
{}
classes:
{}
groups:
- name: YourGroup
characters:
- servername_charname
- server_OtherCharInGroup
- server_OneMore
channels:
- name: Deaths
id: YourGroupChannelHere
allowed:
- You have been slain by
blocked:
[]
notify:
[]
prefix: "[${Me.Name}]"
send_connected: true
allow_commands: false
show_command_response: 0
all:
- name: TellsChannel
id: YourChannelForTellsHere
allowed:
- tells you
blocked:
- "|${Me.Pet.DisplayName}| tells you#*#"
notify:
[]
prefix: "[${EverQuest.Server}_${Me.Name}]"
send_connected: true
allow_commands: false

show_command_response: 0



Thanks very much!
 
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.
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)
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#*#"
Note the above list isn't complete and I just made it up so it might be wrong.

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):
INI:
[Settings]
SaveByChar=1
AlertPerSpeaker=1
[Default]
AlertCommand=/discord process [MQ2Say] ${SayWnd.LastSpeaker} says: ${SayWnd.LastSay}
Since MQ2Say already does NPC checks and the like this will severely limit false positives.

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.
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.

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
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
 
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)
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#*#"
Note the above list isn't complete and I just made it up so it might be wrong.

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):
INI:
[Settings]
SaveByChar=1
AlertPerSpeaker=1
[Default]
AlertCommand=/discord process [MQ2Say] ${SayWnd.LastSpeaker} says: ${SayWnd.LastSay}
Since MQ2Say already does NPC checks and the like this will severely limit false positives.


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

@Knightly MQ2Say is great, I did not know it could do that.
I may add Zone to the process command so that I can block PoK and Guild lobby
 
Yeah, that's what I love about configurable commands. You just add whatever you want to fit your needs. SL968 did a great job on MQ2Say.
 
With the
show_command_response
option.

When its reflecting the chat back to Discord will it honor your block settings? I made the mistake of testing a command while in combat. I forgot how long I have to wait before discord will start excepting connections again.

Thinking I may want to try and block some of that combat spam
 
lol -- I don't actually recall, but it's a good question. When you find out, let us know~

Does not appear to :(
I setup a separate channel and cut the response time to 500 and still seems to send it all.
Unless I did something wrong
INI:
    - 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

[CODE lang="ini" title="Discord Chatter"]MQ2-ChatBot
— Today at ##:## AM
You tell your party, 'hello'
MyCleric bashes a restless wurm for 435
MyWarrior slashes a restless wurm for 4774
MyWarrior missed a restless wurm
MyWarrior slashes a restless wurm for 113862
MyWarrior slashes a restless wurm for 120386
MyWarrior missed a restless wurm
MyWarrior slashes a restless wurm for 66223
bash a restless wurm for 17650
MyBst begins casting Beramos' Maelstrom.
You hit a restless wurm for 1587 points of magic damage by Overdrive Punch.
A restless wurm is struck by heavy punch!
missed a restless wurm
crush a restless wurm for 63589
MyCleric hit a restless wurm for 8190 points of chromatic damage by Arcane Symphony Strike II. (Lucky Critical)
A restless wurm quivers as a bolt of energy surges through them.
MyCleric hit a restless wurm for 1347 points of chromatic damage by Arcane Symphony Strike II. (Twincast)
A restless wurm quivers as a bolt of energy surges through them.
MyCleric crushes a restless wurm for 1637
MyCleric crushes a restless wurm for 1357
MyBard crushes a restless wurm for 7802
MyBard crushes a restless wurm for 36147
MyBard crushes a restless wurm for 8787
MyBard missed a restless wurm
MyBard crushes a restless wurm for 38836
MyBard slashes a restless wurm for 5548
MyBard slashes a restless wurm for 31780
MyBard slashes a restless wurm for 26014[/CODE]

It's not like its a big deal, did not have the feed back in the old version and I operated fine without it.
 
Yes, that behavior is intended and controlled via the setting. JerkChicken’s question was whether it honored the block or not (which they confirmed it doesn’t). I think that is probably also intentional, although I can see how in combat that would be an issue.
 
Anyone else having issues with the MQ2Discord plugin crashing them after the latest patch?

I'm getting an endless loop of "[MQ2Discord] Exception: invalid string position" and ultimately crashing.
 
MQ2. I didn't change my config at all, was working perfectly fine Tuesday then when I reloaded after the server maintenance on Wednesday it was borked. I've checked my .json file, compared it to other's files, etc. Deleted and reinstalled the mq2discord.dll. Not sure what's going on.
 
Does anyone know what the maximum number of characters that you can have connected to discord at the same time is?

With my groups + tradeskill farming characters + Auction house alts + guys in POK, and a few other things I think I am hitting a limit, maybe they think I am DOS attacking them :(

I had to remove the ALL section to get it working again.

Is there a way to set that up, I wanted them all connected so that I could see tells to each character in the all channel.
I guess I need to setup relay tells again.
 
It's less about the maximum number of characters that you can have connected and more about the number of reconnections you make and the number of messages that you send. If you're zoning frequently on a lot of characters, MQ2Discord disconnects and reconnects you between zones which, with a lot of characters, will cause you to hit the connection limit.

Similarly, if you're not filtering out chat, you can hit the message send limit.
 
It loads normally but complains no channel set for this char. I copied old MQ2 configs to MQNext folder using the migrator, anything else i should look for?
 
I am no expert with MQ2Discord, but in MQ2 i used an INI file and in Next its a yaml file
I reconfigured mine from scratch. It wasn't too hard since I had it working previously (with the INI).


Edited Response:
I am no expert with MQ2Discord, but in MQ2 i used an json (mine had a file for every toon) file and in Next I have a single yaml file
I reconfigured mine from scratch. It wasn't too hard since I had it working previously (with the JSON).

Once you understand what IDs to put where its not so bad. Then again; Everything is easy once you know how
 
Last edited:
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.
 
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.
Yeah i do see some JSON files, changed them to ini extension and all working again, thanks guys.
 
You might be able to remove the old one. I just have a "MQ2Discord.yaml" file for Next an it works will.
I was wrong about there being an INI. (Thank you Knightly)
 
I keep getting combat spam on mine it's going pingpingpingpingping what can I do to stop the combat spam ;-;
 
Release MQ2Discord

Users who are viewing this thread

Back
Top
Cart