You're likely to find as I did the MPL's don't work. It's a path issue, put
the path on the mpl name and it will work like:
gx /mystic/scripts/blackjack
that will make blackjack work normally. If I look at ./mystic -cfg all the paths look correct, but the scripts one doesn't work. I found that as the 1liners uses a different path and worked. So I added the path to blackjack
and it started working too.

--- Mystic BBS v1.12 A38 2018/01/01 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)

The /mystic/scripts path appears not to work for all the MPLs. I had to add
the path to the MPLs like:
GX /mystic/scripts/blackjack
to get them to work. The paths look OK under ./mystic -cfg so no clue what happened. Without the path you get the usual version error message (mismatch). I'm also having issues with /W showing two of each login, perhaps it's the in and out showing?
So far that's the only issues from upgrading. If I build from scratch those problems don't show up. Only from upgrade. So possibly from users.dat or mystic.dat even though upgrade was run. What else should I try under mutil to fix them? They were backed up first.

--- Mystic BBS v1.12 A38 2018/01/01 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)

You're likely to find as I did the MPL's don't work. It's a path issue, put the path on the mpl name and it will work like:
gx /mystic/scripts/blackjack

Sounds like you have your scripts path set wrong.

--- Mystic BBS v1.12 A39 2018/01/04 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

The /mystic/scripts path appears not to work for all the MPLs. I had to add the path to the MPLs like:
GX /mystic/scripts/blackjack
to get them to work. The paths look OK under ./mystic -cfg so no clue
what happened. Without the path you get the usual version error message (mismatch). I'm also having issues with /W showing two of each login,

Its difficult to imagine what you might have going on there, but a Version mismatch is completely unrelated to the directory. If it says version mismatch then there is not a directory issue, because its finding the file. It also means you didn't properly upgrade.

I can assure you with 1000% certainty that this is not something broken in Mystic, as literally no one's BBS would be working properly, yet not a single person is reporting any related issues with A38.

For the record the paths are not in the System Configuration paths, its in
the Theme paths.

--- Mystic BBS v1.12 A39 2018/01/04 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 01/04/18, g00r00 said the following...

Sounds like you have your scripts path set wrong.

Yes, that was my first thought too, but it's set to the default. Something
else is going on, I'm not sure what. Ahh, read the second message and that explains it totally: Theme Paths. I'd forgotten about them and I opened the Edit Theme and it shows /mystic/lbscripts/ as I was thinking about separating the MPLs, so I didn't update that path! That's it. I'll recompile them as I should have in the first place. It happens to work as they are the same MPLs
at present. Thanks for the heads up on it being stored in Themes.

--- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
* Origin: Workpoint (21:1/145.3)