AntiSkidAC Changelog

Client Integrity and Policy Management

New F8 integrity interface

• Added a new F8 AntiSkidAC interface for viewing client integrity and mod manifest information in-game.
• Added a terminal-style manifest browser showing detected mods, versions, source files, and shortened BLAKE3-256 hashes.
• Added controls for copying the full policy JSON, individual manifest entries, and full mod hashes directly to the clipboard.
• Added an in-game control for regenerating the client manifest export.
• Added administrator shortcuts for requesting pending hash updates and reloading the server policy.
• Multiplayer-only administrator controls are automatically disabled in singleplayer.
• Added clear status displays for server challenges, manifest generation, runtime integrity, and server policy state.
• Added a dedicated singleplayer state rather than displaying misleading multiplayer attestation warnings.
• The manifest list now automatically uses all available vertical space, allowing more entries to be displayed at once on larger windows and resolutions.
• Added responsive sizing so the interface makes better use of available screen space while remaining usable at smaller resolutions.

Client manifest export

• Added a deterministic client mod manifest export at:

  config/antiskidac/client-mod-hashes.txt

• The export uses the same Forge mod detection and BLAKE3-256 hashes used by AntiSkidAC's client attestation.

• Manifest exports can be regenerated directly from the new F8 interface.

• Exported information can be used when creating or reviewing an AntiSkidAC server policy.

Forge 1.7.10 coremod support

• Added proper integrity hashing for Forge 1.7.10 coremods whose normal Forge container reports minecraft.jar instead of the mod's actual source file.
• AntiSkidAC can now recover the physical JAR associated with standard IFMLLoadingPlugin coremods and hash it through the same BLAKE3-256 verification path as ordinary Forge mods.
• Added support for Forge's wrapped InjectedModContainer behavior so the underlying coremod container can be matched to its real loading-plugin JAR.
• Coremods such as CodeChickenCore and GTNHLib Core now resolve to their actual installed JARs instead of appearing as unverifiable minecraft.jar sources.
• Coremods use the normal approved-hash policy; there is no weaker version-only or non-JAR whitelist.
• Ambiguous or genuinely unresolvable coremod sources continue to fail closed rather than being trusted heuristically.
• Entries without a valid digest now display B3 unknown instead of an empty hash value.

Reviewed mod hash updates

• Added optional detection of hash changes for already-known mods.
• Detected hashes are treated only as review candidates and are never automatically trusted.
• AntiSkidAC tracks repeated observations of candidate hashes to make legitimate mod updates easier to identify.
• Conflicting observations are retained instead of silently replacing one another.
• Added administrator commands to list, approve, and reject pending hash updates.
• Invalid candidates are rejected before they can be approved.
• Approved hash changes are written safely before becoming part of the active server policy.
• Detection, conflicts, approvals, rejections, and persistence failures are logged for administrator review.

Live server policy management

• Added live reload support for:

  • Approved mod hashes
  • Required mods
  • Allowed platform versions
  • Blacklist rules

• Server policies can now be updated without restarting Minecraft.

• Connected clients can optionally be issued fresh integrity challenges after a policy change so they are checked against the new rules.

• Invalid or incomplete policy changes do not replace the currently working configuration.

Configuration cleanup

• Consolidated AntiSkidAC files under:

  config/antiskidac/

• This directory now contains the main configuration, mod hash policy, platform policy, required-mod policy, blacklist policy, and generated client manifest.

• Existing AntiSkidAC files from the previous locations are migrated automatically on startup when possible.

• Migration will not overwrite files already present in the new directory.

Singleplayer and LAN behavior

• The player hosting an integrated singleplayer/LAN server is no longer subjected to server modlist attestation against themselves.
• Local manifest generation, exports, and configured runtime-integrity functionality remain available.
• Other players joining through LAN are still treated as remote clients and go through AntiSkidAC's normal nonce-bound integrity verification.