Configure saves, leaderboards and events

Before you start

These settings declare features to the platform. Your game still needs the corresponding SDK calls. Save a checkpoint before changing a published game’s save format.

Save format

1. Open Project settings > Saves.
2. Review the current format and any live release format shown.
3. If you are changing the structure of saved data, update the format and implement migration from older saves in your code.
4. Run the game and test loading older data as well as starting with no data.
5. Read the compatibility warning before publishing or later rolling back.

Changing the number alone does not migrate player data.

Leaderboards

1. Open Leaderboards in Project settings.
2. Choose Add a leaderboard.
3. Give it a unique id and title.
4. Choose whether higher or lower scores are better and how scores are displayed.
5. Update game code to submit scores to that declared id.
6. Run and test the relevant scoring flow, then save.

Events

1. Open Level and analytics events.
2. Add an event with a valid unique name and a description.
3. Declare the numeric properties it carries.
4. Emit the matching event from the relevant point in game code.
5. Use the preview’s SDK tools to inspect calls.

Events carry numbers, not player text or personal details. Declaring events does not make every planned analytics report available.

What happens next

Preview data is for testing. A new preview build gets fresh in-memory saves; a restart of the same build retains them unless you clear them. Test the live player experience after release as well.

Still stuck?

Email support@4rc4d3.com with the project or game name, if relevant, the action you tried and the exact error. Never include passwords, authenticator codes, backup codes or AI keys.