Keep a game current
Some files in your game's repo are Brain's: its CI workflows, the shared rules in AGENTS.md, and the Brain SDK. ase sync brings them up to date with the ase you're running. Run it in the game's repo:
ase sync --game neon-drift
ase prints each file it updated, or says the game is up to date. Review the changes and commit them like any other change.
What sync changes
| Kind | Files | What sync does |
|---|---|---|
| Brain's files | .github/workflows/ci.yml, build.yml, release.yml, website.yml |
Rewrites them |
| Brain's blocks | AGENTS.md and .gitattributes, between brain:begin and brain:end |
Rewrites only the block; your lines after it stay |
| Registry block | The end of brain/game.toml |
Rewrites ASE Brain's read-only values for the game |
| The SDK | The engine project's Brain SDK | Installs the newest release |
| Scaffold | websites/main/README.md, websites/main/public/index.html and style.css |
Adds them only when missing |
Everything else is yours from the first commit, and sync never touches it: your code, scenes, assets, release.toml, the rest of brain/game.toml, brain/events.toml and your website's content.
Because sync rewrites Brain's files, don't edit them. A change you need there belongs in ASE Brain.
Options
ase sync --game neon-drift --project path/to/repo # a repo other than the current folder
ase sync --game neon-drift --keep-addon # leave the installed SDK as it is
Only the SDK
To update just the SDK, without the workflows and rules:
ase sdk update # the newest release
ase sdk update --version 0.2.0 # a specific one
ase sdk status # the installed version against the newest
Your engine also keeps the SDK current on its own when you open the project. See Install the SDK.
A game that isn't on ASE Brain yet
ase sync needs the game in your studio. For a repo that isn't, run ase games adopt first; it ends with a sync.