Support
Feedback
How to reach the Veresk team with questions, bug reports and ideas.
Questions, bug reports and ideas are welcome on Telegram: @piavart.
What to include in a bug report
The more of this you send, the faster a problem can be reproduced:
- What you did and what you expected to happen.
- What happened instead: the error text or a screenshot.
- The project alias, the version name and the consumer name.
- For SDK problems: which SDK (Node.js or Unity) and its version, and your Node.js or Unity version.
- For API or MCP problems: the request (method and path) and the response status.
Never send an API token or a project encryption key. If one ended up in a message or a screenshot by accident, revoke the token or regenerate the key (see API tokens and Encryption).
Before you write
- Check the Quickstart: the most common problem is a version that was never published.
- For file format questions, see Config files.