CompatScope

Highlights

• Significantly improved runtime diagnostic accuracy.
• Reduced false-positive HIGH and MEDIUM priority findings.
• Improved root-cause and ownership attribution.
• Added more conservative handling of ambiguous compatibility conflicts.
• Improved recipe, advancement, loot, registry, shader, resource, Mixin and integration diagnostics.
• Added better aggregation and deduplication of repeated runtime events.
• Added structured operation types, subjects, impact scopes and affected targets to many previously generic warnings.
• Improved consistency between NeoForge and Fabric reports.
• Improved investigation grouping and report readability.
• Added broader diagnostic integrity validation.
• Fixed a CompatScope startup issue on NeoForge.

Runtime Diagnostics

Runtime analysis now recognizes and structures many additional situations, including:

• Recipe parsing and loading failures.
• Advancement loading failures.
• Loot table loading failures.
• Empty registry failures.
• Registry tag loading and validation problems.
• Shader program validation errors.
• Missing shader samplers and uniforms.
• Missing textures and model resources.
• Missing sound events.
• Invalid sprite animation frames.
• Invalid animation file names.
• Malformed language files.
• Texture mip-level reductions.
• Resource preload failures.
• Invalid resource-pack paths.
• Invalid recipe-book mappings.
• Missing integration keybindings.
• Skipped dynamic item model generation.
• Missing optional classes.
• Missing Mixin targets.
• Cancelled Mixins.
• Force-disabled Mixins.
• Mixin redirect conflicts.
• Mixin overwrite conflicts.
• Mixin reference-map warnings.
• Duplicate configuration registration.
• Automatically corrected configuration files.
• Invalid mod metadata.
• Legacy integration modes.
• Deprecated integration APIs.
• Remote update and metadata check failures.
• Optional integrations disabled because dependencies or classes are unavailable.
• Runtime compatibility workarounds.
• Explicit cross-mod compatibility warnings.
• Startup performance warnings.
• Deferred-task performance warnings.

Priority Calibration

Priority handling has been significantly refined.

• Intentional recipe overrides are no longer treated as false HIGH conflicts.
• Recipe viewer failures from JEI/EMI are separated from actual gameplay recipe-loading failures.
• Optional update-check network failures are treated as degraded optional functionality rather than gameplay failures.
• Missing texture priority is based on affected objects rather than model variant count.
• OS-specific compatibility gates remain informational.
• Feature-local failures no longer automatically become HIGH solely because the original log uses ERROR severity.
• Repeated cosmetic/resource warnings no longer escalate just because many variants produced the same message.
• Real recipe, loot, advancement, registry and data-loading failures remain high priority when appropriate.

Attribution Improvements

CompatScope now uses more conservative and evidence-based attribution.

• Added verified physical resource ownership.
• Added Java exception throw-site attribution.
• Added advancement source attribution.
• Added implementation-provider attribution.
• Added client asset ownership analysis.
• Improved logger display-name resolution.
• Improved resource and recipe source-container evidence.
• Reporter mods are no longer automatically treated as root causes.
• Referenced mods are separated from verified providers.
• Mixin conflicts no longer automatically blame a single participant.
• Unique namespace/resource ownership does not automatically imply root cause.
• Cross-namespace physical ownership is preserved when it can be verified.

A diagnostic can no longer remain marked as ATTRIBUTED unless its final actor set contains sufficient attribution evidence.

Supported evidence roles include cases such as:

• SOURCE_PROVIDER
• MIXIN_PROVIDER
• CODE_OWNER
• EXCEPTION_ORIGIN
• IMPLEMENTATION_PROVIDER

Mixin Analysis

Mixin diagnostics received major improvements.

• Added structured redirect-conflict detection.
• Added structured overwrite-conflict detection.
• Improved conservative attribution when two mods compete for the same target.
• Fixed malformed mod IDs extracted from Mixin log syntax.
• Added static-binding recovery semantics.
• Added missing-target semantics.
• Added force-disabled Mixin semantics.
• Added cancelled Mixin semantics.
• Added reference-map aggregation.
• Mixin providers are only considered root causes when sufficient evidence exists.

Resource Analysis

Resource diagnostics are now more precise.

• Shader problems are classified by shader semantics rather than words inside namespaces.
• Missing model textures are aggregated by base model.
• Texture variants no longer produce unnecessary duplicate diagnostics.
• Missing sounds use structured sound-event targets.
• Invalid animation file names are reported as resource issues.
• Malformed language files are correctly classified as language/resource problems.
• Texture mip-level reductions are reported as visual degradation.
• Invalid resource-pack paths receive dedicated diagnostics.
• Resource preload failures are grouped using meaningful owner/path context.
• Client assets can use verified physical source ownership.
• Sprite frame validation now has dedicated resource semantics.

Recipe and Data Analysis

• Normalized multiple recipe parsing message formats.
• Improved recipe failure aggregation.
• Added recipe source ownership.
• Added structured recipe subjects and recipe sets.
• Added recipe-book mapping validation.
• Improved distinction between gameplay recipe failures and recipe-viewer integration failures.
• Improved invalid recipe reference handling.
• Added advancement source attribution.
• Added advancement load summaries.
• Added structured advancement-set subjects.
• Added structured loot table subjects and targets.
• Improved registry and registry-tag diagnostics.
• Improved empty-registry loading semantics.

Remote Checks and Optional Integrations

Optional online functionality is now separated from core gameplay failures.

Recognized cases include:

• SSL handshake failures.
• Connection resets.
• DNS failures.
• Connection refused.
• Network unreachable.
• HTTP/socket timeouts.
• Expired remote metadata.
• Missing update indexes.
• Named optional metadata checks.
• Version checks.
• Update checks.
• Supporter/Patreon-style metadata checks.

Equivalent WARN and ERROR messages from the same remote check are now deduplicated into one diagnostic while preserving the strongest source severity.

Performance Diagnostics

Added structured runtime performance diagnostics for:

• Initial datapack loading time.
• Total game startup time.
• Time from startup to world loading.
• Deferred mod tasks.
• Rendering paths without optimized vertex writing.
• Server tick lag.

Performance warnings do not automatically assign blame to the mod or framework that logged them.

Aggregation and Deduplication

• Improved semantic grouping of repeated runtime events.
• Duplicate remote check errors and warnings are consolidated.
• Shader failures are grouped by provider/namespace while retaining individual shader targets.
• Missing model variants are aggregated to their base object.
• DataFixer notices are grouped into bounded sets.
• Recipe parsing failures are no longer split by irrelevant contextual mods.
• Similar runtime warnings now produce fewer duplicate investigations.
• Strongest source severity is preserved when equivalent events are merged.
• Recipe viewer failures are grouped separately from core recipe-loading failures.
• Resource preload failures are grouped more consistently.

Diagnostic Structure

Many previously generic runtime warnings now expose structured data such as:

• operationType
• subject
• impactScope
• affectedTargets
• occurrence count
• source severity
• outcome
• actor roles
• attribution status
• ownership evidence

Subjects are now available for more operations including:

• recipe loading
• loot table loading
• advancement loading
• shader validation
• registry tags
• resource preload
• remote checks
• datapack startup timing
• server tick lag
• configuration validation
• Mixin conflicts

Report Improvements

• Fixed investigation layout overflow.
• Improved wrapping of long IDs, file paths and action-plan entries.
• Improved investigation grouping.
• Improved action-plan evidence.
• Added more complete subjects and affected targets.
• Improved distinction between:
  • failures
  • degraded functionality
  • recovered conditions
  • informational observations
• Improved machine-readable diagnostic metadata.
• Improved cross-loader consistency.

CompatScope Reliability

Fixed a NeoForge startup issue where persisted Fix-state recovery attempted to access configuration values before the COMMON configuration had finished loading.

Fix-state recovery is now delayed until the configuration system is available.

This prevents the previous startup warning:

Cannot get config value before config is loaded

and avoids unnecessary CompatScope-generated stack traces during mod initialization.

Diagnostic Integrity

A broader audit was added for diagnostic consistency.

CompatScope now performs stronger checks for:

• Missing operation types.
• Missing subjects.
• Unknown impact scopes.
• Unsupported attribution states.
• Unsupported root-cause assignments.
• Invalid or nonexistent mod IDs.
• Category/operation mismatches.
• Duplicate diagnostics.
• Incorrect aggregation.
• Priority escalation caused only by occurrence count.
• Reporter/provider confusion.
• Inconsistent affected targets.
• Runtime exception-chain duplication.

Ambiguous INFO-only messages remain generic when the original log does not provide enough information to identify a reliable target or cause.

CompatScope will prefer an honest unknown result over inventing attribution.

Current Report Schema

• Report format: 52
• Diagnostic schema: diagnostics-43
• Analysis schema: analysis-54

This update focuses on making CompatScope reports more accurate, structured and actionable while reducing false positives and avoiding unsupported root-cause assumptions.