Electrify

Build power plants, keep the lights on, and make your grid cleaner. Electrify is a mobile-friendly tycoon game about electricity markets, where weather, fuel prices, and unexpected events put your plans to the test.

Play Electrify in your browser, on desktop or mobile.

Run locally

Install Node.js 24 and Git LFS, then:

git clone https://github.com/toddmedema/electrify.git
cd electrify
git lfs install
git lfs pull
npm ci
npm run check:assets
npm start

Open localhost:3000. The app reloads as you edit. Online accounts and leaderboards need a Firebase API key from a maintainer; see setup notes.

Start contributing

There are plenty of ways to help: tune game balance, write a scenario, improve a tutorial, fix a bug, or make the interface easier to use.

• Browse issues to find work or share a bug report or idea.
• Read the contributor guide for a map of the code and how to check your changes. The app uses React 18, Redux Toolkit, and TypeScript.
• Keep your pull request focused and explain what changed and how you checked it.

For a quick feedback loop, run npm run test:once -- <name> for one test suite or npm run sim -- --scenario 103 to try a scenario without a browser. Use npm run check during development and npm run check:ci before pushing code changes. For prose-only Markdown changes, review the text and run git diff --check.

Each check invocation prints a report path under .tmp/check-runs/. The report records its source commit and working-tree fingerprint, runtime, selected gates, pass/fail/skip results, and retained command logs. Production browser, multiplayer, and controller reports preserve individual attempts, including successful runs and retries. A changed source fingerprint at completion invalidates that run; partial runs remain separate evidence. Native packaged Electron and Firestore rules checks are reported as outside the local runner's scope.

Use npm run check -- --report <report.json> to produce a review summary with the tested source, runtime, full or partial scope, and whether the current snapshot still matches. It reads existing evidence without rerunning checks. Use npm run ci:history to group the latest 100 PR runs by recurring test and branch, including passed retries; pass a smaller count with npm run ci:history -- 20. Gate counts overlap, and unreadable logs are reported explicitly. npm run ci:failures -- <pr> remains the detailed reproduction guide for an individual failure.

Explore further

• Simulation guide: run scenarios and check game economics.
• Mods and Steam Workshop: create and share community scenarios for the desktop edition.
• Desktop and Steam: build an offline app or prepare a Steam release.
• Weather and assets: add cities, update weather, and work with icons and manual figures.
• Releases: web deployment, version metadata, and account storage.

License

Electrify is source available under the MIT License with Commons Clause. The Commons Clause is a condition on the MIT License, not an alternative license.

You can use, study, modify, and share Electrify subject to these terms. The license does not permit selling the software as defined by the Commons Clause: providing a product or service for a fee or other consideration whose value derives entirely or substantially from Electrify, including paid hosting and related consulting or support services. See the full license and Commons Clause FAQ for the scope of this restriction.

Versions containing this license notice use the combined license. Versions previously distributed under MIT retain their MIT permissions. Third-party components and assets with separate license notices retain their own licenses.

Modding

Community scenarios work in solo play and co-op in the Steam/desktop edition. Open Mods to import a JSON file or browse Steam Workshop. Choose Play to review a scenario's setup, goals and announced events before starting. Co-op guests receive the host's scenario without installing it. Modded games are unranked and earn no official scores or achievements.

Installed scenarios work offline. Updates apply to new games; existing saves keep their rules even if you update or remove the package.

To create a scenario, choose Save authoring template, edit the JSON, then reimport it to try your changes. You can change costs, schedule events, offer choices, set goals and reuse bundled challenge arcs. Packages contain data only; scripts and custom media are unsupported.

Start with the authoring guide and example packages. Use the format reference for fields and limits, and the arc reference for reusable challenge content.

To share, send the JSON file directly or connect to Steam and choose Publish. After editing, reimport with the same id and choose Upload update to update its Workshop item. Complete Steam's Workshop agreement if prompted.