You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After operating ownfoil for more than 6 months now (great job btw!) I decided to cleanup some other shops that were inactive and no longer necessary.
However after doing so, nothing appears from my local ownfoil. Browsing to the instance shows many 0b folders with no name, with the shop.json and shop.tfl files appearing in the root directory.
New Games appears empty while before deleting the other sources everything was ok.
How could this affect ownfoil? I have deleted & re-added, restarted the docker container but with the same result.
Thanks
The text was updated successfully, but these errors were encountered:
its on the "roadmap":
Web UI
list of available games/saves
list of available updates/DLC not present on the shop, based on currently present games.
operation on files
i guess the new game folder / 0 kb are some cached stuff from other shops.
tinfoil detects games / updates and has no update file / connection to the source, so it shows 0kb
im gonna guess u have a folder with games in it that looks like \switch games\fun game\fun game.nsp. i noticed that if u take fun games.nsp and place it in switch games, it should show up in a new tab to the left called new games up only if u also dont already have the game installed.
Hi
After operating ownfoil for more than 6 months now (great job btw!) I decided to cleanup some other shops that were inactive and no longer necessary.
However after doing so, nothing appears from my local ownfoil. Browsing to the instance shows many 0b folders with no name, with the shop.json and shop.tfl files appearing in the root directory.
New Games appears empty while before deleting the other sources everything was ok.
How could this affect ownfoil? I have deleted & re-added, restarted the docker container but with the same result.
Thanks
The text was updated successfully, but these errors were encountered: