adding log camps

2026-05-18 20:42:49 -05:00
parent 3167558e04
commit bf75f02dbb
12 changed files with 365 additions and 35 deletions
@@ -8,6 +8,7 @@ Tracks hex locations for the territory map.
 - `GET /api/locations?minQ=-7&maxQ=7&minR=-7&maxR=7` List a coordinate range, constrained by visibility for USER.
 - `GET /api/locations/{q}/{r}` Fetch one visible location for USER, any known location for SUPER.
 - `POST /api/locations/claim` Claim visible unclaimed territory for the authenticated user. Normal players spend one completed Scout.
+- `POST /api/locations/build` Build on controlled territory.
 - `GET /api/locations/home` Get the authenticated user's home location.
 - `POST /api/locations/home` Assign or return the authenticated user's home location.
 - `GET /api/locations/visible` Get locations visible to the authenticated user.
@@ -27,7 +28,8 @@ locations are unowned `Open` records until claimed by a player.

 Player resource state is stored server-side in the `PlayerResources` collection.
 New players start with 100 gold. A player's headquarters generates 10 gold per
-minute. Generation is applied lazily when the resource record is read.
+minute. Log Camps generate wood. Generation is applied lazily when the resource
+record is read.

 ## Units

@@ -35,3 +37,9 @@ Unit training is stored server-side in the `UnitTraining` collection. The first
 unit type is `Scout`, which costs 50 gold and takes 60 seconds to train.
 Finished training is completed lazily when unit state is read. Claiming an
 unclaimed visible location consumes one completed Scout.
+
+## Buildings
+
+Buildings are stored on location records. The first building type is `LogCamp`,
+which can be built on controlled Forest territory and adds 5 wood per minute to
+the owning player's resource generation.