Should BridgeMod focus on making mod systems port-friendly?

[rootedresilientshop-pixel]

One of the biggest pain points in game porting is mod support. A PC game with Steam Workshop integration has to completely rip that system out when porting to console — Workshop doesn't exist there. The result is usually one of two outcomes: the console version ships without mods entirely, or the studio spends months rebuilding the mod pipeline for a proprietary solution.

BridgeMod is already designed to avoid this. Because it validates locally, uses no cloud dependencies, executes no arbitrary code, and works with pure data mods, the same BridgeMod integration you write for PC should work on console without changes. That's not a theoretical claim — it's how the SDK is architected.

The question is: should we make this a primary selling point?

Specifically, we're thinking about:

• Documentation: A dedicated porting guide — "Your mod system, from PC to console" — walking through what stays the same and what (if anything) needs adjustment per platform
• Certification guidance: Notes on how BridgeMod's safety model aligns with Xbox and PlayStation certification requirements (no arbitrary code execution, sandboxed data access, offline validation)
• Porting studio outreach: Making BridgeMod discoverable to studios that specialize in cross-platform ports

We'd love to hear from anyone who's dealt with this problem:

• Have you ever had to strip mod support during a console port?
• Would a mod system that "just works" across PC and console have saved you time?
• What would you need to see from BridgeMod to trust it for a console submission?

Even if you haven't ported a game, your perspective on whether this direction makes sense is valuable.