Browsing gems is one thing; deciding which gems a project uses is another. OPAL gives each project its own gem configuration, reached from the project’s Gems quick-action (available once the project’s engine is resolved).
Enable and disable gems
The project gem view reuses the same list-and-inspector layout as the Asset Library, but scoped to the gems available for that project’s engine plus your repository gems. Toggle a gem active or inactive for the project, and OPAL keeps the project’s gem set in sync — updating project.json’s gem list and the project’s CMake gem list together.
Required dependencies
Gems that are pulled in as dependencies of an active gem are marked with a Required dependency badge and can’t be switched off directly — OPAL won’t let you disable something another active gem needs.
Sorting
Sort the list to suit the task: Name A–Z, Name Z–A, Active First, or Inactive First.
Downloading a gem’s source
Per gem, you can download the gem or its source — OPAL uses git clone or an archive download as appropriate (see Repositories & sources for how credentials and the git/archive choice work).
Engine not resolved
If the project’s engine can’t be resolved, the page shows an engine-missing banner — resolve the engine first (see status & health) and the gem configuration becomes available.