Skip to content

Droid Mod Loader v0.7.0-beta: Reliable Foundation

Latest

Choose a tag to compare

@CyberShonk CyberShonk released this 30 Jun 02:12
· 22 commits to main since this release

Droid Mod Loader v0.7.0-beta

Summary

v0.7.0-beta is the Reliable Foundation release. It strengthens archive
handling, protects installed mods during replacement, adds interruption and
cancellation recovery, completes the direct-filesystem transition, and retains
the post-v0.6.0-beta architecture and plugin-order improvements.

Added

  • Tale of Two Wastelands profile support with the correct legacy
    timestamp-based plugin-order policy.
  • Content-signature detection for ZIP, 7Z, RAR4, and RAR5 archives.
  • Safe extraction limits for paths, duplicates, case collisions, entry counts,
    file sizes, total output, path length, and available storage.
  • Persistent replacement transactions with recovery after interruption.
  • Cooperative cancellation for archive copying, extraction, preparation, and
    installation.
  • Canonical release version metadata through version.properties.

Changed

  • DML now uses direct filesystem paths for Game Root, Data, Archive Library,
    archive imports, deployment, scanning, overwrite inspection, and legacy
    plugin timestamp ordering.
  • Archive type and Archive Library labels are based on file content rather than
    filename extensions.
  • New mod content is fully staged before it can replace an existing installed
    mod.
  • Archive import cancellation distinguishes between unregistered partial copies
    and archives already saved to the library.
  • Internal activity and engine responsibilities were split into focused
    workflows and services without intentionally changing established behavior.
  • The displayed app version now comes from the APK's build configuration.

Fixed

  • Failed or partial extraction can no longer be accepted as a successful mod
    installation.
  • Existing installed mods remain available when replacement preparation or
    promotion fails.
  • Interrupted replacement operations are recovered during startup and profile
    activation.
  • Cancellation removes partial copied or extracted output where possible.
  • RAR failures now distinguish unsupported RAR5, encrypted or
    password-protected archives, multipart archives, corruption, and general I/O
    failures more clearly.
  • Supported archives can be recognized when their filename extension is missing
    or incorrect.

Known Issues

  • RAR5 is recognized but cannot currently be installed.
  • Password-protected or encrypted archives and multipart RAR archives are not
    supported.
  • Some uncommon 7Z compression or encryption variants may remain unsupported.
  • Android does not allow DML to access another application's protected
    Android/data directory.
  • Game Root and Data folder validation still needs stronger game-specific
    guidance.
  • This is beta software. Back up important game folders before deployment.

Upgrade Notes

  • Install v0.7.0-beta over v0.6.0-beta. Do not uninstall first if you want
    to preserve app-managed profiles and state.
  • Grant all-files access when prompted on Android 11 or newer.
  • Upgrade validation confirmed retention of profiles, direct paths, archive
    history, installed mods, plugin state, and deployment state.
  • Legacy URI-only Game Root, Data, and Archive Library selections must be
    selected again as direct filesystem paths.

Validation

Completed for this release:

  • JVM unit tests and project validation script;
  • debug and release APK assembly;
  • version name v0.7.0-beta and version code 3 verification;
  • game-aware plugin-order tests;
  • focused archive probing, extraction-safety, replacement, recovery, and
    cancellation tests;
  • real ZIP, 7Z, RAR4, RAR5, encrypted, multipart, corrupt, renamed, and
    extensionless archive checks;
  • fresh install and in-place upgrade from the public v0.6.0-beta APK;
  • profile, path, archive-history, mod, plugin, and deployment-state retention;
  • large-import cancellation and cleanup;
  • interrupted replacement recovery after restart; and
  • safe-folder deployment and restart smoke checks.