The Changelog page helps you document your game's evolution, track meaningful changes, and create a complete history of your game's development journey. Here’s how you can make the most of it:
1. Accessing the Changelog
Navigate to your workspace and select the game you want to view or update.
In the game’s navigation tabs, click on “Versions” or “Changelog” (the exact label may vary).
You’ll be taken to the Version Tracking page for that game.
2. Understanding the Changelog Page
On this page, you’ll see:
Changelog Title: “Version Tracking”
Description: Explains the purpose—documenting your game’s evolution and tracking design decisions.
List of Versions: Each entry shows the version number, date, and a summary of changes.
3. Adding a New Version
To log a new version of your game:
Click “Add Version” or “Log New Game Version”.
A form will appear with the following fields:
Version: Enter a version number that makes sense for your workflow (e.g., 1.0, 2.5).
Date: Select or enter the date for this version.
Changes: Describe what changed in this version and why. Be as detailed as needed to help future-you (or collaborators) understand the evolution.
Submit the form.
You’ll see a loading indicator (“Adding version..”).
On success, you’ll get a confirmation (“Version added successfully”).
If there’s an error, you’ll see an error message (“Error adding version”).
4. Reviewing Version History
All logged versions are displayed in a list or table.
Each entry shows:
Version Number (e.g., Version 2.5)
Date
Summary of Changes
Use this list to review your design journey, reference past decisions, or prepare materials for publishers and collaborators.
5. Editing or Deleting Versions
If the UI allows, you may be able to edit or delete previous version entries.
Click the corresponding action (e.g., an “Edit” or “Delete” button) next to the version you want to modify.
Follow the prompts to update or remove the entry.
6. Best Practices
Be Consistent: Use a clear versioning scheme (e.g., 1.0, 1.1, 2.0) that matches your workflow.
Be Descriptive: Write detailed change summaries. This will help you and your team understand the evolution of your game.
Log Regularly: Add a new version entry whenever you make significant changes to your game’s design, rules, components, or other key aspects.
7. Troubleshooting
If you see errors when adding or editing a version, check your internet connection and try again.
If problems persist, contact support or check for updates.
8. Why Use the Changelog?
Track Progress: See how your game has evolved over time.
Reference Past Decisions: Understand why changes were made.
Collaborate Effectively: Keep your team and collaborators in the loop.
Prepare for Publishing: Create a professional history of your game’s development for publishers or partners.