AutoModpack

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:

"nonModpackFilesToDelete": {
  "/mods/lithium-fabric-0.15.1+mc1.21.1.jar": "6038cf136da413753345bf9d48e5798241439894",
  "/mods/": "97452cfadfde1f8f8c67838643019eabafa58fbb"
},