Miner2149 JS
An in-progress browser reimplementation of Michael Baker's Miner2149, a mining-colony simulation originally released for Palm OS.
Play it at miner2149.com · View the original source release · Changelog
Attribution and licensing status
Miner2149 was created by Michael Baker, who granted the project owner written permission to use the original source, formulas, sprites, game imagery, and documentation for this personal, noncommercial, not-for-profit browser project. This project-specific permission does not grant third parties a license to copy or redistribute that material, and the project is not otherwise affiliated with or endorsed by BProjectsGames.
Gameplay
Use a mouse, trackpad, or touch input to:
- Start a new mine and launch probes.
- Select an asteroid and build a colony across its three levels.
- Manage credits, workers, morale, life support, food, health, power, and storage.
- Mine and sell diridium while keeping the colony viable through a two-year term.
The zoom control above the game enlarges the intentionally low-resolution Palm-style interface.
Local development
Prerequisites
- Node.js 22.23.4 or newer 22.x, or 24.22.1 or newer 24.x (
.nvmrc pins 24.22.1)
- npm 9 or newer
git clone https://github.com/gabriensymons/miner2149-js.git
cd miner2149-js
npm ci
npm run dev
Open http://127.0.0.1:8080. Useful commands:
| Command | Purpose |
|---|
npm run dev | Serve the static site locally with caching disabled |
npm test | Run unit and repository-hygiene tests |
npm run test:smoke | Run the Chromium startup smoke test |
npm run build | Validate JavaScript and vendored browser dependencies |
npm run verify | Run checks, tests, browser smoke test, and dependency audit |
Architecture
- Plain HTML, CSS, and native JavaScript modules
- PixiJS 6 for rendering and pointer interaction
- Local storage for offline save slots
- A disabled, test-covered Supabase adapter reserved for future optional cloud saves
- Node's built-in test runner for persistence, source-parity simulation specifications, and source-hygiene tests
- Playwright for data-isolated browser smoke tests
Source-derived formulas, ordering decisions, intentional compatibility fixes, and preserved quirks are summarized in Original Behavior Compatibility Notes.
PixiJS is pinned in package.json and vendored for deterministic static deployment; its license is preserved in Third-Party Notices. The public build does not load the Supabase browser SDK while cloud saves are disabled.
Accounts and save-game security
The public demo currently disables account creation, sign-in, and remote save operations. Cloud-save safety depends on correctly configured Row Level Security (RLS), and the deployed project's policies have not yet been independently verified. RLS verification remains a release blocker before those features can be enabled again.
The dormant adapter scopes reads and writes to the authenticated user as defense in depth, restricts writes to known save slots, and does not log sessions or save data. Client-side filtering is not a substitute for RLS. A Supabase project URL and anonymous client key appeared in prior browser code; those are public client identifiers rather than privileged credentials. See the Supabase security checklist.
Local saves are stored for the browser origin. The dormant synchronization policy keeps local slots authoritative and uses cloud data only to fill missing slots, preventing a stale remote record from replacing a newer local save after a failed write.
The automated browser smoke test blocks HTTP and WebSocket connections to Supabase-hosted endpoints, verifies those blockers with synthetic probes, and never touches production account or save-game data.
Project status
This is an in-progress, local-save-only public demo/preview—not a finished v1.0 release. Core colony building, local saves, reports, economic systems, source disasters, meteor defense, and two-year completion scoring are present; accessibility, mobile polish, deterministic browser scenarios, and any future opt-in online leaderboard remain on the roadmap.
Contributions are welcome only where the contributor has the right to submit the material. Read CONTRIBUTING.md and SECURITY.md first.
