Get help without exposing your game.

1. Technical help

Search existing issues first. If you need a new issue, include:

• whether the game is web, Unity, or server-side;
• the feature you are adding and the step that failed;
• what you expected and what happened instead;
• a sanitised error code or message, with tokens, URLs containing secrets, wallet proofs, and personal data removed; and
• the public game ID only if you are comfortable associating it with the public issue.

The tracker is currently attached to the public Blockmaker Unity SDK repository, but may be used as the temporary intake route for general Blockmaker, web, admin, and Unity questions. Support is best-effort during early access; no response time is promised.

2. What not to post

Never include any of the following in GitHub, screenshots, AI chat, or copied logs:

• a Blockmaker sk_ server key, provider API key, admin secret, or .env file;
• a wallet recovery phrase, private key, reward-wallet credential, or signed ownership proof;
• an admin or player session token, one-time login code, backup key, database, or unredacted request headers;
• a player email, save data, IP address, or other personal information; or
• working exploit details or steps that could put other games or assets at risk.

If a key or token may already be exposed, revoke or rotate it before asking for help. Do not wait for a support reply to protect a wallet or disable a compromised integration.

3. Security reports

There is not yet a published private vulnerability-reporting inbox. Do not put a vulnerability, exploit, affected identifier, secret, or player data into a public issue.

Open a minimal issue titled “Private security reporting route requested”. Say only that you have a potentially sensitive Blockmaker report and need private handling instructions. Wait for a verified project maintainer to provide a private route before sharing details. Do not test against another developer’s game, access data, move assets, or degrade the live service.

If you are responding to an active compromise, first revoke exposed credentials, remove the affected integration from service where safe, and secure the relevant wallets. The public tracker is not an emergency-response service.

4. Account and data requests

For account, game-deletion, or privacy requests, open a minimal issue asking for private handling instructions. Do not include your contact email, wallet address, player information, or the data you want removed in public.

Blockmaker may ask the account owner to complete a fresh wallet proof before changing or deleting an account-owned game. Requests are handled as described in the Privacy notice; blockchain records and data controlled by a game developer or third party cannot be removed by Blockmaker.

5. Help for players

Contact the developer or support channel for the game you were playing first. That developer controls the game’s rules, content, player relationship, and decisions about items, saves, eligibility, rewards, purchases, moderation, and refunds.

If the game developer believes the problem is in Blockmaker, they can report a sanitised technical issue. Do not post your email, wallet proof, session token, save data, or purchase details in the public Blockmaker tracker.