Troubleshooting
Fast checks for the most common setup problems before opening a ticket.
Server consoleF8 consoleConfiguration
Resource will not start
- Confirm mysticky_bridge starts first.
- Confirm your framework and required providers start before the bridge.
- Do not rename purchased resource folders.
- Read the first error—not only later cascade errors.
- For Drug System, confirm the addiction SQL table exists.
Interaction is missing
- Verify the configured coordinates and job.
- Confirm target or fallback interaction settings are enabled.
- Confirm the selected provider is running and detected in the bridge startup summary.
- Test without admin bypasses using a normal player character.
Items or rewards fail
- Confirm every configured item exists with the exact same name.
- Check inventory capacity and item weight.
- Check account names such as cash, bank, or black_money.
- If an item was renamed, update every matching config reference.
What to send support
- Resource name and manifest version
- Framework and provider resource names
- Complete server-console error and relevant F8 error
- Screenshot or short video of the issue
- The configuration section involved, with secrets removed
- Steps to reproduce on a clean test character
Good to know
Support cannot diagnose “it’s broken” without enough context. Detailed reports are resolved much faster.