Support
Start with these three#
- Troubleshooting — symptoms in the order people meet them, each with a cause and a fix. Most reports are answered here.
- Limitations — several "bugs" are documented boundaries. If the framework is behaving as described there, it is not a defect, and we would rather tell you that than pretend otherwise.
- FAQ — the questions that are not symptoms.
Run the validation pass before writing#
Tools → PersistKit → Validate Scene and References checks your configuration, the package's files, the resolved dependencies, the platform, the identity scan, and a real write/read/delete through the framework's storage. Its output is exactly what a maintainer needs, and it is safe to paste: diagnostics never contain payload bytes, keys or credentials.
Need help?#
Need help integrating PersistKit into your project? Have a question, found an issue, or need clarification? Contact us at contact.nexusforge@gmail.com — we're happy to help. We read every message; we do not promise a response time, and we will not invent one here.
What a useful report contains#
- PersistKit version (
Persist.Diagnostics.Report()prints it), Unity version, target platform, and whether the build is Mono or IL2CPP. - The exact error code (
PK-…) and the message. Codes are stable, so the code alone is often enough. - The diagnostics lines around the failure. They are safe to paste.
- The smallest reproduction you can manage. Environment-specific faults — a read-only filesystem, a full disk, a suspended app — are extremely common in this domain, so say what the device was doing.
- If it involves Unity objects: whether the identity scan reported missing, duplicate or unstable ids.
What to expect#
- **A failure that produces a wrong result rather than an error is treated as serious.** A save system that lies is worse than one that fails, and that is the class of report we most want.
- A report that a documented limitation is inconvenient is welcome, but it is a design discussion rather than a bug — Limitations is where to start that conversation.
- We read every report. We do not promise a response time, and we will not invent one here.
Security issues#
Report privately to contact.nexusforge@gmail.com with a subject line beginning SECURITY. Include the affected version, the configuration (integrity, encryption and authentication settings), and a description of the impact.
Contact and channels#
| Channel | Use it for |
|---|---|
| contact.nexusforge@gmail.com | PersistKit support: questions, bug reports, documentation corrections, security reports |
| Studio news and enquiries | |
| Documentation | The first place to look, and the place we keep accurate |
We do not operate a public issue tracker or a community chat for this package, and this site will not pretend otherwise by linking to an empty one.
Documentation corrections#
Each documentation page ends with a link to report a problem with it. If a page and the package disagree, the package wins and the page is a documentation bug — say which page and which sentence, and it gets fixed.