Closed dcode closed 8 months ago
I am having the same issue. I about panicked a little XD, i have people paying for a Play By Post and your module helps keep the server going ;) luckily did things the old fashioned way. Following to see resolution.
Huh, I was wondering what the issue was. My imports on my machine were fine, and it wasn't showing a diff on the source controls, so I was confused as well. Thanks for finding the problem.
Edit: I've been trying to find the bug for the past few hours. I'll have it fixed in a few.
Are you all on The Forge? I've found this is only happening on The Forge for me. As of v2.0.0 no status messages are sent from Forge servers, even though the module is on. No settings appear in Configure Settings. Hosting on Foundry, status messages are sent, and the settings appear. I've reverted to 1.1.11 on The Forge for now, but on Foundry 2.0.0 is working as expected.
Yes, looks like Forge is run on something Linux-adjacent. I've also confirmed it to not work on Forge now that I had the chance to test it there. I guess I shouldn't rely too much on VSCode changing imports when I move stuff around now. This is fixed.
For context, I run my games on a Windows machine, which isn't case-sensitive when it comes to imports. Though I do still work with case-sensitivity in mind most of the time, but I guess this one slipped through the cracks. Sorry for the inconvenience, guys. I also wasn't expecting to be making a release on my phone while I'm on a trip, so it took longer than it should, lol.
You are doing great, thank you for all you do @loki123
On Mon, Mar 25, 2024 at 3:51 PM Loki123 @.***> wrote:
For context, I run my games on a Windows machine, which isn't case-sensitive when it comes to imports. Though I do still work with case-sensitivity in mind most of the time, but I guess this one slipped through the cracks. Sorry for the inconvenience, guys. I also wasn't expecting to be making a release on my phone while I'm on a trip, so it took longer than it should, lol.
— Reply to this email directly, view it on GitHub https://github.com/therealguy90/foundrytodiscord/issues/36#issuecomment-2018790061, or unsubscribe https://github.com/notifications/unsubscribe-auth/BB2I5KJTBBC62UYWO4IUSVDY2B53FAVCNFSM6AAAAABFG6C2HGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJYG44TAMBWGE . You are receiving this because you commented.Message ID: @.***>
Describe the bug
EDIT: I was able to track down the specific issue to running this on a case-sensitive file system. In the v2.0.0 release, the file
scripts/helpers/monitor/serverStatus.mjs
was renamed to all lowercase, but the import is still camel-cased. I'm leaving the rest of my comments as context in case someone else runs into this and wants to troubleshoot it.Renaming the file back to
serverStatus.mjs
fixed this issue.This could be user error, but I'm not sure how to fix it, if so. After upgrading to 2.0.0, the module doesn't show up in settings. I did clear my browser state at one point due to some other silliness not related to this module.
I've tried to unload the module from the world. I removed the module from Foundry and re-installed, but nothing has gotten it to reappear.
To Reproduce Steps to reproduce the behavior:
Expected behavior I expected the settings to be present.
Screenshots
No error from the module itself, because it doesn't load due to this 404.
Additional context
I dumped my current active modules in console with:
List of my current active modules and versions: