ВЕРСИИ (1303)

## What's Changed * Couple fixes for mod loader quirks, mostly forge. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v5.0.0-rc.6...v5.0.0-rc.7

## What's Changed ### Security * The server's TLS certificate is now checked against Mozilla's OneCRL revocation list. Certificates issued by revoked or compromised certificate authorities, such as the recently compromised eMudhra intermediates, are no longer trusted. The list ships with the mod, so the check also works offline, and it refreshes in the background. * Certificates issued by a public CA are now checked against that CA's revocation list before they're trusted automatically. * The server's TLS private key is now saved readable only by its owner. Existing keys stay as they are and log a warning. * The server no longer replaces its TLS key and certificate when one of them is missing. If `cert.crt` exists without `key.pem`, hosting won't start until you restore the key or remove both files. * Downloads now stop as soon as they run past the size listed in the modpack, so a malicious server or mirror can no longer fill memory or disk. ### In-game updates * Updates, switches and removals made in-game now always apply right away on best effort basis. Files the game holds open (common on Windows) are finished after the game exits or on the next launch. * Several changes in one session now stack properly. Each starts where the previous one left off, so the next launch always ends up on the latest one. * Fixed updates getting stuck on a file that was already deleted. * A Minecraft or loader version switch is now written to the launcher together with the files of its update, so the launcher never starts versions the installed mods weren't made for. * If an update's files stay held through two restarts, AutoModpack stops asking and loads what's installed, trying again every launch. From the third launch like that, an in-game message tells you the update is still unfinished. ### Other changes * Fixed a crash with Sinytra Connector and mixin-booster in the same pack on Forge/NeoForge. Early-service mods that run in place now get each other's names and their own launch options the way ModLauncher gives them, so mixin-booster stands down for Connector like it does in `mods/`. If one of them fails to load, the crash now names it. * The update helper and the restart window now run in a separate JVM. * Faster boots and update checks on large packs. * Quieter console logs. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v5.0.0-rc.5...v5.0.0-rc.6

## Security patch - The server's TLS certificate is now checked against Mozilla's OneCRL revocation list. Certificates issued by revoked or compromised certificate authorities, such as the recently compromised eMudhra intermediates, are no longer trusted. The list ships with the mod, so the check also works offline, and it refreshes in the background. - Certificates issued by a public CA are now checked against that CA's revocation list before they're trusted automatically. - The server's TLS private key is now saved readable only by its owner. Existing keys stay as they are and log a warning. - The server no longer replaces its TLS key and certificate when one of them is missing. If `cert.crt` exists without `key.pem`, hosting won't start until you restore the key or remove both files. - Downloads now stop as soon as they run past the size listed in the modpack, so a malicious server or mirror can no longer fill memory or disk. Clients on 4.0.7 can join servers running 4.0.5, 4.0.6 and 4.0.7. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.6...v4.0.7

## Security patch - The server's TLS certificate is now checked against Mozilla's OneCRL revocation list. Certificates issued by revoked or compromised certificate authorities, such as the recently compromised eMudhra intermediates, are no longer trusted. The list ships with the mod, so the check also works offline, and it refreshes in the background. - Certificates issued by a public CA are now checked against that CA's revocation list before they're trusted automatically. - The server's TLS private key is now saved readable only by its owner. Existing keys stay as they are and log a warning. - The server no longer replaces its TLS key and certificate when one of them is missing. If `cert.crt` exists without `key.pem`, hosting won't start until you restore the key or remove both files. - Downloads now stop as soon as they run past the size listed in the modpack, so a malicious server or mirror can no longer fill memory or disk. Clients on 4.0.7 can join servers running 4.0.5, 4.0.6 and 4.0.7. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.6...v4.0.7

## Security patch - The server's TLS certificate is now checked against Mozilla's OneCRL revocation list. Certificates issued by revoked or compromised certificate authorities, such as the recently compromised eMudhra intermediates, are no longer trusted. The list ships with the mod, so the check also works offline, and it refreshes in the background. - Certificates issued by a public CA are now checked against that CA's revocation list before they're trusted automatically. - The server's TLS private key is now saved readable only by its owner. Existing keys stay as they are and log a warning. - The server no longer replaces its TLS key and certificate when one of them is missing. If `cert.crt` exists without `key.pem`, hosting won't start until you restore the key or remove both files. - Downloads now stop as soon as they run past the size listed in the modpack, so a malicious server or mirror can no longer fill memory or disk. Clients on 4.0.7 can join servers running 4.0.5, 4.0.6 and 4.0.7. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.6...v4.0.7

## Security patch - The server's TLS certificate is now checked against Mozilla's OneCRL revocation list. Certificates issued by revoked or compromised certificate authorities, such as the recently compromised eMudhra intermediates, are no longer trusted. The list ships with the mod, so the check also works offline, and it refreshes in the background. - Certificates issued by a public CA are now checked against that CA's revocation list before they're trusted automatically. - The server's TLS private key is now saved readable only by its owner. Existing keys stay as they are and log a warning. - The server no longer replaces its TLS key and certificate when one of them is missing. If `cert.crt` exists without `key.pem`, hosting won't start until you restore the key or remove both files. - Downloads now stop as soon as they run past the size listed in the modpack, so a malicious server or mirror can no longer fill memory or disk. Clients on 4.0.7 can join servers running 4.0.5, 4.0.6 and 4.0.7. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.6...v4.0.7

## Security patch - The server's TLS certificate is now checked against Mozilla's OneCRL revocation list. Certificates issued by revoked or compromised certificate authorities, such as the recently compromised eMudhra intermediates, are no longer trusted. The list ships with the mod, so the check also works offline, and it refreshes in the background. - Certificates issued by a public CA are now checked against that CA's revocation list before they're trusted automatically. - The server's TLS private key is now saved readable only by its owner. Existing keys stay as they are and log a warning. - The server no longer replaces its TLS key and certificate when one of them is missing. If `cert.crt` exists without `key.pem`, hosting won't start until you restore the key or remove both files. - Downloads now stop as soon as they run past the size listed in the modpack, so a malicious server or mirror can no longer fill memory or disk. Clients on 4.0.7 can join servers running 4.0.5, 4.0.6 and 4.0.7. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.6...v4.0.7

## Security patch - The server's TLS certificate is now checked against Mozilla's OneCRL revocation list. Certificates issued by revoked or compromised certificate authorities, such as the recently compromised eMudhra intermediates, are no longer trusted. The list ships with the mod, so the check also works offline, and it refreshes in the background. - Certificates issued by a public CA are now checked against that CA's revocation list before they're trusted automatically. - The server's TLS private key is now saved readable only by its owner. Existing keys stay as they are and log a warning. - The server no longer replaces its TLS key and certificate when one of them is missing. If `cert.crt` exists without `key.pem`, hosting won't start until you restore the key or remove both files. - Downloads now stop as soon as they run past the size listed in the modpack, so a malicious server or mirror can no longer fill memory or disk. Clients on 4.0.7 can join servers running 4.0.5, 4.0.6 and 4.0.7. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.6...v4.0.7

## Security patch - The server's TLS certificate is now checked against Mozilla's OneCRL revocation list. Certificates issued by revoked or compromised certificate authorities, such as the recently compromised eMudhra intermediates, are no longer trusted. The list ships with the mod, so the check also works offline, and it refreshes in the background. - Certificates issued by a public CA are now checked against that CA's revocation list before they're trusted automatically. - The server's TLS private key is now saved readable only by its owner. Existing keys stay as they are and log a warning. - The server no longer replaces its TLS key and certificate when one of them is missing. If `cert.crt` exists without `key.pem`, hosting won't start until you restore the key or remove both files. - Downloads now stop as soon as they run past the size listed in the modpack, so a malicious server or mirror can no longer fill memory or disk. Clients on 4.0.7 can join servers running 4.0.5, 4.0.6 and 4.0.7. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.6...v4.0.7

## Security patch - The server's TLS certificate is now checked against Mozilla's OneCRL revocation list. Certificates issued by revoked or compromised certificate authorities, such as the recently compromised eMudhra intermediates, are no longer trusted. The list ships with the mod, so the check also works offline, and it refreshes in the background. - Certificates issued by a public CA are now checked against that CA's revocation list before they're trusted automatically. - The server's TLS private key is now saved readable only by its owner. Existing keys stay as they are and log a warning. - The server no longer replaces its TLS key and certificate when one of them is missing. If `cert.crt` exists without `key.pem`, hosting won't start until you restore the key or remove both files. - Downloads now stop as soon as they run past the size listed in the modpack, so a malicious server or mirror can no longer fill memory or disk. Clients on 4.0.7 can join servers running 4.0.5, 4.0.6 and 4.0.7. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.6...v4.0.7

## Security patch - The server's TLS certificate is now checked against Mozilla's OneCRL revocation list. Certificates issued by revoked or compromised certificate authorities, such as the recently compromised eMudhra intermediates, are no longer trusted. The list ships with the mod, so the check also works offline, and it refreshes in the background. - Certificates issued by a public CA are now checked against that CA's revocation list before they're trusted automatically. - The server's TLS private key is now saved readable only by its owner. Existing keys stay as they are and log a warning. - The server no longer replaces its TLS key and certificate when one of them is missing. If `cert.crt` exists without `key.pem`, hosting won't start until you restore the key or remove both files. - Downloads now stop as soon as they run past the size listed in the modpack, so a malicious server or mirror can no longer fill memory or disk. Clients on 4.0.7 can join servers running 4.0.5, 4.0.6 and 4.0.7. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.6...v4.0.7

## Security patch - The server's TLS certificate is now checked against Mozilla's OneCRL revocation list. Certificates issued by revoked or compromised certificate authorities, such as the recently compromised eMudhra intermediates, are no longer trusted. The list ships with the mod, so the check also works offline, and it refreshes in the background. - Certificates issued by a public CA are now checked against that CA's revocation list before they're trusted automatically. - The server's TLS private key is now saved readable only by its owner. Existing keys stay as they are and log a warning. - The server no longer replaces its TLS key and certificate when one of them is missing. If `cert.crt` exists without `key.pem`, hosting won't start until you restore the key or remove both files. - Downloads now stop as soon as they run past the size listed in the modpack, so a malicious server or mirror can no longer fill memory or disk. Clients on 4.0.7 can join servers running 4.0.5, 4.0.6 and 4.0.7. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.6...v4.0.7

## Security patch - The server's TLS certificate is now checked against Mozilla's OneCRL revocation list. Certificates issued by revoked or compromised certificate authorities, such as the recently compromised eMudhra intermediates, are no longer trusted. The list ships with the mod, so the check also works offline, and it refreshes in the background. - Certificates issued by a public CA are now checked against that CA's revocation list before they're trusted automatically. - The server's TLS private key is now saved readable only by its owner. Existing keys stay as they are and log a warning. - The server no longer replaces its TLS key and certificate when one of them is missing. If `cert.crt` exists without `key.pem`, hosting won't start until you restore the key or remove both files. - Downloads now stop as soon as they run past the size listed in the modpack, so a malicious server or mirror can no longer fill memory or disk. Clients on 4.0.7 can join servers running 4.0.5, 4.0.6 and 4.0.7. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.6...v4.0.7

## Security patch - The server's TLS certificate is now checked against Mozilla's OneCRL revocation list. Certificates issued by revoked or compromised certificate authorities, such as the recently compromised eMudhra intermediates, are no longer trusted. The list ships with the mod, so the check also works offline, and it refreshes in the background. - Certificates issued by a public CA are now checked against that CA's revocation list before they're trusted automatically. - The server's TLS private key is now saved readable only by its owner. Existing keys stay as they are and log a warning. - The server no longer replaces its TLS key and certificate when one of them is missing. If `cert.crt` exists without `key.pem`, hosting won't start until you restore the key or remove both files. - Downloads now stop as soon as they run past the size listed in the modpack, so a malicious server or mirror can no longer fill memory or disk. Clients on 4.0.7 can join servers running 4.0.5, 4.0.6 and 4.0.7. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.6...v4.0.7

## Security patch - The server's TLS certificate is now checked against Mozilla's OneCRL revocation list. Certificates issued by revoked or compromised certificate authorities, such as the recently compromised eMudhra intermediates, are no longer trusted. The list ships with the mod, so the check also works offline, and it refreshes in the background. - Certificates issued by a public CA are now checked against that CA's revocation list before they're trusted automatically. - The server's TLS private key is now saved readable only by its owner. Existing keys stay as they are and log a warning. - The server no longer replaces its TLS key and certificate when one of them is missing. If `cert.crt` exists without `key.pem`, hosting won't start until you restore the key or remove both files. - Downloads now stop as soon as they run past the size listed in the modpack, so a malicious server or mirror can no longer fill memory or disk. Clients on 4.0.7 can join servers running 4.0.5, 4.0.6 and 4.0.7. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.6...v4.0.7

## Security patch - The server's TLS certificate is now checked against Mozilla's OneCRL revocation list. Certificates issued by revoked or compromised certificate authorities, such as the recently compromised eMudhra intermediates, are no longer trusted. The list ships with the mod, so the check also works offline, and it refreshes in the background. - Certificates issued by a public CA are now checked against that CA's revocation list before they're trusted automatically. - The server's TLS private key is now saved readable only by its owner. Existing keys stay as they are and log a warning. - The server no longer replaces its TLS key and certificate when one of them is missing. If `cert.crt` exists without `key.pem`, hosting won't start until you restore the key or remove both files. - Downloads now stop as soon as they run past the size listed in the modpack, so a malicious server or mirror can no longer fill memory or disk. Clients on 4.0.7 can join servers running 4.0.5, 4.0.6 and 4.0.7. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.6...v4.0.7

## Security patch - The server's TLS certificate is now checked against Mozilla's OneCRL revocation list. Certificates issued by revoked or compromised certificate authorities, such as the recently compromised eMudhra intermediates, are no longer trusted. The list ships with the mod, so the check also works offline, and it refreshes in the background. - Certificates issued by a public CA are now checked against that CA's revocation list before they're trusted automatically. - The server's TLS private key is now saved readable only by its owner. Existing keys stay as they are and log a warning. - The server no longer replaces its TLS key and certificate when one of them is missing. If `cert.crt` exists without `key.pem`, hosting won't start until you restore the key or remove both files. - Downloads now stop as soon as they run past the size listed in the modpack, so a malicious server or mirror can no longer fill memory or disk. Clients on 4.0.7 can join servers running 4.0.5, 4.0.6 and 4.0.7. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.6...v4.0.7

## Security patch - The server's TLS certificate is now checked against Mozilla's OneCRL revocation list. Certificates issued by revoked or compromised certificate authorities, such as the recently compromised eMudhra intermediates, are no longer trusted. The list ships with the mod, so the check also works offline, and it refreshes in the background. - Certificates issued by a public CA are now checked against that CA's revocation list before they're trusted automatically. - The server's TLS private key is now saved readable only by its owner. Existing keys stay as they are and log a warning. - The server no longer replaces its TLS key and certificate when one of them is missing. If `cert.crt` exists without `key.pem`, hosting won't start until you restore the key or remove both files. - Downloads now stop as soon as they run past the size listed in the modpack, so a malicious server or mirror can no longer fill memory or disk. Clients on 4.0.7 can join servers running 4.0.5, 4.0.6 and 4.0.7. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.6...v4.0.7

## Security patch - The server's TLS certificate is now checked against Mozilla's OneCRL revocation list. Certificates issued by revoked or compromised certificate authorities, such as the recently compromised eMudhra intermediates, are no longer trusted. The list ships with the mod, so the check also works offline, and it refreshes in the background. - Certificates issued by a public CA are now checked against that CA's revocation list before they're trusted automatically. - The server's TLS private key is now saved readable only by its owner. Existing keys stay as they are and log a warning. - The server no longer replaces its TLS key and certificate when one of them is missing. If `cert.crt` exists without `key.pem`, hosting won't start until you restore the key or remove both files. - Downloads now stop as soon as they run past the size listed in the modpack, so a malicious server or mirror can no longer fill memory or disk. Clients on 4.0.7 can join servers running 4.0.5, 4.0.6 and 4.0.7. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.6...v4.0.7

## Security patch - The server's TLS certificate is now checked against Mozilla's OneCRL revocation list. Certificates issued by revoked or compromised certificate authorities, such as the recently compromised eMudhra intermediates, are no longer trusted. The list ships with the mod, so the check also works offline, and it refreshes in the background. - Certificates issued by a public CA are now checked against that CA's revocation list before they're trusted automatically. - The server's TLS private key is now saved readable only by its owner. Existing keys stay as they are and log a warning. - The server no longer replaces its TLS key and certificate when one of them is missing. If `cert.crt` exists without `key.pem`, hosting won't start until you restore the key or remove both files. - Downloads now stop as soon as they run past the size listed in the modpack, so a malicious server or mirror can no longer fill memory or disk. Clients on 4.0.7 can join servers running 4.0.5, 4.0.6 and 4.0.7. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.6...v4.0.7

## Security patch - The server's TLS certificate is now checked against Mozilla's OneCRL revocation list. Certificates issued by revoked or compromised certificate authorities, such as the recently compromised eMudhra intermediates, are no longer trusted. The list ships with the mod, so the check also works offline, and it refreshes in the background. - Certificates issued by a public CA are now checked against that CA's revocation list before they're trusted automatically. - The server's TLS private key is now saved readable only by its owner. Existing keys stay as they are and log a warning. - The server no longer replaces its TLS key and certificate when one of them is missing. If `cert.crt` exists without `key.pem`, hosting won't start until you restore the key or remove both files. - Downloads now stop as soon as they run past the size listed in the modpack, so a malicious server or mirror can no longer fill memory or disk. Clients on 4.0.7 can join servers running 4.0.5, 4.0.6 and 4.0.7. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.6...v4.0.7

## Security patch - The server's TLS certificate is now checked against Mozilla's OneCRL revocation list. Certificates issued by revoked or compromised certificate authorities, such as the recently compromised eMudhra intermediates, are no longer trusted. The list ships with the mod, so the check also works offline, and it refreshes in the background. - Certificates issued by a public CA are now checked against that CA's revocation list before they're trusted automatically. - The server's TLS private key is now saved readable only by its owner. Existing keys stay as they are and log a warning. - The server no longer replaces its TLS key and certificate when one of them is missing. If `cert.crt` exists without `key.pem`, hosting won't start until you restore the key or remove both files. - Downloads now stop as soon as they run past the size listed in the modpack, so a malicious server or mirror can no longer fill memory or disk. Clients on 4.0.7 can join servers running 4.0.5, 4.0.6 and 4.0.7. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.6...v4.0.7

## Security patch - The server's TLS certificate is now checked against Mozilla's OneCRL revocation list. Certificates issued by revoked or compromised certificate authorities, such as the recently compromised eMudhra intermediates, are no longer trusted. The list ships with the mod, so the check also works offline, and it refreshes in the background. - Certificates issued by a public CA are now checked against that CA's revocation list before they're trusted automatically. - The server's TLS private key is now saved readable only by its owner. Existing keys stay as they are and log a warning. - The server no longer replaces its TLS key and certificate when one of them is missing. If `cert.crt` exists without `key.pem`, hosting won't start until you restore the key or remove both files. - Downloads now stop as soon as they run past the size listed in the modpack, so a malicious server or mirror can no longer fill memory or disk. Clients on 4.0.7 can join servers running 4.0.5, 4.0.6 and 4.0.7. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.6...v4.0.7

## Security patch - The server's TLS certificate is now checked against Mozilla's OneCRL revocation list. Certificates issued by revoked or compromised certificate authorities, such as the recently compromised eMudhra intermediates, are no longer trusted. The list ships with the mod, so the check also works offline, and it refreshes in the background. - Certificates issued by a public CA are now checked against that CA's revocation list before they're trusted automatically. - The server's TLS private key is now saved readable only by its owner. Existing keys stay as they are and log a warning. - The server no longer replaces its TLS key and certificate when one of them is missing. If `cert.crt` exists without `key.pem`, hosting won't start until you restore the key or remove both files. - Downloads now stop as soon as they run past the size listed in the modpack, so a malicious server or mirror can no longer fill memory or disk. Clients on 4.0.7 can join servers running 4.0.5, 4.0.6 and 4.0.7. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.6...v4.0.7

## Security patch - The server's TLS certificate is now checked against Mozilla's OneCRL revocation list. Certificates issued by revoked or compromised certificate authorities, such as the recently compromised eMudhra intermediates, are no longer trusted. The list ships with the mod, so the check also works offline, and it refreshes in the background. - Certificates issued by a public CA are now checked against that CA's revocation list before they're trusted automatically. - The server's TLS private key is now saved readable only by its owner. Existing keys stay as they are and log a warning. - The server no longer replaces its TLS key and certificate when one of them is missing. If `cert.crt` exists without `key.pem`, hosting won't start until you restore the key or remove both files. - Downloads now stop as soon as they run past the size listed in the modpack, so a malicious server or mirror can no longer fill memory or disk. Clients on 4.0.7 can join servers running 4.0.5, 4.0.6 and 4.0.7. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.6...v4.0.7

## Security patch - The server's TLS certificate is now checked against Mozilla's OneCRL revocation list. Certificates issued by revoked or compromised certificate authorities, such as the recently compromised eMudhra intermediates, are no longer trusted. The list ships with the mod, so the check also works offline, and it refreshes in the background. - Certificates issued by a public CA are now checked against that CA's revocation list before they're trusted automatically. - The server's TLS private key is now saved readable only by its owner. Existing keys stay as they are and log a warning. - The server no longer replaces its TLS key and certificate when one of them is missing. If `cert.crt` exists without `key.pem`, hosting won't start until you restore the key or remove both files. - Downloads now stop as soon as they run past the size listed in the modpack, so a malicious server or mirror can no longer fill memory or disk. Clients on 4.0.7 can join servers running 4.0.5, 4.0.6 and 4.0.7. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.6...v4.0.7

## Security patch - The server's TLS certificate is now checked against Mozilla's OneCRL revocation list. Certificates issued by revoked or compromised certificate authorities, such as the recently compromised eMudhra intermediates, are no longer trusted. The list ships with the mod, so the check also works offline, and it refreshes in the background. - Certificates issued by a public CA are now checked against that CA's revocation list before they're trusted automatically. - The server's TLS private key is now saved readable only by its owner. Existing keys stay as they are and log a warning. - The server no longer replaces its TLS key and certificate when one of them is missing. If `cert.crt` exists without `key.pem`, hosting won't start until you restore the key or remove both files. - Downloads now stop as soon as they run past the size listed in the modpack, so a malicious server or mirror can no longer fill memory or disk. Clients on 4.0.7 can join servers running 4.0.5, 4.0.6 and 4.0.7. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.6...v4.0.7

## Security patch - The server's TLS certificate is now checked against Mozilla's OneCRL revocation list. Certificates issued by revoked or compromised certificate authorities, such as the recently compromised eMudhra intermediates, are no longer trusted. The list ships with the mod, so the check also works offline, and it refreshes in the background. - Certificates issued by a public CA are now checked against that CA's revocation list before they're trusted automatically. - The server's TLS private key is now saved readable only by its owner. Existing keys stay as they are and log a warning. - The server no longer replaces its TLS key and certificate when one of them is missing. If `cert.crt` exists without `key.pem`, hosting won't start until you restore the key or remove both files. - Downloads now stop as soon as they run past the size listed in the modpack, so a malicious server or mirror can no longer fill memory or disk. Clients on 4.0.7 can join servers running 4.0.5, 4.0.6 and 4.0.7. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.6...v4.0.7

## Security patch - The server's TLS certificate is now checked against Mozilla's OneCRL revocation list. Certificates issued by revoked or compromised certificate authorities, such as the recently compromised eMudhra intermediates, are no longer trusted. The list ships with the mod, so the check also works offline, and it refreshes in the background. - Certificates issued by a public CA are now checked against that CA's revocation list before they're trusted automatically. - The server's TLS private key is now saved readable only by its owner. Existing keys stay as they are and log a warning. - The server no longer replaces its TLS key and certificate when one of them is missing. If `cert.crt` exists without `key.pem`, hosting won't start until you restore the key or remove both files. - Downloads now stop as soon as they run past the size listed in the modpack, so a malicious server or mirror can no longer fill memory or disk. Clients on 4.0.7 can join servers running 4.0.5, 4.0.6 and 4.0.7. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.6...v4.0.7

## Security patch - The server's TLS certificate is now checked against Mozilla's OneCRL revocation list. Certificates issued by revoked or compromised certificate authorities, such as the recently compromised eMudhra intermediates, are no longer trusted. The list ships with the mod, so the check also works offline, and it refreshes in the background. - Certificates issued by a public CA are now checked against that CA's revocation list before they're trusted automatically. - The server's TLS private key is now saved readable only by its owner. Existing keys stay as they are and log a warning. - The server no longer replaces its TLS key and certificate when one of them is missing. If `cert.crt` exists without `key.pem`, hosting won't start until you restore the key or remove both files. - Downloads now stop as soon as they run past the size listed in the modpack, so a malicious server or mirror can no longer fill memory or disk. Clients on 4.0.7 can join servers running 4.0.5, 4.0.6 and 4.0.7. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.6...v4.0.7

## Security patch - The server's TLS certificate is now checked against Mozilla's OneCRL revocation list. Certificates issued by revoked or compromised certificate authorities, such as the recently compromised eMudhra intermediates, are no longer trusted. The list ships with the mod, so the check also works offline, and it refreshes in the background. - Certificates issued by a public CA are now checked against that CA's revocation list before they're trusted automatically. - The server's TLS private key is now saved readable only by its owner. Existing keys stay as they are and log a warning. - The server no longer replaces its TLS key and certificate when one of them is missing. If `cert.crt` exists without `key.pem`, hosting won't start until you restore the key or remove both files. - Downloads now stop as soon as they run past the size listed in the modpack, so a malicious server or mirror can no longer fill memory or disk. Clients on 4.0.7 can join servers running 4.0.5, 4.0.6 and 4.0.7. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.6...v4.0.7

## Security patch - The server's TLS certificate is now checked against Mozilla's OneCRL revocation list. Certificates issued by revoked or compromised certificate authorities, such as the recently compromised eMudhra intermediates, are no longer trusted. The list ships with the mod, so the check also works offline, and it refreshes in the background. - Certificates issued by a public CA are now checked against that CA's revocation list before they're trusted automatically. - The server's TLS private key is now saved readable only by its owner. Existing keys stay as they are and log a warning. - The server no longer replaces its TLS key and certificate when one of them is missing. If `cert.crt` exists without `key.pem`, hosting won't start until you restore the key or remove both files. - Downloads now stop as soon as they run past the size listed in the modpack, so a malicious server or mirror can no longer fill memory or disk. Clients on 4.0.7 can join servers running 4.0.5, 4.0.6 and 4.0.7. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.6...v4.0.7

## What's Changed * Improved `auto-exclude-server-side-mods` behavior, it now excludes only **dedicated** server mods, server mods that may run on client are shipped by default, it will no longer end up excluding mods that potentially clients might need to have in order to connect to the server. To exclude more, use `exclude` list. * Added `/automodpack generate replace-notes [text...]` to caption the live generation without publishing a new one. Without text it reads `automodpack/host-modpack/patch-notes.md` and clears the file after a successful replace. * [Windows] Fixed update apply stalling when a managed file stays locked or an empty directory cannot be removed. * [Windows] Locked files are now recognized by error type, so the update helper behaves the same on non-English locale. * Fixed resumable downloads losing stream alignment when the server answers with a whole file instead of the requested range. * Fixed a download that finished without every slice on disk, and a served object whose length does not match what the client expected. * A mod that cannot be mounted as a zip is treated as unreadable instead of aborting the scan. * Fixed client storage maintenance counting history objects that were never fetched as missing. * Filesystems that cannot make a file read-only no longer fail the protection step. AutoModpack probes the filesystem once and skips enforcement there. * Fixed couple UI bugs like modpack '🎵' button breaking after visiting sub-menu or input screen exiting after button press with some mods. * A failing command worker no longer crashes the server, and command replies are sent on the server thread. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v5.0.0-rc.4...v5.0.0-rc.5

## What's Changed * Replaced the pack-wide `auto-exclude-server-side-mods` boolean with a per-group `auto-exclude-server-side-mods` enum, taking `DISABLED` , `METADATA` or `PLATFORMS`. Fresh and existing configs default to `METADATA` (pre rc.3 behavior). Set `PLATFORMS` on a group to also ask Modrinth and CurseForge APIs (rc.3 behavior) * Config enum values now accept any case * Interrupted updates resume from files they already wrote, and locked or unreadable live files wait for the update helper after the game exits * The update helper starts as soon as the game cannot finish the apply, and waits for the game to exit * Added handle for a new `EarlyBootstrapper` 26.3 neoforge service * Fixed couple edge cases related to instance timeline restore **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v5.0.0-rc.3...v5.0.0-rc.4

## What's Changed * Replaced `modpack.<category>.<id>.required` and `modpack.<category>.<id>.default-selected` booleans with a single `modpack.<category>.<id>.selection` enum, taking `REQUIRED`, `RECOMMENDED` or `OPTIONAL` * The `auto-exclude-server-side-mods` option now takes to account results from Modrinth and CurseForge APIs when we cannot make a decision based solely on the included mod metadata * Improved UI elements to look more readable on wider range of high contrast resourcepacks * Improved download source selection algorithm, to measure all available download paths for each file and use the best available while always prioritizing Modrinth or CurseForge * Custom waiting music is now previewable in the modpack screen * Fixed an loader edge case with some connector mods * Fixed not properly recognizing mods containing ImmediateWindowProvider service to force-copy on neo/forge * Shortened generated-copies file location to avoid hitting default windows publishable path limit * Improved Minecraft version detection on startup to work on more non standard environments * Fixed couple edge cases related to instance timeline **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v5.0.0-rc.2...v5.0.0-rc.3

## What's Changed * Direct connection now respects the `#amp1=` as ephemeral pins * The fallback codepath for when hardlinks are unavailable has been improved * CurseForge-only mods that come without a download URL now show up as matched * AutoModpack now nags you about old leftover v4 files * Empty modpack generation no longer crashes the server * Switching between modpack groups has been improved * AutoModpack now checks for updates when the server's advertisement never arrives * Sped up update application, planning, downloads, and contract serving **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v5.0.0-rc.1...v5.0.0-rc.2

# AutoModpack 5.0.0-rc.1 It took a while, but here it is: the first release candidate of v5. Pretty much everything changed. Core modpack concepts (groups!), config format, transfer protocol, storage layout, the UIs, you name it. This is the ~~biggest~~ update AutoModpack has ever gotten. It's actually also the smallest update since the entire mod now fits in just 3.8MB and it works on all supported targets! ## Before you upgrade - v5 drops Minecraft 1.19.4, 1.20.4, 1.20.6, and 1.21.3, and adds 26.3 (Fabric and NeoForge). - Releases ship one jar for every supported loader and game version. - Human files are `automodpack/server.conf` and `automodpack/client.conf`. The format is a small HOCON subset. Your existing config will get auto-migrated to new format and the old file will be renamed with `.backup` suffix. - The server's TLS certificate lives in `automodpack/credentials/`. There is no auto-copy from v4 paths. If files are missing, the server generates a new certificate. - The `nonModpackFilesToDelete` list is gone. Deletions are ownership-checked, with no toggle. - `forceCopyFilesToStandardLocation` is also gone, `editable` list inherited its functionality. ## Modpack content and groups - The modpack is now declared as groups. Each group has `from-server` (previously called `syncedFiles` - content from the server root. `host-modpack/<id>/` is included in full), `exclude` (list of file paths excluded from both `from-server` and `host-modpack`), and `editable` (previously `allowEditsInFiles`). Groups also have a display name, description, required, default-selected, `requires`, `breaks-with`, and `compatible-platforms`. `main` is the required core. Extra groups are optional. - Players pick optional groups in a Group Selection screen, with file counts, sizes, dependency and conflict text, and a platform dropdown. The choice persists across updates. - Editable files always live in the game directory, mods included. A mod marked editable lands in the player's mods folder. It stays replaceable and removable, and it survives updates until the server changes its content. - A server can ship a custom waiting track as `automodpack/host-modpack/waiting-music.ogg`. Clients stream it during downloads and cache it. ## Publishing (server) - Publishing is a journalled workflow. `/automodpack generate preview` shows a diff without publishing. `notes` attaches patch notes (or write them to `patch-notes.md`). `if-content` publishes only while the pack still matches a named state. `history` lists past generations. `revert <seq>` rolls back by publishing an old state as a new generation. - The server keeps every published generation in an append-only journal, with file bytes in a content store. `generate storage collect confirm` is the only deletion. It prints what it removed. - `/automodpack generate export-http` writes the pack as plain files (`head`, `journal`, `objects/`) for a static HTTPS host. It refuses while `validate-secrets` is on, since a static mirror cannot check them. Files that Modrinth or CurseForge already serve are omitted unless you pass `--all`. - `/automodpack groups` inspects the pack: one summary line per group, and `/automodpack groups <id>` for a single group's rules, files, and published state. ## Connectivity - All connection modes use one HTTP wire: GET over TLS for the pack head, journal, and objects, with the login-issued secret as a bearer header, resumable range requests, unchanged-check short circuits, and zstd with a gzip fallback. - You can now host your modpack statically without minecraft server even. Any static HTTP host or S3 works. - New default HOLEPUNCH connection mode behaves like a minecraft login protocol which now make AutoModpack work behind strict Minecraft proxies. ## Client: pack management - The multiplayer screen gains a Modpacks button (hideable). It opens an installed-pack manager: update, repair, stop and resume syncing, deactivate, remove, and switch between installed packs. - A server running with `require-modpack` off offers its pack at login, before anything transfers: sync it, join without it, or cancel. - Every pack action is previewed first. A review screen shows added, changed, and removed files with sources, filters, and hashes, and states whether a restart is needed. A first install asks for consent, names how many mod files were matched on Modrinth or CurseForge, and gates unverified jars behind a risk acknowledgement. - A Pack History screen lists every published generation of the installed pack with its patch notes, and can restore an older version offline. Restoring detaches the pack from syncing until you resume. - An Instance timeline records every state this instance lived (installs, updates, rollbacks, repairs, and automatic captures of your files before a change). Restore the whole instance or single files, save copies out, or forget old snapshots to free space. - A Repair action runs a cache-bypassing integrity check, asks before resetting edited files, can finish missing files from the server later, and prints a receipt. - A Local storage screen runs a confirmed cleanup with a receipt and a storage integrity pass. - Pinned mods: a player can pin mod ids that keep loading their version from their own mods folder even when the pack ships a mod with the same id. The player's jar survives even if the pack later drops that mod. - Declining an update keeps local state with a detached warning. Joining through a new address asks before trusting it. - A pack that needs a different Minecraft version or modloader is handled per launcher. Prism, MultiMC forks, and Pandora get their instance switched. Other launchers, get a manual-switch notice and no broken state. ## Security - The modpack connection's certificate is matched to the Minecraft hostname you join. SRV records and advertised endpoints are treated as routes only. - Servers with a DNSSEC-signed domain can publish their certificate fingerprint as a `_automodpack` TXT record. Clients look it up through DNS-over-HTTPS (Cloudflare and Quad9) and accept it only when both resolvers return the same DNSSEC-validated record. `/automodpack host fingerprint dns` prints the record. - `/automodpack host fingerprint share` produces a copy-paste join address with the fingerprint embedded (e.g. `play.example.com#amp1=...`). Importing it pins the exact certificate and leaves a working vanilla entry in the server list. - A bootstrap file pre-configures a client with the server address, endpoint, and certificate pin, and can carry a provisioning secret for one-shot installs (`/automodpack host bootstrap pin|install`). ## Performance - Downloaded files are stored once by hash and hard-linked into place. Identical files are shared across packs and instances. - Hash results and parsed mod metadata are cached per file and reused across launches. - The download scheduler interleaves large and small files per source, which removes the stall near the end of a transfer. The speed readout is smoothed. - Server-side pack generation reuses the hash caches. - The jar is leaner: pure-Java compression instead of bundled native zstd libraries, the JDK HTTP client instead of a shaded Apache HttpClient, custom simple toml parser instead of toml4j, removed bundled fabric api, waiting music replaced for a smaller noteblock remaster. - Updates are computed in full before anything is touched, then committed as a crash-recoverable transaction. Locked files are handled by a detached helper after the game exits. A runaway update-restart loop is stopped after two looped attempts. ## Fixes and changes - Each pack gets a stable 7-character id, so a server-side rename or server address change no longer requires modpack redownload. - The server configuration's `requireMagicPackets` boolean became `connection-mode` with `HOLEPUNCH` as the default: the pack rides the Minecraft login protocol with no second open port. `MAGIC` and `HTTP` use dedicated or external listeners. - Forge and NeoForge mods that must load early (coremods, language providers, transformation services) load straight from the modpack folder. That retires the force copied mod jars like sodium and the `forceCopyFilesToStandardLocation` option. - Configuration, secret, and state writes land atomically, so a crash mid-save cannot leave a half-written file. - Removed Herobrine. - Broken installs fail with a categorized error screen instead of running half-loaded. Corrupt stored objects are repaired rather than served. A failed join after an applied update suggests a restart, and the restart screen lists the reasons. - The loader-version swap wait on MultiMC and Prism is the remainder of a five-second window since launch, not a flat five seconds. - A "Preparing update" screen sits between certificate acceptance and the download, with cancel. And much more... Full changelog: https://github.com/Skidamek/AutoModpack/compare/v4.0.5...v5.0.0-rc.1

## Security patch - Stronger modpack download warnings. - Requires a 10-second acknowledgement before downloading JAR files that cannot be matched to public Modrinth or CurseForge files. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.5...v4.0.6

## Security patch - Stronger modpack download warnings. - Requires a 10-second acknowledgement before downloading JAR files that cannot be matched to public Modrinth or CurseForge files. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.5...v4.0.6

## Security patch - Stronger modpack download warnings. - Requires a 10-second acknowledgement before downloading JAR files that cannot be matched to public Modrinth or CurseForge files. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.5...v4.0.6

## Security patch - Stronger modpack download warnings. - Requires a 10-second acknowledgement before downloading JAR files that cannot be matched to public Modrinth or CurseForge files. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.5...v4.0.6

## Security patch - Stronger modpack download warnings. - Requires a 10-second acknowledgement before downloading JAR files that cannot be matched to public Modrinth or CurseForge files. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.5...v4.0.6

## Security patch - Stronger modpack download warnings. - Requires a 10-second acknowledgement before downloading JAR files that cannot be matched to public Modrinth or CurseForge files. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.5...v4.0.6

## Security patch - Stronger modpack download warnings. - Requires a 10-second acknowledgement before downloading JAR files that cannot be matched to public Modrinth or CurseForge files. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.5...v4.0.6

## Security patch - Stronger modpack download warnings. - Requires a 10-second acknowledgement before downloading JAR files that cannot be matched to public Modrinth or CurseForge files. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.5...v4.0.6

## Security patch - Stronger modpack download warnings. - Requires a 10-second acknowledgement before downloading JAR files that cannot be matched to public Modrinth or CurseForge files. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.5...v4.0.6

## Security patch - Stronger modpack download warnings. - Requires a 10-second acknowledgement before downloading JAR files that cannot be matched to public Modrinth or CurseForge files. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.5...v4.0.6

## Security patch - Stronger modpack download warnings. - Requires a 10-second acknowledgement before downloading JAR files that cannot be matched to public Modrinth or CurseForge files. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.5...v4.0.6

## Security patch - Stronger modpack download warnings. - Requires a 10-second acknowledgement before downloading JAR files that cannot be matched to public Modrinth or CurseForge files. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.5...v4.0.6

## Security patch - Stronger modpack download warnings. - Requires a 10-second acknowledgement before downloading JAR files that cannot be matched to public Modrinth or CurseForge files. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.5...v4.0.6

## Security patch - Stronger modpack download warnings. - Requires a 10-second acknowledgement before downloading JAR files that cannot be matched to public Modrinth or CurseForge files. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.5...v4.0.6

## Security patch - Stronger modpack download warnings. - Requires a 10-second acknowledgement before downloading JAR files that cannot be matched to public Modrinth or CurseForge files. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.5...v4.0.6

## Security patch - Stronger modpack download warnings. - Requires a 10-second acknowledgement before downloading JAR files that cannot be matched to public Modrinth or CurseForge files. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.5...v4.0.6

## Security patch - Stronger modpack download warnings. - Requires a 10-second acknowledgement before downloading JAR files that cannot be matched to public Modrinth or CurseForge files. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.5...v4.0.6

## Security patch - Stronger modpack download warnings. - Requires a 10-second acknowledgement before downloading JAR files that cannot be matched to public Modrinth or CurseForge files. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.5...v4.0.6

## Security patch - Stronger modpack download warnings. - Requires a 10-second acknowledgement before downloading JAR files that cannot be matched to public Modrinth or CurseForge files. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.5...v4.0.6

## Security patch - Stronger modpack download warnings. - Requires a 10-second acknowledgement before downloading JAR files that cannot be matched to public Modrinth or CurseForge files. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.5...v4.0.6

## Security patch - Stronger modpack download warnings. - Requires a 10-second acknowledgement before downloading JAR files that cannot be matched to public Modrinth or CurseForge files. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.5...v4.0.6

## Security patch - Stronger modpack download warnings. - Requires a 10-second acknowledgement before downloading JAR files that cannot be matched to public Modrinth or CurseForge files. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.5...v4.0.6

## Security patch - Stronger modpack download warnings. - Requires a 10-second acknowledgement before downloading JAR files that cannot be matched to public Modrinth or CurseForge files. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.5...v4.0.6

## Security patch - Stronger modpack download warnings. - Requires a 10-second acknowledgement before downloading JAR files that cannot be matched to public Modrinth or CurseForge files. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.5...v4.0.6

## Security patch - Stronger modpack download warnings. - Requires a 10-second acknowledgement before downloading JAR files that cannot be matched to public Modrinth or CurseForge files. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.5...v4.0.6

## Security patch - Stronger modpack download warnings. - Requires a 10-second acknowledgement before downloading JAR files that cannot be matched to public Modrinth or CurseForge files. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.5...v4.0.6

## Security patch - Stronger modpack download warnings. - Requires a 10-second acknowledgement before downloading JAR files that cannot be matched to public Modrinth or CurseForge files. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.5...v4.0.6

## Security patch - Stronger modpack download warnings. - Requires a 10-second acknowledgement before downloading JAR files that cannot be matched to public Modrinth or CurseForge files. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.5...v4.0.6

## Security patch - Stronger modpack download warnings. - Requires a 10-second acknowledgement before downloading JAR files that cannot be matched to public Modrinth or CurseForge files. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.5...v4.0.6

## Security patch - Stronger modpack download warnings. - Requires a 10-second acknowledgement before downloading JAR files that cannot be matched to public Modrinth or CurseForge files. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.5...v4.0.6

26.2 support

26.2 support

dumb 26.1.1 support

26.1 build of 4.0.5

26.1 build of 4.0.5

## What's changed - Fixed inconsistent behavior of files with same relative paths in the modpack, automodpack will now correctly prioritize files from `host-modpack` directory. - Fixed reset of `nonModpackFilesToDelete` on client modpack refresh request. - Improved `syncLoaderVersion` option expanding its support to [Pandora launcher](https://github.com/Moulberry/PandoraLauncher). - Enabled `syncLoaderVersion` by default on new instances. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.4...v4.0.5

## What's changed - Fixed inconsistent behavior of files with same relative paths in the modpack, automodpack will now correctly prioritize files from `host-modpack` directory. - Fixed reset of `nonModpackFilesToDelete` on client modpack refresh request. - Improved `syncLoaderVersion` option expanding its support to [Pandora launcher](https://github.com/Moulberry/PandoraLauncher). - Enabled `syncLoaderVersion` by default on new instances. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.4...v4.0.5

## What's changed - Fixed inconsistent behavior of files with same relative paths in the modpack, automodpack will now correctly prioritize files from `host-modpack` directory. - Fixed reset of `nonModpackFilesToDelete` on client modpack refresh request. - Improved `syncLoaderVersion` option expanding its support to [Pandora launcher](https://github.com/Moulberry/PandoraLauncher). - Enabled `syncLoaderVersion` by default on new instances. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.4...v4.0.5

## What's changed - Fixed inconsistent behavior of files with same relative paths in the modpack, automodpack will now correctly prioritize files from `host-modpack` directory. - Fixed reset of `nonModpackFilesToDelete` on client modpack refresh request. - Improved `syncLoaderVersion` option expanding its support to [Pandora launcher](https://github.com/Moulberry/PandoraLauncher). - Enabled `syncLoaderVersion` by default on new instances. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.4...v4.0.5

## What's changed - Fixed inconsistent behavior of files with same relative paths in the modpack, automodpack will now correctly prioritize files from `host-modpack` directory. - Fixed reset of `nonModpackFilesToDelete` on client modpack refresh request. - Improved `syncLoaderVersion` option expanding its support to [Pandora launcher](https://github.com/Moulberry/PandoraLauncher). - Enabled `syncLoaderVersion` by default on new instances. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.4...v4.0.5

## What's changed - Fixed inconsistent behavior of files with same relative paths in the modpack, automodpack will now correctly prioritize files from `host-modpack` directory. - Fixed reset of `nonModpackFilesToDelete` on client modpack refresh request. - Improved `syncLoaderVersion` option expanding its support to [Pandora launcher](https://github.com/Moulberry/PandoraLauncher). - Enabled `syncLoaderVersion` by default on new instances. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.4...v4.0.5

## What's changed - Fixed inconsistent behavior of files with same relative paths in the modpack, automodpack will now correctly prioritize files from `host-modpack` directory. - Fixed reset of `nonModpackFilesToDelete` on client modpack refresh request. - Improved `syncLoaderVersion` option expanding its support to [Pandora launcher](https://github.com/Moulberry/PandoraLauncher). - Enabled `syncLoaderVersion` by default on new instances. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.4...v4.0.5

## What's changed - Fixed inconsistent behavior of files with same relative paths in the modpack, automodpack will now correctly prioritize files from `host-modpack` directory. - Fixed reset of `nonModpackFilesToDelete` on client modpack refresh request. - Improved `syncLoaderVersion` option expanding its support to [Pandora launcher](https://github.com/Moulberry/PandoraLauncher). - Enabled `syncLoaderVersion` by default on new instances. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.4...v4.0.5

## What's changed - Fixed inconsistent behavior of files with same relative paths in the modpack, automodpack will now correctly prioritize files from `host-modpack` directory. - Fixed reset of `nonModpackFilesToDelete` on client modpack refresh request. - Improved `syncLoaderVersion` option expanding its support to [Pandora launcher](https://github.com/Moulberry/PandoraLauncher). - Enabled `syncLoaderVersion` by default on new instances. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.4...v4.0.5

## What's changed - Fixed inconsistent behavior of files with same relative paths in the modpack, automodpack will now correctly prioritize files from `host-modpack` directory. - Fixed reset of `nonModpackFilesToDelete` on client modpack refresh request. - Improved `syncLoaderVersion` option expanding its support to [Pandora launcher](https://github.com/Moulberry/PandoraLauncher). - Enabled `syncLoaderVersion` by default on new instances. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.4...v4.0.5

## What's changed - Fixed inconsistent behavior of files with same relative paths in the modpack, automodpack will now correctly prioritize files from `host-modpack` directory. - Fixed reset of `nonModpackFilesToDelete` on client modpack refresh request. - Improved `syncLoaderVersion` option expanding its support to [Pandora launcher](https://github.com/Moulberry/PandoraLauncher). - Enabled `syncLoaderVersion` by default on new instances. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.4...v4.0.5

## What's changed - Fixed inconsistent behavior of files with same relative paths in the modpack, automodpack will now correctly prioritize files from `host-modpack` directory. - Fixed reset of `nonModpackFilesToDelete` on client modpack refresh request. - Improved `syncLoaderVersion` option expanding its support to [Pandora launcher](https://github.com/Moulberry/PandoraLauncher). - Enabled `syncLoaderVersion` by default on new instances. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.4...v4.0.5

## What's changed - Fixed inconsistent behavior of files with same relative paths in the modpack, automodpack will now correctly prioritize files from `host-modpack` directory. - Fixed reset of `nonModpackFilesToDelete` on client modpack refresh request. - Improved `syncLoaderVersion` option expanding its support to [Pandora launcher](https://github.com/Moulberry/PandoraLauncher). - Enabled `syncLoaderVersion` by default on new instances. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.4...v4.0.5

## What's changed - Fixed inconsistent behavior of files with same relative paths in the modpack, automodpack will now correctly prioritize files from `host-modpack` directory. - Fixed reset of `nonModpackFilesToDelete` on client modpack refresh request. - Improved `syncLoaderVersion` option expanding its support to [Pandora launcher](https://github.com/Moulberry/PandoraLauncher). - Enabled `syncLoaderVersion` by default on new instances. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.4...v4.0.5

## What's changed - Fixed inconsistent behavior of files with same relative paths in the modpack, automodpack will now correctly prioritize files from `host-modpack` directory. - Fixed reset of `nonModpackFilesToDelete` on client modpack refresh request. - Improved `syncLoaderVersion` option expanding its support to [Pandora launcher](https://github.com/Moulberry/PandoraLauncher). - Enabled `syncLoaderVersion` by default on new instances. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.4...v4.0.5

## What's changed - Fixed inconsistent behavior of files with same relative paths in the modpack, automodpack will now correctly prioritize files from `host-modpack` directory. - Fixed reset of `nonModpackFilesToDelete` on client modpack refresh request. - Improved `syncLoaderVersion` option expanding its support to [Pandora launcher](https://github.com/Moulberry/PandoraLauncher). - Enabled `syncLoaderVersion` by default on new instances. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.4...v4.0.5

## What's changed - Fixed inconsistent behavior of files with same relative paths in the modpack, automodpack will now correctly prioritize files from `host-modpack` directory. - Fixed reset of `nonModpackFilesToDelete` on client modpack refresh request. - Improved `syncLoaderVersion` option expanding its support to [Pandora launcher](https://github.com/Moulberry/PandoraLauncher). - Enabled `syncLoaderVersion` by default on new instances. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.4...v4.0.5

## What's changed - Fixed inconsistent behavior of files with same relative paths in the modpack, automodpack will now correctly prioritize files from `host-modpack` directory. - Fixed reset of `nonModpackFilesToDelete` on client modpack refresh request. - Improved `syncLoaderVersion` option expanding its support to [Pandora launcher](https://github.com/Moulberry/PandoraLauncher). - Enabled `syncLoaderVersion` by default on new instances. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.4...v4.0.5

## What's changed - Fixed inconsistent behavior of files with same relative paths in the modpack, automodpack will now correctly prioritize files from `host-modpack` directory. - Fixed reset of `nonModpackFilesToDelete` on client modpack refresh request. - Improved `syncLoaderVersion` option expanding its support to [Pandora launcher](https://github.com/Moulberry/PandoraLauncher). - Enabled `syncLoaderVersion` by default on new instances. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.4...v4.0.5

## What's changed - Fixed inconsistent behavior of files with same relative paths in the modpack, automodpack will now correctly prioritize files from `host-modpack` directory. - Fixed reset of `nonModpackFilesToDelete` on client modpack refresh request. - Improved `syncLoaderVersion` option expanding its support to [Pandora launcher](https://github.com/Moulberry/PandoraLauncher). - Enabled `syncLoaderVersion` by default on new instances. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.4...v4.0.5

## What's changed - Fixed inconsistent behavior of files with same relative paths in the modpack, automodpack will now correctly prioritize files from `host-modpack` directory. - Fixed reset of `nonModpackFilesToDelete` on client modpack refresh request. - Improved `syncLoaderVersion` option expanding its support to [Pandora launcher](https://github.com/Moulberry/PandoraLauncher). - Enabled `syncLoaderVersion` by default on new instances. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.4...v4.0.5

## What's changed - Fixed inconsistent behavior of files with same relative paths in the modpack, automodpack will now correctly prioritize files from `host-modpack` directory. - Fixed reset of `nonModpackFilesToDelete` on client modpack refresh request. - Improved `syncLoaderVersion` option expanding its support to [Pandora launcher](https://github.com/Moulberry/PandoraLauncher). - Enabled `syncLoaderVersion` by default on new instances. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.4...v4.0.5

## What's changed - Fixed inconsistent behavior of files with same relative paths in the modpack, automodpack will now correctly prioritize files from `host-modpack` directory. - Fixed reset of `nonModpackFilesToDelete` on client modpack refresh request. - Improved `syncLoaderVersion` option expanding its support to [Pandora launcher](https://github.com/Moulberry/PandoraLauncher). - Enabled `syncLoaderVersion` by default on new instances. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.4...v4.0.5

## What's changed - Fixed inconsistent behavior of files with same relative paths in the modpack, automodpack will now correctly prioritize files from `host-modpack` directory. - Fixed reset of `nonModpackFilesToDelete` on client modpack refresh request. - Improved `syncLoaderVersion` option expanding its support to [Pandora launcher](https://github.com/Moulberry/PandoraLauncher). - Enabled `syncLoaderVersion` by default on new instances. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.4...v4.0.5

## What's changed - Fixed inconsistent behavior of files with same relative paths in the modpack, automodpack will now correctly prioritize files from `host-modpack` directory. - Fixed reset of `nonModpackFilesToDelete` on client modpack refresh request. - Improved `syncLoaderVersion` option expanding its support to [Pandora launcher](https://github.com/Moulberry/PandoraLauncher). - Enabled `syncLoaderVersion` by default on new instances. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.4...v4.0.5

## What's changed - Fixed inconsistent behavior of files with same relative paths in the modpack, automodpack will now correctly prioritize files from `host-modpack` directory. - Fixed reset of `nonModpackFilesToDelete` on client modpack refresh request. - Improved `syncLoaderVersion` option expanding its support to [Pandora launcher](https://github.com/Moulberry/PandoraLauncher). - Enabled `syncLoaderVersion` by default on new instances. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.4...v4.0.5

## Hot fix - Fix `nonModpackFilesToDelete` ignoring all files which have the same timestamp after first one is evaluated. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.3...v4.0.4

## Hot fix - Fix `nonModpackFilesToDelete` ignoring all files which have the same timestamp after first one is evaluated. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.3...v4.0.4

## Hot fix - Fix `nonModpackFilesToDelete` ignoring all files which have the same timestamp after first one is evaluated. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.3...v4.0.4

## Hot fix - Fix `nonModpackFilesToDelete` ignoring all files which have the same timestamp after first one is evaluated. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.3...v4.0.4

## Hot fix - Fix `nonModpackFilesToDelete` ignoring all files which have the same timestamp after first one is evaluated. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.3...v4.0.4

## Hot fix - Fix `nonModpackFilesToDelete` ignoring all files which have the same timestamp after first one is evaluated. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.3...v4.0.4

## Hot fix - Fix `nonModpackFilesToDelete` ignoring all files which have the same timestamp after first one is evaluated. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.3...v4.0.4

## Hot fix - Fix `nonModpackFilesToDelete` ignoring all files which have the same timestamp after first one is evaluated. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.3...v4.0.4

## Hot fix - Fix `nonModpackFilesToDelete` ignoring all files which have the same timestamp after first one is evaluated. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.3...v4.0.4

## Hot fix - Fix `nonModpackFilesToDelete` ignoring all files which have the same timestamp after first one is evaluated. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.3...v4.0.4

## Hot fix - Fix `nonModpackFilesToDelete` ignoring all files which have the same timestamp after first one is evaluated. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.3...v4.0.4

## Hot fix - Fix `nonModpackFilesToDelete` ignoring all files which have the same timestamp after first one is evaluated. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.3...v4.0.4

## Hot fix - Fix `nonModpackFilesToDelete` ignoring all files which have the same timestamp after first one is evaluated. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.3...v4.0.4

## Hot fix - Fix `nonModpackFilesToDelete` ignoring all files which have the same timestamp after first one is evaluated. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.3...v4.0.4

## Hot fix - Fix `nonModpackFilesToDelete` ignoring all files which have the same timestamp after first one is evaluated. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.3...v4.0.4

## Hot fix - Fix `nonModpackFilesToDelete` ignoring all files which have the same timestamp after first one is evaluated. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.3...v4.0.4

## Hot fix - Fix `nonModpackFilesToDelete` ignoring all files which have the same timestamp after first one is evaluated. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.3...v4.0.4

## Hot fix - Fix `nonModpackFilesToDelete` ignoring all files which have the same timestamp after first one is evaluated. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.3...v4.0.4

## Hot fix - Fix `nonModpackFilesToDelete` ignoring all files which have the same timestamp after first one is evaluated. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.3...v4.0.4

## Hot fix - Fix `nonModpackFilesToDelete` ignoring all files which have the same timestamp after first one is evaluated. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.3...v4.0.4

## Hot fix - Fix `nonModpackFilesToDelete` ignoring all files which have the same timestamp after first one is evaluated. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.3...v4.0.4

## Hot fix - Fix `nonModpackFilesToDelete` ignoring all files which have the same timestamp after first one is evaluated. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.3...v4.0.4

## Hot fix - Fix `nonModpackFilesToDelete` ignoring all files which have the same timestamp after first one is evaluated. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.3...v4.0.4

## Hot fix - Fix `nonModpackFilesToDelete` ignoring all files which have the same timestamp after first one is evaluated. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.3...v4.0.4

## Hot fix - Fix `nonModpackFilesToDelete` ignoring all files which have the same timestamp after first one is evaluated. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.3...v4.0.4

## Hot fix - Fix `nonModpackFilesToDelete` ignoring all files which have the same timestamp after first one is evaluated. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.3...v4.0.4

## What's Changed - **Added hash caching:** This should help reduce I/O and speed up update times on slower systems. - **Fixed issues:** Resolved netty buffer corruption and race conditions. - **Added HAProxy PROXY Protocol support.** - **New configuration options:** Implemented the `nonModpackFilesToDelete` server config option and the `allowRemoteNonModpackDeletions` client config option (opt-out). ### Configuration Details The `nonModpackFilesToDelete` feature allows you to delete specific files from the client that weren’t installed via AutoModpack before. If you simply want to remove a file from your modpack, there’s no change; just delete it from the server. This feature uses a map of two strings: the first is the relative file path, and the second is a SHA1 hash. To see these changes in action, you'll need to regenerate the modpack and restart the client. AutoModpack will check the specified path. If the path exists and the hash matches, it will delete the file. If the file doesn’t exist on the client, it will search through the parent directory for any files that match the hash. You can specify only the parent directory if you prefer, but it's best to use the most likely file path for optimal performance. Each file is evaluated only once and is treated as a deletion request; the client can disable it. All requests are timestamped, and the timestamps are saved after each evaluation to help reduce I/O. **Example configuration:** ```json "nonModpackFilesToDelete": { "/mods/lithium-fabric-0.15.1+mc1.21.1.jar": "6038cf136da413753345bf9d48e5798241439894", "/mods/": "97452cfadfde1f8f8c67838643019eabafa58fbb" }, ```

## What's Changed - **Added hash caching:** This should help reduce I/O and speed up update times on slower systems. - **Fixed issues:** Resolved netty buffer corruption and race conditions. - **Added HAProxy PROXY Protocol support.** - **New configuration options:** Implemented the `nonModpackFilesToDelete` server config option and the `allowRemoteNonModpackDeletions` client config option (opt-out). ### Configuration Details The `nonModpackFilesToDelete` feature allows you to delete specific files from the client that weren’t installed via AutoModpack before. If you simply want to remove a file from your modpack, there’s no change; just delete it from the server. This feature uses a map of two strings: the first is the relative file path, and the second is a SHA1 hash. To see these changes in action, you'll need to regenerate the modpack and restart the client. AutoModpack will check the specified path. If the path exists and the hash matches, it will delete the file. If the file doesn’t exist on the client, it will search through the parent directory for any files that match the hash. You can specify only the parent directory if you prefer, but it's best to use the most likely file path for optimal performance. Each file is evaluated only once and is treated as a deletion request; the client can disable it. All requests are timestamped, and the timestamps are saved after each evaluation to help reduce I/O. **Example configuration:** ```json "nonModpackFilesToDelete": { "/mods/lithium-fabric-0.15.1+mc1.21.1.jar": "6038cf136da413753345bf9d48e5798241439894", "/mods/": "97452cfadfde1f8f8c67838643019eabafa58fbb" }, ```

## What's Changed - **Added hash caching:** This should help reduce I/O and speed up update times on slower systems. - **Fixed issues:** Resolved netty buffer corruption and race conditions. - **Added HAProxy PROXY Protocol support.** - **New configuration options:** Implemented the `nonModpackFilesToDelete` server config option and the `allowRemoteNonModpackDeletions` client config option (opt-out). ### Configuration Details The `nonModpackFilesToDelete` feature allows you to delete specific files from the client that weren’t installed via AutoModpack before. If you simply want to remove a file from your modpack, there’s no change; just delete it from the server. This feature uses a map of two strings: the first is the relative file path, and the second is a SHA1 hash. To see these changes in action, you'll need to regenerate the modpack and restart the client. AutoModpack will check the specified path. If the path exists and the hash matches, it will delete the file. If the file doesn’t exist on the client, it will search through the parent directory for any files that match the hash. You can specify only the parent directory if you prefer, but it's best to use the most likely file path for optimal performance. Each file is evaluated only once and is treated as a deletion request; the client can disable it. All requests are timestamped, and the timestamps are saved after each evaluation to help reduce I/O. **Example configuration:** ```json "nonModpackFilesToDelete": { "/mods/lithium-fabric-0.15.1+mc1.21.1.jar": "6038cf136da413753345bf9d48e5798241439894", "/mods/": "97452cfadfde1f8f8c67838643019eabafa58fbb" }, ```

## What's Changed - **Added hash caching:** This should help reduce I/O and speed up update times on slower systems. - **Fixed issues:** Resolved netty buffer corruption and race conditions. - **Added HAProxy PROXY Protocol support.** - **New configuration options:** Implemented the `nonModpackFilesToDelete` server config option and the `allowRemoteNonModpackDeletions` client config option (opt-out). ### Configuration Details The `nonModpackFilesToDelete` feature allows you to delete specific files from the client that weren’t installed via AutoModpack before. If you simply want to remove a file from your modpack, there’s no change; just delete it from the server. This feature uses a map of two strings: the first is the relative file path, and the second is a SHA1 hash. To see these changes in action, you'll need to regenerate the modpack and restart the client. AutoModpack will check the specified path. If the path exists and the hash matches, it will delete the file. If the file doesn’t exist on the client, it will search through the parent directory for any files that match the hash. You can specify only the parent directory if you prefer, but it's best to use the most likely file path for optimal performance. Each file is evaluated only once and is treated as a deletion request; the client can disable it. All requests are timestamped, and the timestamps are saved after each evaluation to help reduce I/O. **Example configuration:** ```json "nonModpackFilesToDelete": { "/mods/lithium-fabric-0.15.1+mc1.21.1.jar": "6038cf136da413753345bf9d48e5798241439894", "/mods/": "97452cfadfde1f8f8c67838643019eabafa58fbb" }, ```

## What's Changed - **Added hash caching:** This should help reduce I/O and speed up update times on slower systems. - **Fixed issues:** Resolved netty buffer corruption and race conditions. - **Added HAProxy PROXY Protocol support.** - **New configuration options:** Implemented the `nonModpackFilesToDelete` server config option and the `allowRemoteNonModpackDeletions` client config option (opt-out). ### Configuration Details The `nonModpackFilesToDelete` feature allows you to delete specific files from the client that weren’t installed via AutoModpack before. If you simply want to remove a file from your modpack, there’s no change; just delete it from the server. This feature uses a map of two strings: the first is the relative file path, and the second is a SHA1 hash. To see these changes in action, you'll need to regenerate the modpack and restart the client. AutoModpack will check the specified path. If the path exists and the hash matches, it will delete the file. If the file doesn’t exist on the client, it will search through the parent directory for any files that match the hash. You can specify only the parent directory if you prefer, but it's best to use the most likely file path for optimal performance. Each file is evaluated only once and is treated as a deletion request; the client can disable it. All requests are timestamped, and the timestamps are saved after each evaluation to help reduce I/O. **Example configuration:** ```json "nonModpackFilesToDelete": { "/mods/lithium-fabric-0.15.1+mc1.21.1.jar": "6038cf136da413753345bf9d48e5798241439894", "/mods/": "97452cfadfde1f8f8c67838643019eabafa58fbb" }, ```

## What's Changed - **Added hash caching:** This should help reduce I/O and speed up update times on slower systems. - **Fixed issues:** Resolved netty buffer corruption and race conditions. - **Added HAProxy PROXY Protocol support.** - **New configuration options:** Implemented the `nonModpackFilesToDelete` server config option and the `allowRemoteNonModpackDeletions` client config option (opt-out). ### Configuration Details The `nonModpackFilesToDelete` feature allows you to delete specific files from the client that weren’t installed via AutoModpack before. If you simply want to remove a file from your modpack, there’s no change; just delete it from the server. This feature uses a map of two strings: the first is the relative file path, and the second is a SHA1 hash. To see these changes in action, you'll need to regenerate the modpack and restart the client. AutoModpack will check the specified path. If the path exists and the hash matches, it will delete the file. If the file doesn’t exist on the client, it will search through the parent directory for any files that match the hash. You can specify only the parent directory if you prefer, but it's best to use the most likely file path for optimal performance. Each file is evaluated only once and is treated as a deletion request; the client can disable it. All requests are timestamped, and the timestamps are saved after each evaluation to help reduce I/O. **Example configuration:** ```json "nonModpackFilesToDelete": { "/mods/lithium-fabric-0.15.1+mc1.21.1.jar": "6038cf136da413753345bf9d48e5798241439894", "/mods/": "97452cfadfde1f8f8c67838643019eabafa58fbb" }, ```

## What's Changed - **Added hash caching:** This should help reduce I/O and speed up update times on slower systems. - **Fixed issues:** Resolved netty buffer corruption and race conditions. - **Added HAProxy PROXY Protocol support.** - **New configuration options:** Implemented the `nonModpackFilesToDelete` server config option and the `allowRemoteNonModpackDeletions` client config option (opt-out). ### Configuration Details The `nonModpackFilesToDelete` feature allows you to delete specific files from the client that weren’t installed via AutoModpack before. If you simply want to remove a file from your modpack, there’s no change; just delete it from the server. This feature uses a map of two strings: the first is the relative file path, and the second is a SHA1 hash. To see these changes in action, you'll need to regenerate the modpack and restart the client. AutoModpack will check the specified path. If the path exists and the hash matches, it will delete the file. If the file doesn’t exist on the client, it will search through the parent directory for any files that match the hash. You can specify only the parent directory if you prefer, but it's best to use the most likely file path for optimal performance. Each file is evaluated only once and is treated as a deletion request; the client can disable it. All requests are timestamped, and the timestamps are saved after each evaluation to help reduce I/O. **Example configuration:** ```json "nonModpackFilesToDelete": { "/mods/lithium-fabric-0.15.1+mc1.21.1.jar": "6038cf136da413753345bf9d48e5798241439894", "/mods/": "97452cfadfde1f8f8c67838643019eabafa58fbb" }, ```

## What's Changed - **Added hash caching:** This should help reduce I/O and speed up update times on slower systems. - **Fixed issues:** Resolved netty buffer corruption and race conditions. - **Added HAProxy PROXY Protocol support.** - **New configuration options:** Implemented the `nonModpackFilesToDelete` server config option and the `allowRemoteNonModpackDeletions` client config option (opt-out). ### Configuration Details The `nonModpackFilesToDelete` feature allows you to delete specific files from the client that weren’t installed via AutoModpack before. If you simply want to remove a file from your modpack, there’s no change; just delete it from the server. This feature uses a map of two strings: the first is the relative file path, and the second is a SHA1 hash. To see these changes in action, you'll need to regenerate the modpack and restart the client. AutoModpack will check the specified path. If the path exists and the hash matches, it will delete the file. If the file doesn’t exist on the client, it will search through the parent directory for any files that match the hash. You can specify only the parent directory if you prefer, but it's best to use the most likely file path for optimal performance. Each file is evaluated only once and is treated as a deletion request; the client can disable it. All requests are timestamped, and the timestamps are saved after each evaluation to help reduce I/O. **Example configuration:** ```json "nonModpackFilesToDelete": { "/mods/lithium-fabric-0.15.1+mc1.21.1.jar": "6038cf136da413753345bf9d48e5798241439894", "/mods/": "97452cfadfde1f8f8c67838643019eabafa58fbb" }, ```

## What's Changed - **Added hash caching:** This should help reduce I/O and speed up update times on slower systems. - **Fixed issues:** Resolved netty buffer corruption and race conditions. - **Added HAProxy PROXY Protocol support.** - **New configuration options:** Implemented the `nonModpackFilesToDelete` server config option and the `allowRemoteNonModpackDeletions` client config option (opt-out). ### Configuration Details The `nonModpackFilesToDelete` feature allows you to delete specific files from the client that weren’t installed via AutoModpack before. If you simply want to remove a file from your modpack, there’s no change; just delete it from the server. This feature uses a map of two strings: the first is the relative file path, and the second is a SHA1 hash. To see these changes in action, you'll need to regenerate the modpack and restart the client. AutoModpack will check the specified path. If the path exists and the hash matches, it will delete the file. If the file doesn’t exist on the client, it will search through the parent directory for any files that match the hash. You can specify only the parent directory if you prefer, but it's best to use the most likely file path for optimal performance. Each file is evaluated only once and is treated as a deletion request; the client can disable it. All requests are timestamped, and the timestamps are saved after each evaluation to help reduce I/O. **Example configuration:** ```json "nonModpackFilesToDelete": { "/mods/lithium-fabric-0.15.1+mc1.21.1.jar": "6038cf136da413753345bf9d48e5798241439894", "/mods/": "97452cfadfde1f8f8c67838643019eabafa58fbb" }, ```

## What's Changed - **Added hash caching:** This should help reduce I/O and speed up update times on slower systems. - **Fixed issues:** Resolved netty buffer corruption and race conditions. - **Added HAProxy PROXY Protocol support.** - **New configuration options:** Implemented the `nonModpackFilesToDelete` server config option and the `allowRemoteNonModpackDeletions` client config option (opt-out). ### Configuration Details The `nonModpackFilesToDelete` feature allows you to delete specific files from the client that weren’t installed via AutoModpack before. If you simply want to remove a file from your modpack, there’s no change; just delete it from the server. This feature uses a map of two strings: the first is the relative file path, and the second is a SHA1 hash. To see these changes in action, you'll need to regenerate the modpack and restart the client. AutoModpack will check the specified path. If the path exists and the hash matches, it will delete the file. If the file doesn’t exist on the client, it will search through the parent directory for any files that match the hash. You can specify only the parent directory if you prefer, but it's best to use the most likely file path for optimal performance. Each file is evaluated only once and is treated as a deletion request; the client can disable it. All requests are timestamped, and the timestamps are saved after each evaluation to help reduce I/O. **Example configuration:** ```json "nonModpackFilesToDelete": { "/mods/lithium-fabric-0.15.1+mc1.21.1.jar": "6038cf136da413753345bf9d48e5798241439894", "/mods/": "97452cfadfde1f8f8c67838643019eabafa58fbb" }, ```

## What's Changed - **Added hash caching:** This should help reduce I/O and speed up update times on slower systems. - **Fixed issues:** Resolved netty buffer corruption and race conditions. - **Added HAProxy PROXY Protocol support.** - **New configuration options:** Implemented the `nonModpackFilesToDelete` server config option and the `allowRemoteNonModpackDeletions` client config option (opt-out). ### Configuration Details The `nonModpackFilesToDelete` feature allows you to delete specific files from the client that weren’t installed via AutoModpack before. If you simply want to remove a file from your modpack, there’s no change; just delete it from the server. This feature uses a map of two strings: the first is the relative file path, and the second is a SHA1 hash. To see these changes in action, you'll need to regenerate the modpack and restart the client. AutoModpack will check the specified path. If the path exists and the hash matches, it will delete the file. If the file doesn’t exist on the client, it will search through the parent directory for any files that match the hash. You can specify only the parent directory if you prefer, but it's best to use the most likely file path for optimal performance. Each file is evaluated only once and is treated as a deletion request; the client can disable it. All requests are timestamped, and the timestamps are saved after each evaluation to help reduce I/O. **Example configuration:** ```json "nonModpackFilesToDelete": { "/mods/lithium-fabric-0.15.1+mc1.21.1.jar": "6038cf136da413753345bf9d48e5798241439894", "/mods/": "97452cfadfde1f8f8c67838643019eabafa58fbb" }, ```

## What's Changed - **Added hash caching:** This should help reduce I/O and speed up update times on slower systems. - **Fixed issues:** Resolved netty buffer corruption and race conditions. - **Added HAProxy PROXY Protocol support.** - **New configuration options:** Implemented the `nonModpackFilesToDelete` server config option and the `allowRemoteNonModpackDeletions` client config option (opt-out). ### Configuration Details The `nonModpackFilesToDelete` feature allows you to delete specific files from the client that weren’t installed via AutoModpack before. If you simply want to remove a file from your modpack, there’s no change; just delete it from the server. This feature uses a map of two strings: the first is the relative file path, and the second is a SHA1 hash. To see these changes in action, you'll need to regenerate the modpack and restart the client. AutoModpack will check the specified path. If the path exists and the hash matches, it will delete the file. If the file doesn’t exist on the client, it will search through the parent directory for any files that match the hash. You can specify only the parent directory if you prefer, but it's best to use the most likely file path for optimal performance. Each file is evaluated only once and is treated as a deletion request; the client can disable it. All requests are timestamped, and the timestamps are saved after each evaluation to help reduce I/O. **Example configuration:** ```json "nonModpackFilesToDelete": { "/mods/lithium-fabric-0.15.1+mc1.21.1.jar": "6038cf136da413753345bf9d48e5798241439894", "/mods/": "97452cfadfde1f8f8c67838643019eabafa58fbb" }, ```

## What's Changed - **Added hash caching:** This should help reduce I/O and speed up update times on slower systems. - **Fixed issues:** Resolved netty buffer corruption and race conditions. - **Added HAProxy PROXY Protocol support.** - **New configuration options:** Implemented the `nonModpackFilesToDelete` server config option and the `allowRemoteNonModpackDeletions` client config option (opt-out). ### Configuration Details The `nonModpackFilesToDelete` feature allows you to delete specific files from the client that weren’t installed via AutoModpack before. If you simply want to remove a file from your modpack, there’s no change; just delete it from the server. This feature uses a map of two strings: the first is the relative file path, and the second is a SHA1 hash. To see these changes in action, you'll need to regenerate the modpack and restart the client. AutoModpack will check the specified path. If the path exists and the hash matches, it will delete the file. If the file doesn’t exist on the client, it will search through the parent directory for any files that match the hash. You can specify only the parent directory if you prefer, but it's best to use the most likely file path for optimal performance. Each file is evaluated only once and is treated as a deletion request; the client can disable it. All requests are timestamped, and the timestamps are saved after each evaluation to help reduce I/O. **Example configuration:** ```json "nonModpackFilesToDelete": { "/mods/lithium-fabric-0.15.1+mc1.21.1.jar": "6038cf136da413753345bf9d48e5798241439894", "/mods/": "97452cfadfde1f8f8c67838643019eabafa58fbb" }, ```

## What's Changed - **Added hash caching:** This should help reduce I/O and speed up update times on slower systems. - **Fixed issues:** Resolved netty buffer corruption and race conditions. - **Added HAProxy PROXY Protocol support.** - **New configuration options:** Implemented the `nonModpackFilesToDelete` server config option and the `allowRemoteNonModpackDeletions` client config option (opt-out). ### Configuration Details The `nonModpackFilesToDelete` feature allows you to delete specific files from the client that weren’t installed via AutoModpack before. If you simply want to remove a file from your modpack, there’s no change; just delete it from the server. This feature uses a map of two strings: the first is the relative file path, and the second is a SHA1 hash. To see these changes in action, you'll need to regenerate the modpack and restart the client. AutoModpack will check the specified path. If the path exists and the hash matches, it will delete the file. If the file doesn’t exist on the client, it will search through the parent directory for any files that match the hash. You can specify only the parent directory if you prefer, but it's best to use the most likely file path for optimal performance. Each file is evaluated only once and is treated as a deletion request; the client can disable it. All requests are timestamped, and the timestamps are saved after each evaluation to help reduce I/O. **Example configuration:** ```json "nonModpackFilesToDelete": { "/mods/lithium-fabric-0.15.1+mc1.21.1.jar": "6038cf136da413753345bf9d48e5798241439894", "/mods/": "97452cfadfde1f8f8c67838643019eabafa58fbb" }, ```

## What's Changed - **Added hash caching:** This should help reduce I/O and speed up update times on slower systems. - **Fixed issues:** Resolved netty buffer corruption and race conditions. - **Added HAProxy PROXY Protocol support.** - **New configuration options:** Implemented the `nonModpackFilesToDelete` server config option and the `allowRemoteNonModpackDeletions` client config option (opt-out). ### Configuration Details The `nonModpackFilesToDelete` feature allows you to delete specific files from the client that weren’t installed via AutoModpack before. If you simply want to remove a file from your modpack, there’s no change; just delete it from the server. This feature uses a map of two strings: the first is the relative file path, and the second is a SHA1 hash. To see these changes in action, you'll need to regenerate the modpack and restart the client. AutoModpack will check the specified path. If the path exists and the hash matches, it will delete the file. If the file doesn’t exist on the client, it will search through the parent directory for any files that match the hash. You can specify only the parent directory if you prefer, but it's best to use the most likely file path for optimal performance. Each file is evaluated only once and is treated as a deletion request; the client can disable it. All requests are timestamped, and the timestamps are saved after each evaluation to help reduce I/O. **Example configuration:** ```json "nonModpackFilesToDelete": { "/mods/lithium-fabric-0.15.1+mc1.21.1.jar": "6038cf136da413753345bf9d48e5798241439894", "/mods/": "97452cfadfde1f8f8c67838643019eabafa58fbb" }, ```

## What's Changed - **Added hash caching:** This should help reduce I/O and speed up update times on slower systems. - **Fixed issues:** Resolved netty buffer corruption and race conditions. - **Added HAProxy PROXY Protocol support.** - **New configuration options:** Implemented the `nonModpackFilesToDelete` server config option and the `allowRemoteNonModpackDeletions` client config option (opt-out). ### Configuration Details The `nonModpackFilesToDelete` feature allows you to delete specific files from the client that weren’t installed via AutoModpack before. If you simply want to remove a file from your modpack, there’s no change; just delete it from the server. This feature uses a map of two strings: the first is the relative file path, and the second is a SHA1 hash. To see these changes in action, you'll need to regenerate the modpack and restart the client. AutoModpack will check the specified path. If the path exists and the hash matches, it will delete the file. If the file doesn’t exist on the client, it will search through the parent directory for any files that match the hash. You can specify only the parent directory if you prefer, but it's best to use the most likely file path for optimal performance. Each file is evaluated only once and is treated as a deletion request; the client can disable it. All requests are timestamped, and the timestamps are saved after each evaluation to help reduce I/O. **Example configuration:** ```json "nonModpackFilesToDelete": { "/mods/lithium-fabric-0.15.1+mc1.21.1.jar": "6038cf136da413753345bf9d48e5798241439894", "/mods/": "97452cfadfde1f8f8c67838643019eabafa58fbb" }, ```

## What's Changed - **Added hash caching:** This should help reduce I/O and speed up update times on slower systems. - **Fixed issues:** Resolved netty buffer corruption and race conditions. - **Added HAProxy PROXY Protocol support.** - **New configuration options:** Implemented the `nonModpackFilesToDelete` server config option and the `allowRemoteNonModpackDeletions` client config option (opt-out). ### Configuration Details The `nonModpackFilesToDelete` feature allows you to delete specific files from the client that weren’t installed via AutoModpack before. If you simply want to remove a file from your modpack, there’s no change; just delete it from the server. This feature uses a map of two strings: the first is the relative file path, and the second is a SHA1 hash. To see these changes in action, you'll need to regenerate the modpack and restart the client. AutoModpack will check the specified path. If the path exists and the hash matches, it will delete the file. If the file doesn’t exist on the client, it will search through the parent directory for any files that match the hash. You can specify only the parent directory if you prefer, but it's best to use the most likely file path for optimal performance. Each file is evaluated only once and is treated as a deletion request; the client can disable it. All requests are timestamped, and the timestamps are saved after each evaluation to help reduce I/O. **Example configuration:** ```json "nonModpackFilesToDelete": { "/mods/lithium-fabric-0.15.1+mc1.21.1.jar": "6038cf136da413753345bf9d48e5798241439894", "/mods/": "97452cfadfde1f8f8c67838643019eabafa58fbb" }, ```

## What's Changed - **Added hash caching:** This should help reduce I/O and speed up update times on slower systems. - **Fixed issues:** Resolved netty buffer corruption and race conditions. - **Added HAProxy PROXY Protocol support.** - **New configuration options:** Implemented the `nonModpackFilesToDelete` server config option and the `allowRemoteNonModpackDeletions` client config option (opt-out). ### Configuration Details The `nonModpackFilesToDelete` feature allows you to delete specific files from the client that weren’t installed via AutoModpack before. If you simply want to remove a file from your modpack, there’s no change; just delete it from the server. This feature uses a map of two strings: the first is the relative file path, and the second is a SHA1 hash. To see these changes in action, you'll need to regenerate the modpack and restart the client. AutoModpack will check the specified path. If the path exists and the hash matches, it will delete the file. If the file doesn’t exist on the client, it will search through the parent directory for any files that match the hash. You can specify only the parent directory if you prefer, but it's best to use the most likely file path for optimal performance. Each file is evaluated only once and is treated as a deletion request; the client can disable it. All requests are timestamped, and the timestamps are saved after each evaluation to help reduce I/O. **Example configuration:** ```json "nonModpackFilesToDelete": { "/mods/lithium-fabric-0.15.1+mc1.21.1.jar": "6038cf136da413753345bf9d48e5798241439894", "/mods/": "97452cfadfde1f8f8c67838643019eabafa58fbb" }, ```

## What's Changed - **Added hash caching:** This should help reduce I/O and speed up update times on slower systems. - **Fixed issues:** Resolved netty buffer corruption and race conditions. - **Added HAProxy PROXY Protocol support.** - **New configuration options:** Implemented the `nonModpackFilesToDelete` server config option and the `allowRemoteNonModpackDeletions` client config option (opt-out). ### Configuration Details The `nonModpackFilesToDelete` feature allows you to delete specific files from the client that weren’t installed via AutoModpack before. If you simply want to remove a file from your modpack, there’s no change; just delete it from the server. This feature uses a map of two strings: the first is the relative file path, and the second is a SHA1 hash. To see these changes in action, you'll need to regenerate the modpack and restart the client. AutoModpack will check the specified path. If the path exists and the hash matches, it will delete the file. If the file doesn’t exist on the client, it will search through the parent directory for any files that match the hash. You can specify only the parent directory if you prefer, but it's best to use the most likely file path for optimal performance. Each file is evaluated only once and is treated as a deletion request; the client can disable it. All requests are timestamped, and the timestamps are saved after each evaluation to help reduce I/O. **Example configuration:** ```json "nonModpackFilesToDelete": { "/mods/lithium-fabric-0.15.1+mc1.21.1.jar": "6038cf136da413753345bf9d48e5798241439894", "/mods/": "97452cfadfde1f8f8c67838643019eabafa58fbb" }, ```

## What's Changed - **Added hash caching:** This should help reduce I/O and speed up update times on slower systems. - **Fixed issues:** Resolved netty buffer corruption and race conditions. - **Added HAProxy PROXY Protocol support.** - **New configuration options:** Implemented the `nonModpackFilesToDelete` server config option and the `allowRemoteNonModpackDeletions` client config option (opt-out). ### Configuration Details The `nonModpackFilesToDelete` feature allows you to delete specific files from the client that weren’t installed via AutoModpack before. If you simply want to remove a file from your modpack, there’s no change; just delete it from the server. This feature uses a map of two strings: the first is the relative file path, and the second is a SHA1 hash. To see these changes in action, you'll need to regenerate the modpack and restart the client. AutoModpack will check the specified path. If the path exists and the hash matches, it will delete the file. If the file doesn’t exist on the client, it will search through the parent directory for any files that match the hash. You can specify only the parent directory if you prefer, but it's best to use the most likely file path for optimal performance. Each file is evaluated only once and is treated as a deletion request; the client can disable it. All requests are timestamped, and the timestamps are saved after each evaluation to help reduce I/O. **Example configuration:** ```json "nonModpackFilesToDelete": { "/mods/lithium-fabric-0.15.1+mc1.21.1.jar": "6038cf136da413753345bf9d48e5798241439894", "/mods/": "97452cfadfde1f8f8c67838643019eabafa58fbb" }, ```

## What's Changed - **Added hash caching:** This should help reduce I/O and speed up update times on slower systems. - **Fixed issues:** Resolved netty buffer corruption and race conditions. - **Added HAProxy PROXY Protocol support.** - **New configuration options:** Implemented the `nonModpackFilesToDelete` server config option and the `allowRemoteNonModpackDeletions` client config option (opt-out). ### Configuration Details The `nonModpackFilesToDelete` feature allows you to delete specific files from the client that weren’t installed via AutoModpack before. If you simply want to remove a file from your modpack, there’s no change; just delete it from the server. This feature uses a map of two strings: the first is the relative file path, and the second is a SHA1 hash. To see these changes in action, you'll need to regenerate the modpack and restart the client. AutoModpack will check the specified path. If the path exists and the hash matches, it will delete the file. If the file doesn’t exist on the client, it will search through the parent directory for any files that match the hash. You can specify only the parent directory if you prefer, but it's best to use the most likely file path for optimal performance. Each file is evaluated only once and is treated as a deletion request; the client can disable it. All requests are timestamped, and the timestamps are saved after each evaluation to help reduce I/O. **Example configuration:** ```json "nonModpackFilesToDelete": { "/mods/lithium-fabric-0.15.1+mc1.21.1.jar": "6038cf136da413753345bf9d48e5798241439894", "/mods/": "97452cfadfde1f8f8c67838643019eabafa58fbb" }, ```

## What's Changed - **Added hash caching:** This should help reduce I/O and speed up update times on slower systems. - **Fixed issues:** Resolved netty buffer corruption and race conditions. - **Added HAProxy PROXY Protocol support.** - **New configuration options:** Implemented the `nonModpackFilesToDelete` server config option and the `allowRemoteNonModpackDeletions` client config option (opt-out). ### Configuration Details The `nonModpackFilesToDelete` feature allows you to delete specific files from the client that weren’t installed via AutoModpack before. If you simply want to remove a file from your modpack, there’s no change; just delete it from the server. This feature uses a map of two strings: the first is the relative file path, and the second is a SHA1 hash. To see these changes in action, you'll need to regenerate the modpack and restart the client. AutoModpack will check the specified path. If the path exists and the hash matches, it will delete the file. If the file doesn’t exist on the client, it will search through the parent directory for any files that match the hash. You can specify only the parent directory if you prefer, but it's best to use the most likely file path for optimal performance. Each file is evaluated only once and is treated as a deletion request; the client can disable it. All requests are timestamped, and the timestamps are saved after each evaluation to help reduce I/O. **Example configuration:** ```json "nonModpackFilesToDelete": { "/mods/lithium-fabric-0.15.1+mc1.21.1.jar": "6038cf136da413753345bf9d48e5798241439894", "/mods/": "97452cfadfde1f8f8c67838643019eabafa58fbb" }, ```

## What's Changed - **Added hash caching:** This should help reduce I/O and speed up update times on slower systems. - **Fixed issues:** Resolved netty buffer corruption and race conditions. - **Added HAProxy PROXY Protocol support.** - **New configuration options:** Implemented the `nonModpackFilesToDelete` server config option and the `allowRemoteNonModpackDeletions` client config option (opt-out). ### Configuration Details The `nonModpackFilesToDelete` feature allows you to delete specific files from the client that weren’t installed via AutoModpack before. If you simply want to remove a file from your modpack, there’s no change; just delete it from the server. This feature uses a map of two strings: the first is the relative file path, and the second is a SHA1 hash. To see these changes in action, you'll need to regenerate the modpack and restart the client. AutoModpack will check the specified path. If the path exists and the hash matches, it will delete the file. If the file doesn’t exist on the client, it will search through the parent directory for any files that match the hash. You can specify only the parent directory if you prefer, but it's best to use the most likely file path for optimal performance. Each file is evaluated only once and is treated as a deletion request; the client can disable it. All requests are timestamped, and the timestamps are saved after each evaluation to help reduce I/O. **Example configuration:** ```json "nonModpackFilesToDelete": { "/mods/lithium-fabric-0.15.1+mc1.21.1.jar": "6038cf136da413753345bf9d48e5798241439894", "/mods/": "97452cfadfde1f8f8c67838643019eabafa58fbb" }, ```

## What's Changed - **Added hash caching:** This should help reduce I/O and speed up update times on slower systems. - **Fixed issues:** Resolved netty buffer corruption and race conditions. - **Added HAProxy PROXY Protocol support.** - **New configuration options:** Implemented the `nonModpackFilesToDelete` server config option and the `allowRemoteNonModpackDeletions` client config option (opt-out). ### Configuration Details The `nonModpackFilesToDelete` feature allows you to delete specific files from the client that weren’t installed via AutoModpack before. If you simply want to remove a file from your modpack, there’s no change; just delete it from the server. This feature uses a map of two strings: the first is the relative file path, and the second is a SHA1 hash. To see these changes in action, you'll need to regenerate the modpack and restart the client. AutoModpack will check the specified path. If the path exists and the hash matches, it will delete the file. If the file doesn’t exist on the client, it will search through the parent directory for any files that match the hash. You can specify only the parent directory if you prefer, but it's best to use the most likely file path for optimal performance. Each file is evaluated only once and is treated as a deletion request; the client can disable it. All requests are timestamped, and the timestamps are saved after each evaluation to help reduce I/O. **Example configuration:** ```json "nonModpackFilesToDelete": { "/mods/lithium-fabric-0.15.1+mc1.21.1.jar": "6038cf136da413753345bf9d48e5798241439894", "/mods/": "97452cfadfde1f8f8c67838643019eabafa58fbb" }, ```

## What's Changed - **Added hash caching:** This should help reduce I/O and speed up update times on slower systems. - **Fixed issues:** Resolved netty buffer corruption and race conditions. - **Added HAProxy PROXY Protocol support.** - **New configuration options:** Implemented the `nonModpackFilesToDelete` server config option and the `allowRemoteNonModpackDeletions` client config option (opt-out). ### Configuration Details The `nonModpackFilesToDelete` feature allows you to delete specific files from the client that weren’t installed via AutoModpack before. If you simply want to remove a file from your modpack, there’s no change; just delete it from the server. This feature uses a map of two strings: the first is the relative file path, and the second is a SHA1 hash. To see these changes in action, you'll need to regenerate the modpack and restart the client. AutoModpack will check the specified path. If the path exists and the hash matches, it will delete the file. If the file doesn’t exist on the client, it will search through the parent directory for any files that match the hash. You can specify only the parent directory if you prefer, but it's best to use the most likely file path for optimal performance. Each file is evaluated only once and is treated as a deletion request; the client can disable it. All requests are timestamped, and the timestamps are saved after each evaluation to help reduce I/O. **Example configuration:** ```json "nonModpackFilesToDelete": { "/mods/lithium-fabric-0.15.1+mc1.21.1.jar": "6038cf136da413753345bf9d48e5798241439894", "/mods/": "97452cfadfde1f8f8c67838643019eabafa58fbb" }, ```

## What's Changed - **Added hash caching:** This should help reduce I/O and speed up update times on slower systems. - **Fixed issues:** Resolved netty buffer corruption and race conditions. - **Added HAProxy PROXY Protocol support.** - **New configuration options:** Implemented the `nonModpackFilesToDelete` server config option and the `allowRemoteNonModpackDeletions` client config option (opt-out). ### Configuration Details The `nonModpackFilesToDelete` feature allows you to delete specific files from the client that weren’t installed via AutoModpack before. If you simply want to remove a file from your modpack, there’s no change; just delete it from the server. This feature uses a map of two strings: the first is the relative file path, and the second is a SHA1 hash. To see these changes in action, you'll need to regenerate the modpack and restart the client. AutoModpack will check the specified path. If the path exists and the hash matches, it will delete the file. If the file doesn’t exist on the client, it will search through the parent directory for any files that match the hash. You can specify only the parent directory if you prefer, but it's best to use the most likely file path for optimal performance. Each file is evaluated only once and is treated as a deletion request; the client can disable it. All requests are timestamped, and the timestamps are saved after each evaluation to help reduce I/O. **Example configuration:** ```json "nonModpackFilesToDelete": { "/mods/lithium-fabric-0.15.1+mc1.21.1.jar": "6038cf136da413753345bf9d48e5798241439894", "/mods/": "97452cfadfde1f8f8c67838643019eabafa58fbb" }, ```

## What's Changed - Added support for Minecraft 1.21.11. - Improved self-updater robustness and added `syncAutoModpackVersion` config option to allow opting out of forced server version synchronization. - Added `requireMagicPackets` configuration option. - Implemented more complete [glob pattern](https://en.wikipedia.org/wiki/Glob_(programming)#Syntax) support, replacing the limited `!`, `*`, and `**` wildcards. - Implemented TLS session resumption. - Significantly optimized code performance, particularly on Unix platforms. - Reduced mod JAR size from ~25MB to ~15MB. - Fixed startup crashes caused by special characters (e.g., `!`) in the Minecraft directory path. - Fixed memory leaks. - Removed Herobrine. - Removed duplicate AutoModpack entry from the ModMenu. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.1...v4.0.2

## What's Changed - Added support for Minecraft 1.21.11. - Improved self-updater robustness and added `syncAutoModpackVersion` config option to allow opting out of forced server version synchronization. - Added `requireMagicPackets` configuration option. - Implemented more complete [glob pattern](https://en.wikipedia.org/wiki/Glob_(programming)#Syntax) support, replacing the limited `!`, `*`, and `**` wildcards. - Implemented TLS session resumption. - Significantly optimized code performance, particularly on Unix platforms. - Reduced mod JAR size from ~25MB to ~15MB. - Fixed startup crashes caused by special characters (e.g., `!`) in the Minecraft directory path. - Fixed memory leaks. - Removed Herobrine. - Removed duplicate AutoModpack entry from the ModMenu. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.1...v4.0.2

## What's Changed - Added support for Minecraft 1.21.11. - Improved self-updater robustness and added `syncAutoModpackVersion` config option to allow opting out of forced server version synchronization. - Added `requireMagicPackets` configuration option. - Implemented more complete [glob pattern](https://en.wikipedia.org/wiki/Glob_(programming)#Syntax) support, replacing the limited `!`, `*`, and `**` wildcards. - Implemented TLS session resumption. - Significantly optimized code performance, particularly on Unix platforms. - Reduced mod JAR size from ~25MB to ~15MB. - Fixed startup crashes caused by special characters (e.g., `!`) in the Minecraft directory path. - Fixed memory leaks. - Removed Herobrine. - Removed duplicate AutoModpack entry from the ModMenu. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.1...v4.0.2

## What's Changed - Added support for Minecraft 1.21.11. - Improved self-updater robustness and added `syncAutoModpackVersion` config option to allow opting out of forced server version synchronization. - Added `requireMagicPackets` configuration option. - Implemented more complete [glob pattern](https://en.wikipedia.org/wiki/Glob_(programming)#Syntax) support, replacing the limited `!`, `*`, and `**` wildcards. - Implemented TLS session resumption. - Significantly optimized code performance, particularly on Unix platforms. - Reduced mod JAR size from ~25MB to ~15MB. - Fixed startup crashes caused by special characters (e.g., `!`) in the Minecraft directory path. - Fixed memory leaks. - Removed Herobrine. - Removed duplicate AutoModpack entry from the ModMenu. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.1...v4.0.2

## What's Changed - Added support for Minecraft 1.21.11. - Improved self-updater robustness and added `syncAutoModpackVersion` config option to allow opting out of forced server version synchronization. - Added `requireMagicPackets` configuration option. - Implemented more complete [glob pattern](https://en.wikipedia.org/wiki/Glob_(programming)#Syntax) support, replacing the limited `!`, `*`, and `**` wildcards. - Implemented TLS session resumption. - Significantly optimized code performance, particularly on Unix platforms. - Reduced mod JAR size from ~25MB to ~15MB. - Fixed startup crashes caused by special characters (e.g., `!`) in the Minecraft directory path. - Fixed memory leaks. - Removed Herobrine. - Removed duplicate AutoModpack entry from the ModMenu. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.1...v4.0.2

## What's Changed - Added support for Minecraft 1.21.11. - Improved self-updater robustness and added `syncAutoModpackVersion` config option to allow opting out of forced server version synchronization. - Added `requireMagicPackets` configuration option. - Implemented more complete [glob pattern](https://en.wikipedia.org/wiki/Glob_(programming)#Syntax) support, replacing the limited `!`, `*`, and `**` wildcards. - Implemented TLS session resumption. - Significantly optimized code performance, particularly on Unix platforms. - Reduced mod JAR size from ~25MB to ~15MB. - Fixed startup crashes caused by special characters (e.g., `!`) in the Minecraft directory path. - Fixed memory leaks. - Removed Herobrine. - Removed duplicate AutoModpack entry from the ModMenu. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.1...v4.0.2

## What's Changed - Added support for Minecraft 1.21.11. - Improved self-updater robustness and added `syncAutoModpackVersion` config option to allow opting out of forced server version synchronization. - Added `requireMagicPackets` configuration option. - Implemented more complete [glob pattern](https://en.wikipedia.org/wiki/Glob_(programming)#Syntax) support, replacing the limited `!`, `*`, and `**` wildcards. - Implemented TLS session resumption. - Significantly optimized code performance, particularly on Unix platforms. - Reduced mod JAR size from ~25MB to ~15MB. - Fixed startup crashes caused by special characters (e.g., `!`) in the Minecraft directory path. - Fixed memory leaks. - Removed Herobrine. - Removed duplicate AutoModpack entry from the ModMenu. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.1...v4.0.2

## What's Changed - Added support for Minecraft 1.21.11. - Improved self-updater robustness and added `syncAutoModpackVersion` config option to allow opting out of forced server version synchronization. - Added `requireMagicPackets` configuration option. - Implemented more complete [glob pattern](https://en.wikipedia.org/wiki/Glob_(programming)#Syntax) support, replacing the limited `!`, `*`, and `**` wildcards. - Implemented TLS session resumption. - Significantly optimized code performance, particularly on Unix platforms. - Reduced mod JAR size from ~25MB to ~15MB. - Fixed startup crashes caused by special characters (e.g., `!`) in the Minecraft directory path. - Fixed memory leaks. - Removed Herobrine. - Removed duplicate AutoModpack entry from the ModMenu. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.1...v4.0.2

## What's Changed - Added support for Minecraft 1.21.11. - Improved self-updater robustness and added `syncAutoModpackVersion` config option to allow opting out of forced server version synchronization. - Added `requireMagicPackets` configuration option. - Implemented more complete [glob pattern](https://en.wikipedia.org/wiki/Glob_(programming)#Syntax) support, replacing the limited `!`, `*`, and `**` wildcards. - Implemented TLS session resumption. - Significantly optimized code performance, particularly on Unix platforms. - Reduced mod JAR size from ~25MB to ~15MB. - Fixed startup crashes caused by special characters (e.g., `!`) in the Minecraft directory path. - Fixed memory leaks. - Removed Herobrine. - Removed duplicate AutoModpack entry from the ModMenu. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.1...v4.0.2

## What's Changed - Added support for Minecraft 1.21.11. - Improved self-updater robustness and added `syncAutoModpackVersion` config option to allow opting out of forced server version synchronization. - Added `requireMagicPackets` configuration option. - Implemented more complete [glob pattern](https://en.wikipedia.org/wiki/Glob_(programming)#Syntax) support, replacing the limited `!`, `*`, and `**` wildcards. - Implemented TLS session resumption. - Significantly optimized code performance, particularly on Unix platforms. - Reduced mod JAR size from ~25MB to ~15MB. - Fixed startup crashes caused by special characters (e.g., `!`) in the Minecraft directory path. - Fixed memory leaks. - Removed Herobrine. - Removed duplicate AutoModpack entry from the ModMenu. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.1...v4.0.2

## What's Changed - Added support for Minecraft 1.21.11. - Improved self-updater robustness and added `syncAutoModpackVersion` config option to allow opting out of forced server version synchronization. - Added `requireMagicPackets` configuration option. - Implemented more complete [glob pattern](https://en.wikipedia.org/wiki/Glob_(programming)#Syntax) support, replacing the limited `!`, `*`, and `**` wildcards. - Implemented TLS session resumption. - Significantly optimized code performance, particularly on Unix platforms. - Reduced mod JAR size from ~25MB to ~15MB. - Fixed startup crashes caused by special characters (e.g., `!`) in the Minecraft directory path. - Fixed memory leaks. - Removed Herobrine. - Removed duplicate AutoModpack entry from the ModMenu. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.1...v4.0.2

## What's Changed - Added support for Minecraft 1.21.11. - Improved self-updater robustness and added `syncAutoModpackVersion` config option to allow opting out of forced server version synchronization. - Added `requireMagicPackets` configuration option. - Implemented more complete [glob pattern](https://en.wikipedia.org/wiki/Glob_(programming)#Syntax) support, replacing the limited `!`, `*`, and `**` wildcards. - Implemented TLS session resumption. - Significantly optimized code performance, particularly on Unix platforms. - Reduced mod JAR size from ~25MB to ~15MB. - Fixed startup crashes caused by special characters (e.g., `!`) in the Minecraft directory path. - Fixed memory leaks. - Removed Herobrine. - Removed duplicate AutoModpack entry from the ModMenu. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.1...v4.0.2

## What's Changed - Added support for Minecraft 1.21.11. - Improved self-updater robustness and added `syncAutoModpackVersion` config option to allow opting out of forced server version synchronization. - Added `requireMagicPackets` configuration option. - Implemented more complete [glob pattern](https://en.wikipedia.org/wiki/Glob_(programming)#Syntax) support, replacing the limited `!`, `*`, and `**` wildcards. - Implemented TLS session resumption. - Significantly optimized code performance, particularly on Unix platforms. - Reduced mod JAR size from ~25MB to ~15MB. - Fixed startup crashes caused by special characters (e.g., `!`) in the Minecraft directory path. - Fixed memory leaks. - Removed Herobrine. - Removed duplicate AutoModpack entry from the ModMenu. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.1...v4.0.2

## What's Changed - Added support for Minecraft 1.21.11. - Improved self-updater robustness and added `syncAutoModpackVersion` config option to allow opting out of forced server version synchronization. - Added `requireMagicPackets` configuration option. - Implemented more complete [glob pattern](https://en.wikipedia.org/wiki/Glob_(programming)#Syntax) support, replacing the limited `!`, `*`, and `**` wildcards. - Implemented TLS session resumption. - Significantly optimized code performance, particularly on Unix platforms. - Reduced mod JAR size from ~25MB to ~15MB. - Fixed startup crashes caused by special characters (e.g., `!`) in the Minecraft directory path. - Fixed memory leaks. - Removed Herobrine. - Removed duplicate AutoModpack entry from the ModMenu. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.1...v4.0.2

## What's Changed - Added support for Minecraft 1.21.11. - Improved self-updater robustness and added `syncAutoModpackVersion` config option to allow opting out of forced server version synchronization. - Added `requireMagicPackets` configuration option. - Implemented more complete [glob pattern](https://en.wikipedia.org/wiki/Glob_(programming)#Syntax) support, replacing the limited `!`, `*`, and `**` wildcards. - Implemented TLS session resumption. - Significantly optimized code performance, particularly on Unix platforms. - Reduced mod JAR size from ~25MB to ~15MB. - Fixed startup crashes caused by special characters (e.g., `!`) in the Minecraft directory path. - Fixed memory leaks. - Removed Herobrine. - Removed duplicate AutoModpack entry from the ModMenu. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.1...v4.0.2

## What's Changed - Added support for Minecraft 1.21.11. - Improved self-updater robustness and added `syncAutoModpackVersion` config option to allow opting out of forced server version synchronization. - Added `requireMagicPackets` configuration option. - Implemented more complete [glob pattern](https://en.wikipedia.org/wiki/Glob_(programming)#Syntax) support, replacing the limited `!`, `*`, and `**` wildcards. - Implemented TLS session resumption. - Significantly optimized code performance, particularly on Unix platforms. - Reduced mod JAR size from ~25MB to ~15MB. - Fixed startup crashes caused by special characters (e.g., `!`) in the Minecraft directory path. - Fixed memory leaks. - Removed Herobrine. - Removed duplicate AutoModpack entry from the ModMenu. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.1...v4.0.2

## What's Changed - Added support for Minecraft 1.21.11. - Improved self-updater robustness and added `syncAutoModpackVersion` config option to allow opting out of forced server version synchronization. - Added `requireMagicPackets` configuration option. - Implemented more complete [glob pattern](https://en.wikipedia.org/wiki/Glob_(programming)#Syntax) support, replacing the limited `!`, `*`, and `**` wildcards. - Implemented TLS session resumption. - Significantly optimized code performance, particularly on Unix platforms. - Reduced mod JAR size from ~25MB to ~15MB. - Fixed startup crashes caused by special characters (e.g., `!`) in the Minecraft directory path. - Fixed memory leaks. - Removed Herobrine. - Removed duplicate AutoModpack entry from the ModMenu. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.1...v4.0.2

## What's Changed - Added support for Minecraft 1.21.11. - Improved self-updater robustness and added `syncAutoModpackVersion` config option to allow opting out of forced server version synchronization. - Added `requireMagicPackets` configuration option. - Implemented more complete [glob pattern](https://en.wikipedia.org/wiki/Glob_(programming)#Syntax) support, replacing the limited `!`, `*`, and `**` wildcards. - Implemented TLS session resumption. - Significantly optimized code performance, particularly on Unix platforms. - Reduced mod JAR size from ~25MB to ~15MB. - Fixed startup crashes caused by special characters (e.g., `!`) in the Minecraft directory path. - Fixed memory leaks. - Removed Herobrine. - Removed duplicate AutoModpack entry from the ModMenu. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.1...v4.0.2

## What's Changed - Added support for Minecraft 1.21.11. - Improved self-updater robustness and added `syncAutoModpackVersion` config option to allow opting out of forced server version synchronization. - Added `requireMagicPackets` configuration option. - Implemented more complete [glob pattern](https://en.wikipedia.org/wiki/Glob_(programming)#Syntax) support, replacing the limited `!`, `*`, and `**` wildcards. - Implemented TLS session resumption. - Significantly optimized code performance, particularly on Unix platforms. - Reduced mod JAR size from ~25MB to ~15MB. - Fixed startup crashes caused by special characters (e.g., `!`) in the Minecraft directory path. - Fixed memory leaks. - Removed Herobrine. - Removed duplicate AutoModpack entry from the ModMenu. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.1...v4.0.2

## What's Changed - Added support for Minecraft 1.21.11. - Improved self-updater robustness and added `syncAutoModpackVersion` config option to allow opting out of forced server version synchronization. - Added `requireMagicPackets` configuration option. - Implemented more complete [glob pattern](https://en.wikipedia.org/wiki/Glob_(programming)#Syntax) support, replacing the limited `!`, `*`, and `**` wildcards. - Implemented TLS session resumption. - Significantly optimized code performance, particularly on Unix platforms. - Reduced mod JAR size from ~25MB to ~15MB. - Fixed startup crashes caused by special characters (e.g., `!`) in the Minecraft directory path. - Fixed memory leaks. - Removed Herobrine. - Removed duplicate AutoModpack entry from the ModMenu. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.1...v4.0.2

## What's Changed - Added support for Minecraft 1.21.11. - Improved self-updater robustness and added `syncAutoModpackVersion` config option to allow opting out of forced server version synchronization. - Added `requireMagicPackets` configuration option. - Implemented more complete [glob pattern](https://en.wikipedia.org/wiki/Glob_(programming)#Syntax) support, replacing the limited `!`, `*`, and `**` wildcards. - Implemented TLS session resumption. - Significantly optimized code performance, particularly on Unix platforms. - Reduced mod JAR size from ~25MB to ~15MB. - Fixed startup crashes caused by special characters (e.g., `!`) in the Minecraft directory path. - Fixed memory leaks. - Removed Herobrine. - Removed duplicate AutoModpack entry from the ModMenu. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.1...v4.0.2

## What's Changed - Added support for Minecraft 1.21.11. - Improved self-updater robustness and added `syncAutoModpackVersion` config option to allow opting out of forced server version synchronization. - Added `requireMagicPackets` configuration option. - Implemented more complete [glob pattern](https://en.wikipedia.org/wiki/Glob_(programming)#Syntax) support, replacing the limited `!`, `*`, and `**` wildcards. - Implemented TLS session resumption. - Significantly optimized code performance, particularly on Unix platforms. - Reduced mod JAR size from ~25MB to ~15MB. - Fixed startup crashes caused by special characters (e.g., `!`) in the Minecraft directory path. - Fixed memory leaks. - Removed Herobrine. - Removed duplicate AutoModpack entry from the ModMenu. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.1...v4.0.2

## What's Changed - Added support for Minecraft 1.21.11. - Improved self-updater robustness and added `syncAutoModpackVersion` config option to allow opting out of forced server version synchronization. - Added `requireMagicPackets` configuration option. - Implemented more complete [glob pattern](https://en.wikipedia.org/wiki/Glob_(programming)#Syntax) support, replacing the limited `!`, `*`, and `**` wildcards. - Implemented TLS session resumption. - Significantly optimized code performance, particularly on Unix platforms. - Reduced mod JAR size from ~25MB to ~15MB. - Fixed startup crashes caused by special characters (e.g., `!`) in the Minecraft directory path. - Fixed memory leaks. - Removed Herobrine. - Removed duplicate AutoModpack entry from the ModMenu. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.1...v4.0.2

## What's Changed - Added support for Minecraft 1.21.11. - Improved self-updater robustness and added `syncAutoModpackVersion` config option to allow opting out of forced server version synchronization. - Added `requireMagicPackets` configuration option. - Implemented more complete [glob pattern](https://en.wikipedia.org/wiki/Glob_(programming)#Syntax) support, replacing the limited `!`, `*`, and `**` wildcards. - Implemented TLS session resumption. - Significantly optimized code performance, particularly on Unix platforms. - Reduced mod JAR size from ~25MB to ~15MB. - Fixed startup crashes caused by special characters (e.g., `!`) in the Minecraft directory path. - Fixed memory leaks. - Removed Herobrine. - Removed duplicate AutoModpack entry from the ModMenu. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.1...v4.0.2

## What's Changed - Added support for Minecraft 1.21.11. - Improved self-updater robustness and added `syncAutoModpackVersion` config option to allow opting out of forced server version synchronization. - Added `requireMagicPackets` configuration option. - Implemented more complete [glob pattern](https://en.wikipedia.org/wiki/Glob_(programming)#Syntax) support, replacing the limited `!`, `*`, and `**` wildcards. - Implemented TLS session resumption. - Significantly optimized code performance, particularly on Unix platforms. - Reduced mod JAR size from ~25MB to ~15MB. - Fixed startup crashes caused by special characters (e.g., `!`) in the Minecraft directory path. - Fixed memory leaks. - Removed Herobrine. - Removed duplicate AutoModpack entry from the ModMenu. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.1...v4.0.2

## What's Changed - Added support for Minecraft 1.21.11. - Improved self-updater robustness and added `syncAutoModpackVersion` config option to allow opting out of forced server version synchronization. - Added `requireMagicPackets` configuration option. - Implemented more complete [glob pattern](https://en.wikipedia.org/wiki/Glob_(programming)#Syntax) support, replacing the limited `!`, `*`, and `**` wildcards. - Implemented TLS session resumption. - Significantly optimized code performance, particularly on Unix platforms. - Reduced mod JAR size from ~25MB to ~15MB. - Fixed startup crashes caused by special characters (e.g., `!`) in the Minecraft directory path. - Fixed memory leaks. - Removed Herobrine. - Removed duplicate AutoModpack entry from the ModMenu. **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.1...v4.0.2

## What's Changed - **Fixed**: Displaying version as 1.0.0 (#442) - **Fixed**: Resource loading error in logs on 1.21.10 version (#443) - **Fixed**: Neoforge 1.21.8 incorrectly using 1.21.10 loader classes - **Improved**: Server-side detection of Zstd capabilities **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.0...v4.0.1

## What's Changed - **Fixed**: Displaying version as 1.0.0 (#442) - **Fixed**: Resource loading error in logs on 1.21.10 version (#443) - **Fixed**: Neoforge 1.21.8 incorrectly using 1.21.10 loader classes - **Improved**: Server-side detection of Zstd capabilities **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.0...v4.0.1

## What's Changed - **Fixed**: Displaying version as 1.0.0 (#442) - **Fixed**: Resource loading error in logs on 1.21.10 version (#443) - **Fixed**: Neoforge 1.21.8 incorrectly using 1.21.10 loader classes - **Improved**: Server-side detection of Zstd capabilities **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.0...v4.0.1

## What's Changed - **Fixed**: Displaying version as 1.0.0 (#442) - **Fixed**: Resource loading error in logs on 1.21.10 version (#443) - **Fixed**: Neoforge 1.21.8 incorrectly using 1.21.10 loader classes - **Improved**: Server-side detection of Zstd capabilities **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.0...v4.0.1

## What's Changed - **Fixed**: Displaying version as 1.0.0 (#442) - **Fixed**: Resource loading error in logs on 1.21.10 version (#443) - **Fixed**: Neoforge 1.21.8 incorrectly using 1.21.10 loader classes - **Improved**: Server-side detection of Zstd capabilities **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.0...v4.0.1

## What's Changed - **Fixed**: Displaying version as 1.0.0 (#442) - **Fixed**: Resource loading error in logs on 1.21.10 version (#443) - **Fixed**: Neoforge 1.21.8 incorrectly using 1.21.10 loader classes - **Improved**: Server-side detection of Zstd capabilities **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.0...v4.0.1

## What's Changed - **Fixed**: Displaying version as 1.0.0 (#442) - **Fixed**: Resource loading error in logs on 1.21.10 version (#443) - **Fixed**: Neoforge 1.21.8 incorrectly using 1.21.10 loader classes - **Improved**: Server-side detection of Zstd capabilities **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.0...v4.0.1

## What's Changed - **Fixed**: Displaying version as 1.0.0 (#442) - **Fixed**: Resource loading error in logs on 1.21.10 version (#443) - **Fixed**: Neoforge 1.21.8 incorrectly using 1.21.10 loader classes - **Improved**: Server-side detection of Zstd capabilities **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.0...v4.0.1

## What's Changed - **Fixed**: Displaying version as 1.0.0 (#442) - **Fixed**: Resource loading error in logs on 1.21.10 version (#443) - **Fixed**: Neoforge 1.21.8 incorrectly using 1.21.10 loader classes - **Improved**: Server-side detection of Zstd capabilities **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.0...v4.0.1

## What's Changed - **Fixed**: Displaying version as 1.0.0 (#442) - **Fixed**: Resource loading error in logs on 1.21.10 version (#443) - **Fixed**: Neoforge 1.21.8 incorrectly using 1.21.10 loader classes - **Improved**: Server-side detection of Zstd capabilities **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.0...v4.0.1

## What's Changed - **Fixed**: Displaying version as 1.0.0 (#442) - **Fixed**: Resource loading error in logs on 1.21.10 version (#443) - **Fixed**: Neoforge 1.21.8 incorrectly using 1.21.10 loader classes - **Improved**: Server-side detection of Zstd capabilities **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.0...v4.0.1

## What's Changed - **Fixed**: Displaying version as 1.0.0 (#442) - **Fixed**: Resource loading error in logs on 1.21.10 version (#443) - **Fixed**: Neoforge 1.21.8 incorrectly using 1.21.10 loader classes - **Improved**: Server-side detection of Zstd capabilities **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.0...v4.0.1

## What's Changed - **Fixed**: Displaying version as 1.0.0 (#442) - **Fixed**: Resource loading error in logs on 1.21.10 version (#443) - **Fixed**: Neoforge 1.21.8 incorrectly using 1.21.10 loader classes - **Improved**: Server-side detection of Zstd capabilities **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.0...v4.0.1

## What's Changed - **Fixed**: Displaying version as 1.0.0 (#442) - **Fixed**: Resource loading error in logs on 1.21.10 version (#443) - **Fixed**: Neoforge 1.21.8 incorrectly using 1.21.10 loader classes - **Improved**: Server-side detection of Zstd capabilities **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.0...v4.0.1

## What's Changed - **Fixed**: Displaying version as 1.0.0 (#442) - **Fixed**: Resource loading error in logs on 1.21.10 version (#443) - **Fixed**: Neoforge 1.21.8 incorrectly using 1.21.10 loader classes - **Improved**: Server-side detection of Zstd capabilities **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.0...v4.0.1

## What's Changed - **Fixed**: Displaying version as 1.0.0 (#442) - **Fixed**: Resource loading error in logs on 1.21.10 version (#443) - **Fixed**: Neoforge 1.21.8 incorrectly using 1.21.10 loader classes - **Improved**: Server-side detection of Zstd capabilities **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.0...v4.0.1

## What's Changed - **Fixed**: Displaying version as 1.0.0 (#442) - **Fixed**: Resource loading error in logs on 1.21.10 version (#443) - **Fixed**: Neoforge 1.21.8 incorrectly using 1.21.10 loader classes - **Improved**: Server-side detection of Zstd capabilities **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.0...v4.0.1

## What's Changed - **Fixed**: Displaying version as 1.0.0 (#442) - **Fixed**: Resource loading error in logs on 1.21.10 version (#443) - **Fixed**: Neoforge 1.21.8 incorrectly using 1.21.10 loader classes - **Improved**: Server-side detection of Zstd capabilities **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.0...v4.0.1

## What's Changed - **Fixed**: Displaying version as 1.0.0 (#442) - **Fixed**: Resource loading error in logs on 1.21.10 version (#443) - **Fixed**: Neoforge 1.21.8 incorrectly using 1.21.10 loader classes - **Improved**: Server-side detection of Zstd capabilities **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.0...v4.0.1

## What's Changed - **Fixed**: Displaying version as 1.0.0 (#442) - **Fixed**: Resource loading error in logs on 1.21.10 version (#443) - **Fixed**: Neoforge 1.21.8 incorrectly using 1.21.10 loader classes - **Improved**: Server-side detection of Zstd capabilities **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.0...v4.0.1

## What's Changed - **Fixed**: Displaying version as 1.0.0 (#442) - **Fixed**: Resource loading error in logs on 1.21.10 version (#443) - **Fixed**: Neoforge 1.21.8 incorrectly using 1.21.10 loader classes - **Improved**: Server-side detection of Zstd capabilities **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.0...v4.0.1

## What's Changed - **Fixed**: Displaying version as 1.0.0 (#442) - **Fixed**: Resource loading error in logs on 1.21.10 version (#443) - **Fixed**: Neoforge 1.21.8 incorrectly using 1.21.10 loader classes - **Improved**: Server-side detection of Zstd capabilities **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.0...v4.0.1

## What's Changed - **Fixed**: Displaying version as 1.0.0 (#442) - **Fixed**: Resource loading error in logs on 1.21.10 version (#443) - **Fixed**: Neoforge 1.21.8 incorrectly using 1.21.10 loader classes - **Improved**: Server-side detection of Zstd capabilities **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.0...v4.0.1

## What's Changed - **Fixed**: Displaying version as 1.0.0 (#442) - **Fixed**: Resource loading error in logs on 1.21.10 version (#443) - **Fixed**: Neoforge 1.21.8 incorrectly using 1.21.10 loader classes - **Improved**: Server-side detection of Zstd capabilities **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.0...v4.0.1

## Finally stable v4 A lot has changed since 3.5.2 (after 551 commits)... That was released so long ago that i don't believe anyone is still using that ancient version, if you do, now its the time to update. ### Changes since beta44 - Dropped 1.21.9 in favor of 1.21.10 same with 1.21.6 -> 1.21.8 - Changed download progress bar texture for minecraft green bossbar - Properly catches Throwable object instead of Exception for loading zstd, finally fixing Android launchers - Removed ability to remotely downgrade to any of 4.0.0 betas **v4.0.0-beta44...v4.0.0 Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta44...v4.0.0 **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v3.5.2...v4.0.0

## Finally stable v4 A lot has changed since 3.5.2 (after 551 commits)... That was released so long ago that i don't believe anyone is still using that ancient version, if you do, now its the time to update. ### Changes since beta44 - Dropped 1.21.9 in favor of 1.21.10 same with 1.21.6 -> 1.21.8 - Changed download progress bar texture for minecraft green bossbar - Properly catches Throwable object instead of Exception for loading zstd, finally fixing Android launchers - Removed ability to remotely downgrade to any of 4.0.0 betas **v4.0.0-beta44...v4.0.0 Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta44...v4.0.0 **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v3.5.2...v4.0.0

## Finally stable v4 A lot has changed since 3.5.2 (after 551 commits)... That was released so long ago that i don't believe anyone is still using that ancient version, if you do, now its the time to update. ### Changes since beta44 - Dropped 1.21.9 in favor of 1.21.10 same with 1.21.6 -> 1.21.8 - Changed download progress bar texture for minecraft green bossbar - Properly catches Throwable object instead of Exception for loading zstd, finally fixing Android launchers - Removed ability to remotely downgrade to any of 4.0.0 betas **v4.0.0-beta44...v4.0.0 Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta44...v4.0.0 **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v3.5.2...v4.0.0

## Finally stable v4 A lot has changed since 3.5.2 (after 551 commits)... That was released so long ago that i don't believe anyone is still using that ancient version, if you do, now its the time to update. ### Changes since beta44 - Dropped 1.21.9 in favor of 1.21.10 same with 1.21.6 -> 1.21.8 - Changed download progress bar texture for minecraft green bossbar - Properly catches Throwable object instead of Exception for loading zstd, finally fixing Android launchers - Removed ability to remotely downgrade to any of 4.0.0 betas **v4.0.0-beta44...v4.0.0 Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta44...v4.0.0 **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v3.5.2...v4.0.0

## Finally stable v4 A lot has changed since 3.5.2 (after 551 commits)... That was released so long ago that i don't believe anyone is still using that ancient version, if you do, now its the time to update. ### Changes since beta44 - Dropped 1.21.9 in favor of 1.21.10 same with 1.21.6 -> 1.21.8 - Changed download progress bar texture for minecraft green bossbar - Properly catches Throwable object instead of Exception for loading zstd, finally fixing Android launchers - Removed ability to remotely downgrade to any of 4.0.0 betas **v4.0.0-beta44...v4.0.0 Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta44...v4.0.0 **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v3.5.2...v4.0.0

## Finally stable v4 A lot has changed since 3.5.2 (after 551 commits)... That was released so long ago that i don't believe anyone is still using that ancient version, if you do, now its the time to update. ### Changes since beta44 - Dropped 1.21.9 in favor of 1.21.10 same with 1.21.6 -> 1.21.8 - Changed download progress bar texture for minecraft green bossbar - Properly catches Throwable object instead of Exception for loading zstd, finally fixing Android launchers - Removed ability to remotely downgrade to any of 4.0.0 betas **v4.0.0-beta44...v4.0.0 Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta44...v4.0.0 **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v3.5.2...v4.0.0

## Finally stable v4 A lot has changed since 3.5.2 (after 551 commits)... That was released so long ago that i don't believe anyone is still using that ancient version, if you do, now its the time to update. ### Changes since beta44 - Dropped 1.21.9 in favor of 1.21.10 same with 1.21.6 -> 1.21.8 - Changed download progress bar texture for minecraft green bossbar - Properly catches Throwable object instead of Exception for loading zstd, finally fixing Android launchers - Removed ability to remotely downgrade to any of 4.0.0 betas **v4.0.0-beta44...v4.0.0 Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta44...v4.0.0 **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v3.5.2...v4.0.0

## Finally stable v4 A lot has changed since 3.5.2 (after 551 commits)... That was released so long ago that i don't believe anyone is still using that ancient version, if you do, now its the time to update. ### Changes since beta44 - Dropped 1.21.9 in favor of 1.21.10 same with 1.21.6 -> 1.21.8 - Changed download progress bar texture for minecraft green bossbar - Properly catches Throwable object instead of Exception for loading zstd, finally fixing Android launchers - Removed ability to remotely downgrade to any of 4.0.0 betas **v4.0.0-beta44...v4.0.0 Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta44...v4.0.0 **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v3.5.2...v4.0.0

## Finally stable v4 A lot has changed since 3.5.2 (after 551 commits)... That was released so long ago that i don't believe anyone is still using that ancient version, if you do, now its the time to update. ### Changes since beta44 - Dropped 1.21.9 in favor of 1.21.10 same with 1.21.6 -> 1.21.8 - Changed download progress bar texture for minecraft green bossbar - Properly catches Throwable object instead of Exception for loading zstd, finally fixing Android launchers - Removed ability to remotely downgrade to any of 4.0.0 betas **v4.0.0-beta44...v4.0.0 Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta44...v4.0.0 **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v3.5.2...v4.0.0

## Finally stable v4 A lot has changed since 3.5.2 (after 551 commits)... That was released so long ago that i don't believe anyone is still using that ancient version, if you do, now its the time to update. ### Changes since beta44 - Dropped 1.21.9 in favor of 1.21.10 same with 1.21.6 -> 1.21.8 - Changed download progress bar texture for minecraft green bossbar - Properly catches Throwable object instead of Exception for loading zstd, finally fixing Android launchers - Removed ability to remotely downgrade to any of 4.0.0 betas **v4.0.0-beta44...v4.0.0 Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta44...v4.0.0 **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v3.5.2...v4.0.0

## Finally stable v4 A lot has changed since 3.5.2 (after 551 commits)... That was released so long ago that i don't believe anyone is still using that ancient version, if you do, now its the time to update. ### Changes since beta44 - Dropped 1.21.9 in favor of 1.21.10 same with 1.21.6 -> 1.21.8 - Changed download progress bar texture for minecraft green bossbar - Properly catches Throwable object instead of Exception for loading zstd, finally fixing Android launchers - Removed ability to remotely downgrade to any of 4.0.0 betas **v4.0.0-beta44...v4.0.0 Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta44...v4.0.0 **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v3.5.2...v4.0.0

## Finally stable v4 A lot has changed since 3.5.2 (after 551 commits)... That was released so long ago that i don't believe anyone is still using that ancient version, if you do, now its the time to update. ### Changes since beta44 - Dropped 1.21.9 in favor of 1.21.10 same with 1.21.6 -> 1.21.8 - Changed download progress bar texture for minecraft green bossbar - Properly catches Throwable object instead of Exception for loading zstd, finally fixing Android launchers - Removed ability to remotely downgrade to any of 4.0.0 betas **v4.0.0-beta44...v4.0.0 Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta44...v4.0.0 **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v3.5.2...v4.0.0

## Finally stable v4 A lot has changed since 3.5.2 (after 551 commits)... That was released so long ago that i don't believe anyone is still using that ancient version, if you do, now its the time to update. ### Changes since beta44 - Dropped 1.21.9 in favor of 1.21.10 same with 1.21.6 -> 1.21.8 - Changed download progress bar texture for minecraft green bossbar - Properly catches Throwable object instead of Exception for loading zstd, finally fixing Android launchers - Removed ability to remotely downgrade to any of 4.0.0 betas **v4.0.0-beta44...v4.0.0 Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta44...v4.0.0 **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v3.5.2...v4.0.0

## Finally stable v4 A lot has changed since 3.5.2 (after 551 commits)... That was released so long ago that i don't believe anyone is still using that ancient version, if you do, now its the time to update. ### Changes since beta44 - Dropped 1.21.9 in favor of 1.21.10 same with 1.21.6 -> 1.21.8 - Changed download progress bar texture for minecraft green bossbar - Properly catches Throwable object instead of Exception for loading zstd, finally fixing Android launchers - Removed ability to remotely downgrade to any of 4.0.0 betas **v4.0.0-beta44...v4.0.0 Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta44...v4.0.0 **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v3.5.2...v4.0.0

## Finally stable v4 A lot has changed since 3.5.2 (after 551 commits)... That was released so long ago that i don't believe anyone is still using that ancient version, if you do, now its the time to update. ### Changes since beta44 - Dropped 1.21.9 in favor of 1.21.10 same with 1.21.6 -> 1.21.8 - Changed download progress bar texture for minecraft green bossbar - Properly catches Throwable object instead of Exception for loading zstd, finally fixing Android launchers - Removed ability to remotely downgrade to any of 4.0.0 betas **v4.0.0-beta44...v4.0.0 Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta44...v4.0.0 **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v3.5.2...v4.0.0

## Finally stable v4 A lot has changed since 3.5.2 (after 551 commits)... That was released so long ago that i don't believe anyone is still using that ancient version, if you do, now its the time to update. ### Changes since beta44 - Dropped 1.21.9 in favor of 1.21.10 same with 1.21.6 -> 1.21.8 - Changed download progress bar texture for minecraft green bossbar - Properly catches Throwable object instead of Exception for loading zstd, finally fixing Android launchers - Removed ability to remotely downgrade to any of 4.0.0 betas **v4.0.0-beta44...v4.0.0 Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta44...v4.0.0 **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v3.5.2...v4.0.0

## Finally stable v4 A lot has changed since 3.5.2 (after 551 commits)... That was released so long ago that i don't believe anyone is still using that ancient version, if you do, now its the time to update. ### Changes since beta44 - Dropped 1.21.9 in favor of 1.21.10 same with 1.21.6 -> 1.21.8 - Changed download progress bar texture for minecraft green bossbar - Properly catches Throwable object instead of Exception for loading zstd, finally fixing Android launchers - Removed ability to remotely downgrade to any of 4.0.0 betas **v4.0.0-beta44...v4.0.0 Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta44...v4.0.0 **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v3.5.2...v4.0.0

## Finally stable v4 A lot has changed since 3.5.2 (after 551 commits)... That was released so long ago that i don't believe anyone is still using that ancient version, if you do, now its the time to update. ### Changes since beta44 - Dropped 1.21.9 in favor of 1.21.10 same with 1.21.6 -> 1.21.8 - Changed download progress bar texture for minecraft green bossbar - Properly catches Throwable object instead of Exception for loading zstd, finally fixing Android launchers - Removed ability to remotely downgrade to any of 4.0.0 betas **v4.0.0-beta44...v4.0.0 Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta44...v4.0.0 **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v3.5.2...v4.0.0

## Finally stable v4 A lot has changed since 3.5.2 (after 551 commits)... That was released so long ago that i don't believe anyone is still using that ancient version, if you do, now its the time to update. ### Changes since beta44 - Dropped 1.21.9 in favor of 1.21.10 same with 1.21.6 -> 1.21.8 - Changed download progress bar texture for minecraft green bossbar - Properly catches Throwable object instead of Exception for loading zstd, finally fixing Android launchers - Removed ability to remotely downgrade to any of 4.0.0 betas **v4.0.0-beta44...v4.0.0 Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta44...v4.0.0 **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v3.5.2...v4.0.0

## Finally stable v4 A lot has changed since 3.5.2 (after 551 commits)... That was released so long ago that i don't believe anyone is still using that ancient version, if you do, now its the time to update. ### Changes since beta44 - Dropped 1.21.9 in favor of 1.21.10 same with 1.21.6 -> 1.21.8 - Changed download progress bar texture for minecraft green bossbar - Properly catches Throwable object instead of Exception for loading zstd, finally fixing Android launchers - Removed ability to remotely downgrade to any of 4.0.0 betas **v4.0.0-beta44...v4.0.0 Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta44...v4.0.0 **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v3.5.2...v4.0.0

## Finally stable v4 A lot has changed since 3.5.2 (after 551 commits)... That was released so long ago that i don't believe anyone is still using that ancient version, if you do, now its the time to update. ### Changes since beta44 - Dropped 1.21.9 in favor of 1.21.10 same with 1.21.6 -> 1.21.8 - Changed download progress bar texture for minecraft green bossbar - Properly catches Throwable object instead of Exception for loading zstd, finally fixing Android launchers - Removed ability to remotely downgrade to any of 4.0.0 betas **v4.0.0-beta44...v4.0.0 Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta44...v4.0.0 **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v3.5.2...v4.0.0

## Finally stable v4 A lot has changed since 3.5.2 (after 551 commits)... That was released so long ago that i don't believe anyone is still using that ancient version, if you do, now its the time to update. ### Changes since beta44 - Dropped 1.21.9 in favor of 1.21.10 same with 1.21.6 -> 1.21.8 - Changed download progress bar texture for minecraft green bossbar - Properly catches Throwable object instead of Exception for loading zstd, finally fixing Android launchers - Removed ability to remotely downgrade to any of 4.0.0 betas **v4.0.0-beta44...v4.0.0 Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta44...v4.0.0 **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v3.5.2...v4.0.0

## Finally stable v4 A lot has changed since 3.5.2 (after 551 commits)... That was released so long ago that i don't believe anyone is still using that ancient version, if you do, now its the time to update. ### Changes since beta44 - Dropped 1.21.9 in favor of 1.21.10 same with 1.21.6 -> 1.21.8 - Changed download progress bar texture for minecraft green bossbar - Properly catches Throwable object instead of Exception for loading zstd, finally fixing Android launchers - Removed ability to remotely downgrade to any of 4.0.0 betas **v4.0.0-beta44...v4.0.0 Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta44...v4.0.0 **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v3.5.2...v4.0.0

## Finally stable v4 A lot has changed since 3.5.2 (after 551 commits)... That was released so long ago that i don't believe anyone is still using that ancient version, if you do, now its the time to update. ### Changes since beta44 - Dropped 1.21.9 in favor of 1.21.10 same with 1.21.6 -> 1.21.8 - Changed download progress bar texture for minecraft green bossbar - Properly catches Throwable object instead of Exception for loading zstd, finally fixing Android launchers - Removed ability to remotely downgrade to any of 4.0.0 betas **v4.0.0-beta44...v4.0.0 Changelog**: https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta44...v4.0.0 **Full Changelog**: https://github.com/Skidamek/AutoModpack/compare/v3.5.2...v4.0.0

## Hotfix - Fixed configuration incorrectly swapping all `!/` prefixed file paths to `/!/` **Full changelog:** https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta43...v4.0.0-beta44

## Hotfix - Fixed configuration incorrectly swapping all `!/` prefixed file paths to `/!/` **Full changelog:** https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta43...v4.0.0-beta44

## Hotfix - Fixed configuration incorrectly swapping all `!/` prefixed file paths to `/!/` **Full changelog:** https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta43...v4.0.0-beta44

## Hotfix - Fixed configuration incorrectly swapping all `!/` prefixed file paths to `/!/` **Full changelog:** https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta43...v4.0.0-beta44

## Hotfix - Fixed configuration incorrectly swapping all `!/` prefixed file paths to `/!/` **Full changelog:** https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta43...v4.0.0-beta44

## Hotfix - Fixed configuration incorrectly swapping all `!/` prefixed file paths to `/!/` **Full changelog:** https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta43...v4.0.0-beta44

## Hotfix - Fixed configuration incorrectly swapping all `!/` prefixed file paths to `/!/` **Full changelog:** https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta43...v4.0.0-beta44

## Hotfix - Fixed configuration incorrectly swapping all `!/` prefixed file paths to `/!/` **Full changelog:** https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta43...v4.0.0-beta44

## Hotfix - Fixed configuration incorrectly swapping all `!/` prefixed file paths to `/!/` **Full changelog:** https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta43...v4.0.0-beta44

## Hotfix - Fixed configuration incorrectly swapping all `!/` prefixed file paths to `/!/` **Full changelog:** https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta43...v4.0.0-beta44

## Hotfix - Fixed configuration incorrectly swapping all `!/` prefixed file paths to `/!/` **Full changelog:** https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta43...v4.0.0-beta44

## Hotfix - Fixed configuration incorrectly swapping all `!/` prefixed file paths to `/!/` **Full changelog:** https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta43...v4.0.0-beta44

## Hotfix - Fixed configuration incorrectly swapping all `!/` prefixed file paths to `/!/` **Full changelog:** https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta43...v4.0.0-beta44

## Hotfix - Fixed configuration incorrectly swapping all `!/` prefixed file paths to `/!/` **Full changelog:** https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta43...v4.0.0-beta44

## Hotfix - Fixed configuration incorrectly swapping all `!/` prefixed file paths to `/!/` **Full changelog:** https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta43...v4.0.0-beta44

## Hotfix - Fixed configuration incorrectly swapping all `!/` prefixed file paths to `/!/` **Full changelog:** https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta43...v4.0.0-beta44

## Hotfix - Fixed configuration incorrectly swapping all `!/` prefixed file paths to `/!/` **Full changelog:** https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta43...v4.0.0-beta44

## Hotfix - Fixed configuration incorrectly swapping all `!/` prefixed file paths to `/!/` **Full changelog:** https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta43...v4.0.0-beta44

## Hotfix - Fixed configuration incorrectly swapping all `!/` prefixed file paths to `/!/` **Full changelog:** https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta43...v4.0.0-beta44

## Hotfix - Fixed configuration incorrectly swapping all `!/` prefixed file paths to `/!/` **Full changelog:** https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta43...v4.0.0-beta44

## Hotfix - Fixed configuration incorrectly swapping all `!/` prefixed file paths to `/!/` **Full changelog:** https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta43...v4.0.0-beta44

## Hotfix - Fixed configuration incorrectly swapping all `!/` prefixed file paths to `/!/` **Full changelog:** https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta43...v4.0.0-beta44

## Hotfix - Fixed configuration incorrectly swapping all `!/` prefixed file paths to `/!/` **Full changelog:** https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta43...v4.0.0-beta44

## Hotfix - Fixed configuration incorrectly swapping all `!/` prefixed file paths to `/!/` **Full changelog:** https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta43...v4.0.0-beta44

## What's Changed - The certificate validation screen has been redesigned. It's now clearer and easier to skip - WildCards computation is much more efficient, cutting down I/O requests and speeding up modpack generation on large packs - Android compatibility: we now try to load zstd compression on all devices and fall back to gzip if that fails - Server config lists automatically remove the redundant `/automodpack/host-modpack/` prefix - Connection handshake updated to work with playit.gg Full changelog: https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta42...v4.0.0-beta43

## What's Changed - The certificate validation screen has been redesigned. It's now clearer and easier to skip - WildCards computation is much more efficient, cutting down I/O requests and speeding up modpack generation on large packs - Android compatibility: we now try to load zstd compression on all devices and fall back to gzip if that fails - Server config lists automatically remove the redundant `/automodpack/host-modpack/` prefix - Connection handshake updated to work with playit.gg Full changelog: https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta42...v4.0.0-beta43

## What's Changed - The certificate validation screen has been redesigned. It's now clearer and easier to skip - WildCards computation is much more efficient, cutting down I/O requests and speeding up modpack generation on large packs - Android compatibility: we now try to load zstd compression on all devices and fall back to gzip if that fails - Server config lists automatically remove the redundant `/automodpack/host-modpack/` prefix - Connection handshake updated to work with playit.gg Full changelog: https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta42...v4.0.0-beta43

## What's Changed - The certificate validation screen has been redesigned. It's now clearer and easier to skip - WildCards computation is much more efficient, cutting down I/O requests and speeding up modpack generation on large packs - Android compatibility: we now try to load zstd compression on all devices and fall back to gzip if that fails - Server config lists automatically remove the redundant `/automodpack/host-modpack/` prefix - Connection handshake updated to work with playit.gg Full changelog: https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta42...v4.0.0-beta43

## What's Changed - The certificate validation screen has been redesigned. It's now clearer and easier to skip - WildCards computation is much more efficient, cutting down I/O requests and speeding up modpack generation on large packs - Android compatibility: we now try to load zstd compression on all devices and fall back to gzip if that fails - Server config lists automatically remove the redundant `/automodpack/host-modpack/` prefix - Connection handshake updated to work with playit.gg Full changelog: https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta42...v4.0.0-beta43

## What's Changed - The certificate validation screen has been redesigned. It's now clearer and easier to skip - WildCards computation is much more efficient, cutting down I/O requests and speeding up modpack generation on large packs - Android compatibility: we now try to load zstd compression on all devices and fall back to gzip if that fails - Server config lists automatically remove the redundant `/automodpack/host-modpack/` prefix - Connection handshake updated to work with playit.gg Full changelog: https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta42...v4.0.0-beta43

## What's Changed - The certificate validation screen has been redesigned. It's now clearer and easier to skip - WildCards computation is much more efficient, cutting down I/O requests and speeding up modpack generation on large packs - Android compatibility: we now try to load zstd compression on all devices and fall back to gzip if that fails - Server config lists automatically remove the redundant `/automodpack/host-modpack/` prefix - Connection handshake updated to work with playit.gg Full changelog: https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta42...v4.0.0-beta43

## What's Changed - The certificate validation screen has been redesigned. It's now clearer and easier to skip - WildCards computation is much more efficient, cutting down I/O requests and speeding up modpack generation on large packs - Android compatibility: we now try to load zstd compression on all devices and fall back to gzip if that fails - Server config lists automatically remove the redundant `/automodpack/host-modpack/` prefix - Connection handshake updated to work with playit.gg Full changelog: https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta42...v4.0.0-beta43

## What's Changed - The certificate validation screen has been redesigned. It's now clearer and easier to skip - WildCards computation is much more efficient, cutting down I/O requests and speeding up modpack generation on large packs - Android compatibility: we now try to load zstd compression on all devices and fall back to gzip if that fails - Server config lists automatically remove the redundant `/automodpack/host-modpack/` prefix - Connection handshake updated to work with playit.gg Full changelog: https://github.com/Skidamek/AutoModpack/compare/v4.0.0-beta42...v4.0.0-beta43