Functional prototype · Evidence confidence: High

House of Mont RTS

A browser real-time strategy game with nine rival houses, resource harvesting, base building and AI or local two-player play.

Browser RTS game
Project IDPG-029
Repositoryhouseofmontlegacy
StageFunctional prototype
ConfidenceHigh
Also known as
House of Mont GameIron Dominion concept

01 · Purpose

The problem

Recreates the classic RTS loop as original browser-native IP.

02 · Experience

How it works

Players choose a house and match configuration, harvest resources, build a base, field units and attempt to break a rival commander.

Users
  • RTS players
Technology identified
  • React 19
  • TanStack Start
  • Browser game engine code

03 · Functional evidence

What actually exists

Verified working / present4
  • Match setup
  • Lazy-loaded game
  • AI/local two-player positioning
  • Original house framing
Partially verified1
  • Large-scale performance and complete campaign systems not verified
Designed / planned1
  • Expanded factions, campaigns and modes
Unknown / requires verification1
  • Multiplayer network support

04 · Development

What remains

Finish / verify
  • Large-scale performance and complete campaign systems not verified
Planned
  • Expanded factions, campaigns and modes
Resolve unknowns
  • Multiplayer network support

05 · Commercial

Business model

No verified model.

06 · Intellectual property

IP position

Original factions/lore/game configuration.

This archive records what the available project evidence says. It does not infer legal registration, patent grant, trademark ownership or regulatory status where that has not been verified.

07 · Assessment

Strengths and limitations

Strengths

  • Playable core architecture
  • Original RTS identity

Limitations / risks

  • Browser performance and depth require testing

08 · Evidence

What this record is grounded in

  • GitHub repository: simonmowatt1-sudo/houseofmontlegacy
  • Repository README / project brief where available
  • Implemented home route where available

A published URL means the project metadata records a deployment address. It is not represented as runtime-tested unless a separate verification pass confirms that deployment.

09 · Genealogy

Connections

Archive principle

Unknowns stay unknown until evidence changes them.
Back to Project Galaxy