Hello! I have a reproducible issue with custom system package installation on my Forge account.
Server version:
Foundry VTT v13 Stable 9, Build 351.
An empty D&D 5e world starts normally on the same account.
However, every custom system package installed through a GitHub manifest gets stuck indefinitely at:
“Optimizing the package”
The task-status endpoint repeatedly returns:
{“success”:true,“status”:“optimize”}
I originally tested this with my full Digimon system. I then created progressively smaller diagnostic releases:
- Full system package
- Same system without compendium packs
- A minimal shell package with only:
- system.json
- template.json
The minimal shell ZIP is only 606 bytes.
It has:
- a unique system id;
- no scripts;
- no assets;
- no packs;
- no data files;
- no modules;
- no fonts;
- no world content.
The GitHub release asset is confirmed uploaded and intact. I downloaded it again from GitHub and verified that the SHA-256 hash matches the original uploaded ZIP exactly.
The minimal diagnostic manifest is:
The minimal diagnostic release asset is:
Even this 606-byte shell package gets stuck in the same “Optimizing the package” loop.
When I create an empty world using one of the partially installed packages, it reaches “Migrating World Data 100%”, but the /join request eventually fails with HTTP 524.
Could you please inspect and clear any stuck package-optimization task, package cache, or account/region-specific issue affecting external manifest installs on my account?
I can provide task IDs, timestamps, browser Network responses, and Forge server logs if needed.