Tech Notes
Under The Hood

How SpacePimpin Is Built

SpacePimpin is built on a lean web stack with real backend state, real round flow, and room to grow. This page is here for players who want the honest technical picture without turning the whole thing into a dry engineering whitepaper.

OpenAI Codex Static HTML Custom CSS Vanilla JS Node + Express MySQL

Core Stack

The structure behind the game is intentionally direct. It does the real work a browser game needs without burying everything under a giant framework pile.

OpenAI Codex

  • Used as an active development partner throughout the rebuild.
  • Helped with implementation, debugging, layout cleanup, feature design, and deployment flow.
  • Worked more like a technical collaborator than a one-shot generator.

Frontend

  • Static HTML pages define the site shell and main game surfaces.
  • Custom CSS drives the visual style, page flow, and responsive layout.
  • Vanilla JavaScript handles live data rendering, session flow, and player actions.
  • The project avoids a heavyweight frontend framework on purpose.

Backend

  • Node.js with Express powers the live API.
  • The backend handles account flow, round flow, player state, stores, messaging, and combat actions.
  • Admin and moderation tools are controlled server-side rather than just hidden in the interface.

Database

  • MySQL stores accounts, round entries, empire state, stash, morale, messages, and rankings.
  • Permanent account identity is separated from per-round empire state.
  • That separation is one of the most important structural choices in the current build.

Gameplay Architecture

A lot of the game already runs as proper live state rather than placeholder text and fake browser numbers.

Accounts & Rounds

  • Account creation, login, confirmation flow, and password reset are implemented.
  • Players now join rounds separately instead of being shoved straight into the game world.
  • Round-specific usernames and starting planet choices are part of that entry flow.

Empire State

  • Turns, cash, workers, gangsters, stash, morale, exposure, and net worth are persisted.
  • Worker cut, drug coverage, supply pressure, and morale all feed into live state changes.
  • Dashboard, profile, dossier, and store screens reflect that state instead of static filler values.

Conflict & Intel

  • Attacks, poaches, party hits, and scouting are all real actions in the round.
  • Exposure, range restrictions, scouting depth, and dossiers are part of that system.
  • Combat is still growing, but it is already more than a visual mockup.

Admin & Maintenance

  • Moderation and account-management tools exist inside a hidden admin surface.
  • Player state, round usernames, and account status can be managed from there.
  • The idea is to keep control close to the live game without advertising it to everyone else.

Spacecrime's Influence

Spacecrime is not something this project is trying to flat out copy, Spacecrime was a huge influence in this game.

Spacecrime was a huge part of my early adulthood — and for a lot of others too.

Spacecrime existed at a time when other turn based browser games existed, such as Pimpwar and Happypimpin, What made Spacecrime great was its simplicity and its community.

What Carried Over

  • The round-based crime-game rhythm is a major influence.
  • The balance between money, power, pressure, reputation, and rivalry all comes from that lineage.
  • Even when SpacePimpin makes different technical choices, a lot of the design thinking still starts with what made that older world memorable.
  • This rebuild is trying to respect that legacy while shaping something more manageable for the current site and current player base.

Why The Stack Looks Leaner

Spacecrime came from an older era of browser games and heavier web stacks. SpacePimpin is deliberately lighter, but that is a design choice rather than a lack of structure.

Current Philosophy

  • Keep the architecture direct while the systems are still being designed and sharpened.
  • Use fewer layers until more layers are actually justified.
  • Let the game deepen where the gameplay demands it instead of carrying dead complexity for the sake of appearances.
  • Build the world first, then add more machinery when the world genuinely needs it.

Still To Come

Some of the bigger pieces still to land are also the ones that will deepen the architecture the most.

Travel & Markets

  • Spacecraft, timed travel, cargo limits, and movement cost.
  • Planet-specific economies and price spread for real trading play.
  • More strategic reasons to move rather than sitting on one world forever.

History & Archives

  • Read-only archived rounds with preserved state.
  • Deeper attack history and defender logs.
  • Cleaner long-term round memory instead of everything living only in the current season.