CompatScope

What's new

This update focuses on making CompatScope's fixes, history, change tracking, and reports much more reliable and easier to understand.

Persistent Changes tracking

The Changes screen now keeps its state between world restarts and CompatScope updates.

Applied fixes no longer disappear from the list after leaving and re-entering a world, and updating CompatScope will not reset the saved baseline unless the actual scan coverage rules change.

CompatScope can now correctly distinguish between:

• real modpack changes;
• changes made by CompatScope itself;
• resources that only became visible because the scanner gained better coverage.

This prevents large groups of existing resources from suddenly appearing as false "Added" changes after an update.

Better support for modded data resources

Server data scanning has been expanded beyond the standard Minecraft resource folders.

CompatScope can now detect resources from custom mod-defined data roots, including content such as custom Origins data and other non-vanilla server data paths.

Generated fixes are also tracked as their own resource layer instead of being merged with an original provider simply because both resources contain identical data.

This makes provider selection and generated compatibility fixes much more accurate.

Improved Fix History

Fix History has been redesigned to be easier to read.

History entries now focus on useful information such as:

• what resource was affected;
• which provider was selected;
• when the action happened;
• whether the fix was applied, rolled back, staged, or superseded;
• whether the generated resource is still active.

Long internal IDs, hashes, and other implementation details are moved into technical sections instead of dominating the main view.

Better connection between History and Changes

Changes and Fix History now work together.

When a change was created by a CompatScope-generated fix, the interface can show the related history information and selected provider.

This makes it much easier to understand where a change came from and why it exists.

More accurate fix state

CompatScope now clearly separates three different concepts:

• Fix availability — what kind of fix is available before any choice is made;
• Resolved safety — whether the selected provider has been validated as safe;
• Lifecycle state — whether that fix is currently staged, applied, rolled back, or otherwise inactive.

For example, a finding can still have a base fix type of CONDITIONAL, while the selected and verified provider is shown as SAFE and the resulting fix is shown as APPLIED.

These states are no longer mixed together.

Fix state in reports

HTML and JSON reports now include persistent Fix State information.

Reports can show:

• the selected provider;
• the affected resource;
• resolved safety;
• current lifecycle state;
• whether the generated layer is active;
• whether the latest Scan confirmed the generated resource;
• whether the generated resource still matches the selected provider;
• whether the resource currently appears in Changes.

This makes reports much more useful when reviewing a pack after CompatScope has already applied fixes.

Clearer historical report data

Old staged or rolled-back history entries no longer appear as if they still own the current active change.

If a resource is currently changed by another active fix, historical entries now make that distinction clear instead of incorrectly showing the old entry as ADDED.

Safer baseline migration

CompatScope now keeps a separate compatibility version for Changes tracking.

Normal CompatScope updates, report changes, and diagnostic improvements no longer reset your Changes baseline.

A baseline is only rebuilt when the way CompatScope scans content actually changes.

When such a migration is required, existing CompatScope-generated fixes are preserved as real changes instead of being absorbed into the new baseline.

Improved generated-fix verification

Generated SAFE fixes now have stronger verification in reports.

CompatScope can confirm that:

• the generated resource is present in the latest Scan;
• the selected provider is still available;
• the generated resource still matches the selected provider by SHA-256.

This provides a clearer indication that an applied compatibility fix is still active and unchanged.

General UI and reporting improvements

Several smaller improvements were also made across the interface and reports:

• clearer wording in Changes;
• more useful source/provider information;
• better empty-state messages;
• improved History entry layout;
• easier-to-read timestamps;
• cleaner technical details;
• clearer distinction between active and historical fixes;
• improved HTML report navigation and Fix State presentation.

Schema Versions

Current release schemas:

• Report format: 54
• Diagnostic schema: diagnostics-54
• Analysis schema: analysis-68

Since the previous stable release, the schemas have been extended to support the new History, Changes, generated-fix, and report-state features.

The newer schemas add structured information for:

• persistent Fix History;
• resolved fix safety;
• applied/staged/rolled-back fix states;
• generated resource scan confirmation;
• selected provider information;
• generated resource SHA-256 verification;
• separation between the current target state and historical fix entries;
• improved Changes tracking;
• custom server-data resource coverage;
• more accurate generated resource/provider identity.

Notes

CompatScope may still mark a Scan as PARTIAL when configured scan limits are reached or when very large resources are skipped.

Runtime log analysis is also bounded to prevent excessive memory and processing usage on very large modpacks.

These limits are reported directly in the Scan and report metadata so you can see when coverage was incomplete.