SXP Game Factory
SXP's game production system: engine tooling, the games themselves, and a release step that builds, certifies and hands off web demos.
Why it exists
So every game travels from source to a web release by one repeatable path, and the Factory itself never publishes anything.
Where it stands
Used inside SXP. Every game on SXP Games comes through it, and each public release still needs the Founder's approval.
This is a description, not a window. Nothing on this site connects to the system, and no live data from it is shown.
How it works
- Game sourceAn accepted commit
- BuildGodot or Phaser, for the web
- CertifyTests and a certification record
- Hand offFiles with hashes and provenance
- Founder approvesBefore every public release
- SXP GamesPlayable in the browser
What it does
- Builds Godot and Phaser games for the web
- A game registry holding every demo's status and version
- One command that stages a single game's release from an accepted commit
- Refuses a wrong request before building, and records a hash for every file it hands off
What it does not do
- Never deploys or publishes; that step belongs to the SXP site and needs approval