• 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

Overview Updates (12) Reviews (6) Discussion
YAML: 
    - name:
      id:
      allowed:
        - "[MQ2Discord]#*#"
        - "[MQ2]#*#"
        - "#*# tells you,#*#"
        - "#*#out of character#*#"
        - "#*#shouts,#*#"
      blocked:
        - "#*#|${Me.CleanName}|`s pet#*#"
        - "#*#|${Me.Pet.CleanName}| says,#*#"
        - "#*#|${Me.Pet.CleanName}| tells you,#*#"
        - "#*#|${Me.Pet.CleanName}| told you,#*#"
        - "#*# #*# says,#*#"
        - "#*# #*# tells you,#*#"
        - "#*# #*# told you,#*#"
        - "#*#You will not evade me#*#"
        
      notify:
        []
      prefix: ""
      send_connected: true
      allow_commands: true
      show_command_response: 2000

I still get combat spam from group, any idea why?
 
When you update your config file make sure you issue /discord reload

Otherwise it won’t take effect until the next time you log in.
 
q8reflex said:
YAML: 
    - name:
      id:
      allowed:
        - "[MQ2Discord]#*#"
        - "[MQ2]#*#"
        - "#*# tells you,#*#"
        - "#*#out of character#*#"
        - "#*#shouts,#*#"
      blocked:
        - "#*#|${Me.CleanName}|`s pet#*#"
        - "#*#|${Me.Pet.CleanName}| says,#*#"
        - "#*#|${Me.Pet.CleanName}| tells you,#*#"
        - "#*#|${Me.Pet.CleanName}| told you,#*#"
        - "#*# #*# says,#*#"
        - "#*# #*# tells you,#*#"
        - "#*# #*# told you,#*#"
        - "#*#You will not evade me#*#"
       
      notify:
        []
      prefix: ""
      send_connected: true
      allow_commands: true
      show_command_response: 2000

I still get combat spam from group, any idea why?
Click to expand...

Do you mean you get combat spam if you type something into discord following the command? If so I believe lowering that show_command_response figure is what you want.
 
Hello !

I know this is unsupported but I was just wondering if anyone had an idea and could help with my issue.

So I can load the plugin just fine. I set it up and it works flawlessly the first time around. However, when I exit the game and try to reload my toons, I get this error ;

err.png

I'm obviously willing to provide more information if someone wants to look into things.

It would seem that the only way to make it work again is to change Macroquest.ini line to ; "mq2discord=1" so it does not load the plugin.

I can then redo the setup from inside the game.

Really annoying because its working wonderfully otherwise ;)

Thanks
 
alynel said:
6. Enter your the token for your bot (see linked guide earlier) with
Rich (BB code): 
/discord token <token>
Click to expand...
/discord token is not a valid command. I did the /discord reload command and that did nothing, I did /discord process and my clients all crashed. There weren't other commands available to try.

1635877446098.png


So I guess my question is, how do you set this up for the first time? I am using 'Next' currently. I see some folks using this on Next, so... yeah. The plugin doesn't have the token command available to it.

It looks like there was a MQ2Discord.yaml file generated in the config folder. Inside is only 1 character of the 3 that all crashed when I was trying setup commands. So... something worked-ish, but the command method for filling this file out doesn't exist.
 
Last edited:
ppmastah said:
I know this is unsupported but I was just wondering if anyone had an idea and could help with my issue.
Click to expand...
This is probably an issue in your json file. But switch to MQNext and I'll help you troubleshoot it. There's been a lot of work done on this in Next.
BlankStare said:
So I guess my question is, how do you set this up for the first time? I am using 'Next' currently. I see some folks using this on Next, so... yeah. The plugin doesn't have the token command available to it.
Click to expand...
If you had a json file, it'll convert. The MQ version is based on alynel's updated work though, so the old steps might not be useful. I personally just edited the yaml file, I don't think I've ever tried to set it up from scratch, but the file it generates should work. Start with the file that was generated and fill in the blanks.
 
Knightly said:
If you had a json file, it'll convert. The MQ version is based on alynel's updated work though, so the old steps might not be useful. I personally just edited the yaml file, I don't think I've ever tried to set it up from scratch, but the file it generates should work. Start with the file that was generated and fill in the blanks.
Click to expand...

Thanks, I'll fiddle around with it. ;)
 
This is one of my favorite plugins by far. Just fired it up after migrating over to next and it appears that I'm receiving incoming messages just fine. However, when I type a command it tells me, "You are not authorized to issue commands on this channel". Anyone run into this problem or know what might have broken?
 
Redbot updated MQ2Discord with a new update entry:

July 17, 2021

  • The /discord command will now be parsed
  • Added /discord debug which will toggle debug mode on or off
  • Added /discord process which will allow you to send a command to be processed by your config
  • Added an OutputDebug function
  • Updated the token check function to include new Discord token formats (and extend to Z)
  • Rearranged code a bit
  • Still working on the unload issue
Click to expand...

Read the rest of this update entry...
 
Anyone else having issues with Mq2Discord using Next?

I think I've got everything set up correctly, everything looks ok in the yaml file. But no messages come through to my toons. /discord process crashes the client, similar to a previous user.

The token is correct and the channels for the toons are correct, am I possibly missing something or are other people having issues too?

Thanks.
 
My MQ2Discorde is compiling just fine and able to load it in game. I have my YAML correct and get no errors when I /discord reload, however mine are not actually connecting to my discord server either. Might be something with the 64-bit switchover. Mine was working perfect as of the patch before 64-bit (very appreciative for the app btw!)
 
Issuing /discord process crashes immediately. Issuing /discord reload just gives an error message..

I've been trying to get this setup for over an hour and no luck. I even made a fresh .yaml file. With debug on I can see the plugin is giving errors out. For example line 16 column #, removing the space between connected: & true (connected:true) will give the next error.
 
Mine works as well as /discord reload it just doesn't actually send any message to discord like it used to
 
Is on my list. If I don’t get to it today I’ll get to it on the weekend for sure.

Edit: “for sure” meaning “probably” in this case
 
I'm having trouble figuring this out since it seems to not be updated in terms of how to set it up. Is this a single yaml now or? I'm using Next.
 
It’s a single yaml, but the move to 64 bit broke the connection. MQ2Discord believes it is connected but Discord is not receiving the messages.

I spent some time yesterday unwinding it and then got sidetracked because I was trying to replace sleepy-discord which was several hours of time.

The sleepy discord demo doesn’t seem to be working in 64 bit so I need to spend some time figuring out why.
 
Knightly said:
It’s a single yaml, but the move to 64 bit broke the connection. MQ2Discord believes it is connected but Discord is not receiving the messages.

I spent some time yesterday unwinding it and then got sidetracked because I was trying to replace sleepy-discord which was several hours of time.

The sleepy discord demo doesn’t seem to be working in 64 bit so I need to spend some time figuring out why.
Click to expand...
Oh! I see, interesting.

When possible, do you think you could show an example of a multiple character setup in the single YAML?


Also, thanks for all you do. xx
 
RedQueen said:
When possible, do you think you could show an example of a multiple character setup in the single YAML?
Click to expand...
Here's one example:
gitlab.com

docs/MQ2Discord.example.yaml · master · Alynel / MQ2Discord · GitLab

GitLab.com
gitlab.com gitlab.com

You can send characters to the same channel or different channels, using the channel ID. You can also have one character send things to multiple channels, but I didn't make an example for that, I just did a basic one to get people started.

Discord is fixed, I let Redbot know to pull the submodule so it can be in the next build.
 
If you ever want to do that, you can grab the build from the MQ Discord. I don’t really like sending DLLs around randomly.
 
Tried updating to latest build and even pulling source/compiling myself, but am still not connecting properly.

Even went as far as to rebuild a whole new bot just in case it was an issue there and still nada.

Tried the /discord process command and it is still crashing as well
 
If /discord process is still crashing for you, are you sure you’re on latest source?

The process command was just something I added in so I could test things, the actual format of the command is /discord process Some Text Here

But the last update should have fixed it so it will give you an error if you send it nothing.

You can also /discord debug and it will echo back output.
 
Got it figured out. For some reason it is requiring me to have MQ run as admin in compatibility for it to connect. I'll weave through my internal stuff, probably something on my end with my own code additions.
 
You must log in or register to reply here.
Release MQ2Discord
Next unread thread 🦁

Users who are viewing this thread

Total: 1 (members: 0, guests: 1)
Back
Top
Cart

Cart

Total -