Discord presence plugin doesn't seem to be working.

[Firehawke]

Here's a sample run, no errors appear in the output but Discord is definitely not detecting the MAME instance and showing any information:

Logs snipped out...

[cracyc]

Works for me. Just to make sure, you are using the Discord client and not just a normal web browser right?

[Firehawke]

Yep, I'm on the Discord client. I'll get a screenshot here in a moment.

Picture snipped out...

Note that it picks up other games just fine.

[cracyc]

If you aren't using the latest copy of discord/init.lua from the master branch, try it because extra verbose output was recently added and it doesn't need a new mame build to work.

[Firehawke]

A quick overview of my setup---
This is Windows 10. I have a c:\emu\mame-indev folder that uses symlinks and junctions to point to the c:\msys64\src\mame\ folders and files for the critical necessary stuff (plugins, bgfx, etc) so that I can keep my source tree clean and my INI and other user-created stuff over in the c:\emu\mame-indev structure.

Since I just went back to origin/master this morning, my plugins are up to date with mamedev/mame as of three hours ago. The only thing that's NOT up to date is my actual .EXE, which is perhaps too old. That's why I'm doing a recompile now.

[Firehawke]

Okay, still not working. Turned off local firewall to be on the safe side.

With the latest version, and with highscores DAT support turned on so we can see if other plugins are working:

Logs snipped out...

We never even get the other error messages. I might need to trace the script with debug output to see where it stops.

[Firehawke]

Tracing the script is showing that it's running and apparently generating data (I removed the comments on the output lines) but it's not actually changing anything on Discord itself. Hmmm. Discord says it doesn't detect a game (and yes, the feature is on..)

[Firehawke]

...and then suddenly it started working out of nowhere. Seems like a Discord-side issue. I'm going to close this.

[cracyc]

If you started discord while the old version of mame was running then it might have taken the named pipe filename that discord uses. The new version won't try to create the pipe if it doesn't exist so if that is what happened, it shouldn't happen any more.