8.1 KiB
8.1 KiB
Roadmap
Each milestone ends with tests green, ConfigLint green, and something playable in the UI.
M1: Village, economy, buildings
- Backend scaffold: Laravel 13, Docker Compose with Traefik, MySQL, Redis, Pest, Sanctum, laravel-websockets
- Frontend scaffold: Nuxt 4, TS,
ssr: false, WS client, i18n (en), email + password login/register WorldConfigplusconfig/game/world.php,economy.php,buildings.php. Core set: headquarters, storage, farm, timber camp, clay pit, iron mine, hiding place, wall, rally pointConfigLintwith the lock checks from architecture.md- Migrations and models: worlds, players, villages, buildings, build_orders, game_events
- Seeders: default world (speed 4, armies at unit speed 0.5; speed 1 until the pacing change) and dev world (speed 100)
Production+Settle(base trickle, staffing curve, storage caps) with unit testsPopulation(food budget, villagers, worker assignment by priority) with unit testsBuildingRules(cost, time, workers, output, instance_cost_factor, levels from 0) with unit tests- Building space (per-type space, village budget, reserved for queued builds, unique types) with unit tests (replaced the first tile grid)
BuildQueue(builders by HQ level, next unblocked order) with unit tests- Event engine:
game_events,game:eventsworker, per-village catch-up, idempotent handlers - Actions: join world (HQ 0, storage 0, farm 0), build, upgrade, demolish with refund, cancel with refund, set priority. Feature tests with time travel
- WS controllers
village.show|build|upgrade|demolish|cancel|staffand avillage:updatedpush - UI: resource bar with projected values, population and food budget, building table with staffing, village as a low-poly isometric diorama (full width), build queue with builders and countdowns
M2: Map and barbarian villages
- Spawn placement, like Die Stämme: the world starts at 0|0 (negative coordinates, DS continent names) and grows ring by ring with all villages at DS density; players pick a direction (random, NW, NE, SW, SE) and never land right next to another player
- Barbarian villages come with the players: 1.3 per join on average, within a few fields of the new village, random levels;
game:reset-worldstarts a world over - Barbarian growth over time (world config)
- Barbarian waves: every 5 to 9 world days 1.5 new barbarian villages per active player settle within 8 fields of them, so a world with few players keeps moving
map.view {world_id, x, y, w, h}with village owner, points and continent; village points from building levels- UI: Die Stämme-style coordinate map with rulers, continent lines, jump-to and village info
M3: Units, upkeep, starvation
config/game/units.php: spear, sword, archer, light cav, heavy cav, ram, catapult, nobleman, with food upkeep- Barracks, stable, workshop, academy as building instances (several barracks run parallel recruit queues); only these advanced buildings get requirements, e.g. academy needs headquarters + barracks
- Recruiting turns villagers into soldiers; lazy per-unit completion
- Levy: draft workers as militia, automatic return
- Starvation: zero-crossing event, grace timer, desertion order
- UI: recruit forms, troops overview, food balance warnings
M4: Attacks, combat, looting
TravelTime(slowest unit, distance, unit speed, travel mode) with unit tests- Travel modes from
movement.php; warning time from visibility and detection radius; watchtower - Send attack or support (host pays upkeep), send support home, recall, return trips
CombatResolverandLootCalculator(wall, morale, luck, night bonus, hiding place, rams, catapults), with levied militia defending, with unit tests- Beginner protection
- Reports: list, detail, unread count, delete
- Incoming-attack push and UI: rally point screen, troop movements, support, incoming box and badge, send from the map
M4.5: Tribal Wars essentials
What Die Stämme has at this stage that the game still lacks.
- Quest book: construction, army and village lines with goals and rewards; a reward for every building level reached the first time
- Scouts: a scout unit, scouts meet scouts first, scouting reports (troops, resources, buildings)
- Battle simulator at the rally point (
CombatResolverover WS, nothing changes) - Troop templates at the rally point, "repeat attack" from a report
- Rename villages
- Player and village profile pages (from the map, reports and movements)
- Ranking: players by points, villages by points, opponents defeated (attack and defence)
- Chat between players: the world, the tribe, and direct conversations, live
- Messages between players as letters (inbox, threads), if the chat isn't enough
- Account settings: password, delete the account
- Notebook, vacation mode, password reset by email (needs mail on the server)
M4.6: Game loop
The world pushes back, so a world with few players is a game too: something threatens the village, raiding costs a decision, building space forces a choice of what a village is for, and a world has an end.
- Barbarian garrisons: troops from the village's points in one of four profiles (spearmen, swordsmen, archers, riders), capped by its food, regrowing after a hit; their stock grows from their own buildings
- Raiders: the nearest barbarian camp sends a band at every player village about once a day, announced hours ahead and sized by the village's points, with rams against a wall; hitting the camp first shrinks or scatters the band; loot goes back to the camp, a beaten band pays a bounty
- Scarce building space (5 per headquarters level instead of 20) and specialisation: a resource village produces more, a military village trains faster and defends better
- Seasons: crown villages appear around 0|0 after some weeks; a player who holds most of them long enough wins the world, and the next world opens
- Lazarett: half of the own defenders who fall come back wounded into the hospital's beds and stand again after four hours
- Pacing like Die Stämme: build times from its formula and per-level table (10 s floor, 1.05 per HQ level), beginner protection in real days (5), World 1 at speed 4 with armies at unit speed 0.5
M5: Trade and encounters
- Market and merchants, partly: the market with merchants per level, sending resources, offers between players and repeating trade routes. Still open: escorts and travel modes for caravans, encounters, food deliveries (
food_deliveries) and the 24h import average EncounterFinder(closest approach of two linear paths) with unit tests- Encounter events: field battles, caravan looting, skipping destroyed groups
- Barbarian ambushes with seeded RNG
- UI: trade form, caravan tracking, encounter reports
M6: Conquering, tribes, multiple villages
- Loyalty (lazy regeneration), noble drop per hit, conquest transfers the village
- Coins at the academy, rising noble cost per world config
- Tribes with members, roles and invites; alliances and NAPs accepted by both and ended with notice, enmity declared alone; no attacks within a tribe or across a pact
- Tribe relations applied at encounter time (with M5)
- Village switcher in the header
- Overviews across villages (production, troops, buildings per village)
- Map colours by relation (own, tribe, ally, NAP, enemy, others, barbarians) and every known movement drawn on the map with its size
- Restart on the same world after losing every village
- Inactive villages turn barbarian (14 real days); deleted accounts' villages too
Later: the rest of Die Stämme
- Quests and a tutorial for new players
- Smithy-style unit research, church, paladin with items (world options)
- Scavenging (Raubzug) with idle troops
- Bonus villages, awards and statistics
- Tribe forum, mass messages, tribe ranking (with M6 tribes)
M7: City view and Steam
- Richer diorama: more detail per building type and level tier, animations (the basic diorama shipped with M1)
- Steam build check: static output wrapped in Electron or Tauri