Skip to content

Releases: Skidamek/AutoModpack

AutoModpack 4.0.5

19 Jan 11:37

Choose a tag to compare

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.
  • Enabled syncLoaderVersion by default on new instances.

Full Changelog: v4.0.4...v4.0.5

AutoModpack 4.0.4

17 Jan 11:57

Choose a tag to compare

Hot fix

  • Fix nonModpackFilesToDelete ignoring all files which have the same timestamp after first one is evaluated.

Full Changelog: v4.0.3...v4.0.4

AutoModpack 4.0.3

17 Jan 11:00

Choose a tag to compare

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"
},

AutoModpack 4.0.2

19 Dec 15:35

Choose a tag to compare

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 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: v4.0.1...v4.0.2

AutoModpack 4.0.1

15 Nov 13:47

Choose a tag to compare

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: v4.0.0...v4.0.1

AutoModpack 4.0.0

08 Nov 14:11

Choose a tag to compare

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: v4.0.0-beta44...v4.0.0
Full Changelog: v3.5.2...v4.0.0

AutoModpack 4.0.0-beta44

31 Oct 13:53

Choose a tag to compare

Hotfix

  • Fixed configuration incorrectly swapping all !/ prefixed file paths to /!/

Full changelog: v4.0.0-beta43...v4.0.0-beta44

AutoModpack 4.0.0-beta43

31 Oct 13:02

Choose a tag to compare

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: v4.0.0-beta42...v4.0.0-beta43

AutoModpack 4.0.0-beta42

19 Oct 09:35

Choose a tag to compare

What's Changed

  • Now for real, fixed connection issues (#430)
  • Optimized connection code
  • Added configuration packets to the protocol instead of bundling everything into handshake

Full Changelog: v4.0.0-beta41...v4.0.0-beta42

AutoModpack 4.0.0-beta41

15 Oct 16:57

Choose a tag to compare

What's Changed

  • Fixed incompatibility with latest Distant Horizons versions and Cesium mod (#384)
  • Fixed incompatibility with Android launchers like pojav and FCL (#379 )
  • Finally properly fixed the previous connection issue "lost connection: Server sent an invalid packet"

Full Changelog: v4.0.0-beta40...v4.0.0-beta41