Game Profiles and Library

Game Profiles and the Community Library

Per-game auto profiles

Assign a trigger profile to a game and OpenDS5 applies it automatically when that game is running, and restores things when it exits. Detection watches running processes — no game integration needed, which is exactly what makes it work for games with zero native DualSense support.

You can also pin a profile manually to force it active regardless of what's running (and unpin to go back to auto).

The profile library

The library (inside Game Trigger Profiles) is a searchable catalog of community-made game profiles. It lives in its own repo — OpenDS5-Profiles — so new profiles reach everyone's app without waiting for an app release.

Search results come in three kinds:

Tier	Meaning
Verified	Reviewed profiles; sort above community ones
Community	Contributed profiles, validated by CI but not hand-reviewed
Native	Not a profile — a marker that this game has native DualSense trigger support (seeded from PCGamingWiki, 136 games). Use the wired bridge and let the game do the work; a custom profile would fight it.

Install a profile from the library and it behaves like one of yours: editable, assignable, exportable. Reset returns an edited library profile to its published version.

Import / export

Profiles are plain JSON. Export from the editor to share a file; Import to load one. This is also the format the library uses.

Contributing your profile

Made something great? Publish it:

1. Export the profile from the app.
2. Open a PR against OpenDS5-Profiles:
   • one game per PR,
   • branch named after the game.
3. CI validates the profile with the same rules the app enforces.
4. Once merged, the index rebuilds automatically and your profile appears in everyone's in-app library.