[freezy]

Plugin-owned paths, mixer channels and future shared settings can now appear on global Player pages while retaining one canonical plugin configuration. Plugins can also block launch with actionable requirements and opt required preparation actions into guided setup.

• Declare enum-based shared settings sections and validate global edits through the owning plugin. Unsupported section values are ignored.
• Check required integrations before importing or activating a game, with cancellation and bounded checks.
• Save individual setup values in their declared scope and expose contextual discovery guidance and automatic setup actions.

Validation: 99 portable Player API tests pass, including unsupported section handling, stop requests during pending startup, and owner-thread replay of held game state after preflight. Unity recompilation and discovery of the actual path/mixer consumers also pass. The consuming player and integration package were tested together through real archive preparation, verification, state initialization and automatic game launch in a Windows standalone build. Reviewed with Opus 5.5.

[greptile-apps]

Confidence Score: 5/5

[Medium impact] The PR appears safe to merge; both previous findings are addressed, with no new actionable issues found.

Summary

This PR adds shared plugin settings and checks required integrations before launch.

• Required plugins can stop a game launch until their checks pass.
• A Player setup flow can save required plugin settings one step at a time.
• Plugins can expose file and folder settings on a shared Paths page.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart TD
  A[Check required integrations] --> B{Requirements met?}
  B -->|No| C[Guide user through setup]
  C --> A
  B -->|Yes| D[Prepare and start plugins]
  D --> E{Required plugins running?}
  E -->|Yes| F[Allow table activation]
  E -->|No| G[Stop plugins and report blockers]

Loading

_{Reviews (3) · Last reviewed commit: "plugins: cancel pending startup and repl..." · Reviewed by Greptile}