Describe the bug
I have encountered a similar situation to Issue #28 #28 on with the scenario that the cache will regenerate on every single boot, however instead of "more culling" being the probable cause of the dashloader cache regen it is the current dev build of tinkers construct fabric https://github.com/Alpha-s-Stuff/TinkersConstruct which i've narrowed down as causing this behaviour. Have provided a log with only dashloader + tinkers (second boot, post-cache generation) so the log is readable.

To Reproduce
Steps to reproduce the behavior:

1. Fresh 0.14.9 Fabric installation
2. Boot with Fabric API + Dashloader + Tinker's
3. Quit, reboot and establish if the cache regenerates without a change to the pack
4. ---> Cache regeneration on boot each time

Expected behavior
Regular behavior, boot once ---> subsequent loads with no changes to configs / mods / files should load using the already created cache.
This is seen within the logs of a successful boot as dashloader will print the load, file reading, asset models cached etc. instead of generation.

Context (please complete the following information):

• DashLoader 4.1.2 - 1.18.2
• Minecraft 1.18.2
• Fabric 0.14.9

Full Logs
https://paste.gg/p/anonymous/f2a499018f8e4513a6b07a1c8bac3ff5