[BUG] Uncaught (in promise) Error: Directory does not exist...

[Shadow-355]

Describe the bug
The module doesn't appear to be running properly at all and is tossing an uncaught error in the console.

Steps to reproduce

1. Launch Game
2. Press F12 to open the console.
3. Click on any actor or token.
4. See error

Versions:

• Token Action HUD Core: v1.4.20
• Token Action HUD System: D&D 5E v1.4.13
• System: DnD5E v2.3.1
• Foundry VTT: v11.313
• Browser: Brave Version 1.58.137 Cromium: 117.0.5938.153 (Official Build) (64-bit)

Additional context
I have already attempted Foundry with only the Core, 5E, and socketlib modules installed, but the problem still persists... I'm unsure what is causing the issue. I also attempted to use a different browser, Edge, but this also didn't work. My final attempt to fix the issue was to reinstall the modules, which didn't seem to fix it either.

I've attached the console log from that session in case that helps to diagnose the issue. The error occurs in the console at line 169.
ActionHud Error.log

[madseumas]

For a workaround you can try going to Foundry's settings menu (Game Settings->Configure Settings), then Token Action HUD Core, then Layouts, and "Reset All Layouts". I think I had that happen to me before and was able to get rid of the error that way.

[Shadow-355]

I'll give that a try and report back, thanks!

[Shadow-355]

That didn't seem to work, I received this error when I attempted that. The HUD still didn't display.

[Shadow-355]

I managed to hotfix the issue. By creating the missing folder directories, mainly the "/Data/modules/token-action-hud-core/storage/vonkora/actor" and "/Data/modules/token-action-hud-core/storage/vonkora/user" folders, the module began working again without issue.

While this doesn't fix the odd underlying issue of the problem occurring in the first place, at least the issue can be fixed by creating those folders manually. I wonder if those folders can be automatically created to replace them in the event they are deleted in the future.

[Larkinabout]

While this doesn't fix the odd underlying issue of the problem occurring in the first place, at least the issue can be fixed by creating those folders manually. I wonder if those folders can be automatically created to replace them in the event they are deleted in the future.

That does already happen on reload:

[Shadow-355]

Strange. They weren't automatically created in my case, I'm unsure why that occurred. On the bright side, it's now working without issue now that the folders are present.