💡 Feature Summary
Current behavior downloads the CLI again whenever the source changes, which is understandable for safety and compatibility.
A possible improvement could be checking whether the required CLI is already present and matches the expected version/hash before downloading again.
🔀 Alternatives Considered
This could be added as a toggle to switch between them
For safer patching environment this could be turned off by default
📊 Priority
🟢 Nice to have
🏷️ Feature Category
🔧 New Functionality
✅ Benefits
- Reduces repeated data usage when switching sources if the required CLI has not changed
- Helps users on limited mobile data connections
- Avoids unnecessary download time before patching
- Keeps current safety intact if validation is done before reuse
🛠️ Implementation Ideas
Before downloading assets, Enhancify could check whether a CLI file already exists locally(enhancify folder).
- Compare the cached CLI version or checksum with the required one for the selected source
- If it matches exactly, reuse it
- If it is missing, outdated, corrupted, or incompatible, delete and download fresh assets as usual
This keeps the current safe behavior while only skipping downloads when the existing file is already verified.
✔️ Checklist
💡 Feature Summary
Current behavior downloads the CLI again whenever the source changes, which is understandable for safety and compatibility.
A possible improvement could be checking whether the required CLI is already present and matches the expected version/hash before downloading again.
🔀 Alternatives Considered
This could be added as a toggle to switch between them
For safer patching environment this could be turned off by default
📊 Priority
🟢 Nice to have
🏷️ Feature Category
🔧 New Functionality
✅ Benefits
🛠️ Implementation Ideas
Before downloading assets, Enhancify could check whether a CLI file already exists locally(enhancify folder).
This keeps the current safe behavior while only skipping downloads when the existing file is already verified.
✔️ Checklist