Evan
075547b7b6
## Description: Incremental GPU border recompute — sequel to #4159. On 10 yo low-end chrome book this increased performance by ~5fps. I'm now able to get 40fps on GWM. `BorderComputePass` previously re-ran its fragment shader over every tile on the map every time any input changed (tile flip, highlight, relation, defense post). Cost was O(mapW × mapH) per invalidation, and tile flips invalidate it ~every render frame in live play. This PR adds `BorderScatterPass`, which runs the same fragment shader but rasterizes only one POINT per dirty tile (plus its 4 cardinal neighbors, to cover the cardinal-neighbor read in the border shader). Cost is O(dirty tiles) regardless of map size or spatial distribution. ### What changed - New `BorderScatterPass` — owns its own FBO, VAO, and instance buffer; shares the border fragment shader with `BorderComputePass` so the two paths can't diverge in output. - `BorderComputePass.draw()` now picks per frame: - **Full recompute** — when `globalDirty` is set by highlight / relation / defense-post changes (those affect tiles across the whole map). - **Scatter** — when only per-tile patches have been queued via `patchTile()`. - `TerritoryPass.flushTileTexture()` now returns `"none" | "full" | "scatter"` instead of `boolean`, so the renderer can pick the right downstream invalidation: - `"full"` → `borderPass.markGlobalDirty()` (full tile upload supersedes per-tile patches). - `"scatter"` → no-op; per-tile patches were already pushed via the wired `borderPatchConsumer` callback during drip drain. - Renderer wires `territoryPass.setBorderPatchConsumer((x, y) => borderPass.patchTile(x, y))` so every per-tile scatter write to `tileTex` also schedules an incremental border recompute for that tile + its neighbors. ### Known limitation Highlight-thicken rings (within `uHighlightThicken` of a changed tile) are NOT incrementally repainted — they'll lag visually until the next full recompute. In practice this is short-lived (the next highlight change or seek triggers a full recompute) and not visible during normal play; the trade is documented in the `BorderScatterPass` header. ## Please complete the following: - [x] I have added screenshots for all UI updates - [x] I process any text displayed to the user through translateText() and I've added it to the en.json file - [x] I have added relevant tests to the test directory ## Please put your Discord username so you can be contacted if a bug or regression is found: evan
OpenFront.io is an online real-time strategy game focused on territorial control and alliance building. Players compete to expand their territory, build structures, and form strategic alliances in various maps based on real-world geography.
This is a fork/rewrite of WarFront.io. Credit to https://github.com/WarFrontIO.
License
OpenFront source code is licensed under the GNU Affero General Public License v3.0
Current copyright notices appear in:
- Footer: "© OpenFront and Contributors"
- Loading screen: "© OpenFront and Contributors"
Modified versions must preserve these notices in reasonably visible locations.
See the LICENSE for complete requirements.
For asset licensing, see LICENSE-ASSETS.
For license history, see LICENSING.md.
🌟 Features
- Real-time Strategy Gameplay: Expand your territory and engage in strategic battles
- Alliance System: Form alliances with other players for mutual defense
- Multiple Maps: Play across various geographical regions including Europe, Asia, Africa, and more
- Resource Management: Balance your expansion with defensive capabilities
- Cross-platform: Play in any modern web browser
📋 Prerequisites
- npm (v10.9.2 or higher)
- A modern web browser (Chrome, Firefox, Edge, etc.)
🚀 Installation
-
Clone the repository
git clone https://github.com/openfrontio/OpenFrontIO.git cd OpenFrontIO -
Install dependencies
npm run instDo NOT use
npm installnornpm ibut instead use ournpm run inst. It runs the safernpm ci --ignore-scriptsto install dependencies exactly according to the versions inpackage-lock.jsonand doesn't run scripts. This can prevent being hit by a supply chain attack.
🎮 Running the Game
Development Mode
Run both the client and server in development mode with live reloading:
npm run dev
This will:
- Start the webpack dev server for the client
- Launch the game server with development settings
- Open the game in your default browser (to disable this behavior, set
SKIP_BROWSER_OPEN=truein your environment)
Client Only
To run just the client with hot reloading:
npm run start:client
Server Only
To run just the server with development settings:
npm run start:server-dev
Connecting to staging or production backends
Sometimes it's useful to connect to production servers when replaying a game, testing user profiles, purchases, or login flow.
To replay a production game, make sure you're on the same commit that the game you want to replay was executed on, you can find the
gitCommitvalue viahttps://api.openfront.io/game/[gameId]. Unfinished games cannot be replayed on localhost.
To connect to staging api servers:
npm run dev:staging
To connect to production api servers:
npm run dev:prod
🛠️ Development Tools
-
Format code:
npm run format -
Lint code:
npm run lint -
Lint and fix code:
npm run lint:fix -
Testing
npm test
🏗️ Project Structure
/src/client- Frontend game client/src/core- Deterministic game simulation/src/server- Backend game server/resources- Static assets (images, maps, etc.)
🤝 Contributing
Contributions and translations are welcome! See CONTRIBUTING.md for the workflow, the approved-issue process, project governance, and translation info.