> For the complete documentation index, see [llms.txt](https://jiffyjrdevelopment.gitbook.io/jiffyjrdevelopmentdocs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jiffyjrdevelopment.gitbook.io/jiffyjrdevelopmentdocs/jiffy-jr-development-docs/jiffy-minigames/troubleshooting.md).

# Troubleshooting

## Nothing happens when an interaction triggers

**Symptoms:** No UI appears, no console output, the game just doesn't open.

1. Confirm `ensure jiffy-minigames` is in `server.cfg` and the resource started without errors.
2. Set `Config.Debug = true` and retry — a debug line should appear in the F8 client console.
3. If the call comes from a legacy resource, check [Compatibility Layer](/jiffyjrdevelopmentdocs/jiffy-jr-development-docs/jiffy-minigames/compatibility.md) — you may need a standalone shim.

## `exports['ps-ui']:Circle` is nil / function is nil

The calling script is looking for a resource literally named `ps-ui`. Install the `compat/ps-ui` shim and ensure it in `server.cfg`:

```cfg
ensure jiffy-compat-ps-ui   # if you renamed it
# or just:
ensure ps-ui                 # if the shim folder is named ps-ui
```

The same applies to any other export-name-bound resource. See [Compatibility Layer](/jiffyjrdevelopmentdocs/jiffy-jr-development-docs/jiffy-minigames/compatibility.md).

## Minigame NUI is stuck / camera is locked after a crash

The NUI focus may have been left on. Run:

```
/jmg_cancel
```

If test commands are disabled, restart the resource:

```
restart jiffy-minigames
```

Focus is also released automatically on player death and on resource stop.

## "No minigame appears" with ps-ui calls

ps-ui uses both event-based and export-based calls depending on the script. Check which one your script uses:

* If it calls `TriggerEvent('ps-ui:...')` — handled by the built-in adapter, no shim needed.
* If it calls `exports['ps-ui']:Circle(...)` — you need the `compat/ps-ui` shim running under that exact resource name.

## Framework was not detected correctly

Force it in `editable/config.lua`:

```lua
Config.Framework = 'qb'          -- QBCore
Config.Framework = 'esx'         -- ESX
Config.Framework = 'standalone'  -- no framework
```

## Compatibility adapter call is not being intercepted

1. Check that the adapter is enabled in `Config.Compatibility`.
2. Set `Config.LogCompatCalls = true` — every incoming compat call is logged when this is on.
3. Confirm jiffy-minigames starts **before** the script making the call in `server.cfg`.

## Two minigames opened at the same time / UI overlap

`Config.AllowConcurrent = false` by default, which blocks a second game from starting while one is running. If two are opening anyway:

* Check that there is no other minigame resource still running alongside jiffy-minigames.
* If you want concurrent games intentionally, set `Config.AllowConcurrent = true`.

## Test commands return "access denied"

The server has not granted your player the required ace. Add one of the aces listed in `Config.TestCommandAce` to your player, or add the dedicated ace:

```cfg
# server.cfg — replace with your actual license identifier
add_ace identifier.license:XXXXXXX jiffy-minigames.test allow
```

Alternatively, during local dev only, set `Config.TestCommandAce = false` (open access).

## Wrong framework detected on startup

The auto-detect reads exports from `qb-core` or `es_extended` at startup. If neither is found it falls back to standalone. If you see the wrong framework in the startup log, force it with `Config.Framework`.

## Still stuck?

Open a ticket in the **JiffyJrDev Discord** with:

* The exact error or behavior
* Your `server.cfg` ensure order (the lines near jiffy-minigames)
* The F8 client console output with `Config.Debug = true`