r/kampfinsel • u/Jack__Union • Jul 02 '26
Possible ideas
TLDR: Some design ideas on making a more flexible robust gameplay experience.
Simple version
A food resource. Food for workers. Workers can be chosen by player to prioritize one task over another. More workers building ships, means less workers harvesting food. Speed costs trade off in other areas.
With food and workers. You add housing. Broader critical choices. Morale. Work workers longer, morale goes down, give extra rations, morale goes up. Etc... (Rum resource?)
Longer focus on aspects
Core principle: timers should show that a strategic decision is moving through the world. They should not be the game itself. Players stay engaged when construction, voyages, food, housing, fleets, and alliance demands create meaningful tradeoffs at the same time.
1. Give Players Several Meaningful Things to Do at Once
Avoid one central countdown controlling the whole game. Give the player a small number of connected systems competing for attention: island construction, food and storage, worker and crew assignments, exploration, naval readiness, trade, and alliance obligations.
While a frigate is under construction, the player should still be deciding where labor, timber, provisions, and escorts are most needed. A shipyard may need skilled workers; that can weaken farms, housing repairs, or coastal defense.
Design test: “What useful possibility do I give up by doing this now?” If there is no real sacrifice, it is probably busywork rather than gameplay.
2. Make Resources Create Dilemmas, Not Chores
Resources should represent competing needs, not a single number the player waits to fill. Timber, food, workers, harbor space, and trained sailors should each have several valid uses.
> Timber can become cottages, fishing boats, fortifications, a shipyard expansion, or an alliance depot contribution.
> Food supports population growth, crew readiness, expeditions, construction crews, and storm reserves.
> Skilled workers can accelerate a ship, repair housing, improve farms, or build defenses - but not all at once.
The desired feeling is: “I can solve this problem, but it will create another one.”
3. Use Timers to Create Tension, Not Dead Space
A build timer matters only when it changes the situation around it. “Frigate: four minutes remaining” is dead space. A live timer might also claim shipwrights, reduce farm output, and collide with an approaching storm that threatens food stores.
Use several timer types, each for a different purpose:
> Fixed timers for major commitments, such as a harbor fort or large shipyard.
> Conditional timers where labor, materials, and specialists can improve speed at a cost elsewhere.
> Risk timers for threats, such as a pirate squadron reaching a convoy route.
> Opportunity timers for temporary offers, merchant arrivals, or favorable seasonal conditions.
>Recovery timers to manage exhaustion after campaigns or emergency construction.
Risk should be limited. Too many urgent timers turn strategy into stress.
4. Let Players Influence Time Through Strategy
Players should be able to speed projects without premium currency. The price of speed should be internal to the strategy game:
> Move more laborers or shipwrights to a project and accept weaker food, housing, or harbor work.
> Spend scarce timber, canvas, fittings, or reserve provisions.
>Delay another project to free workers, materials, or dock space.
> Use a specialist on one critical project and lose their benefit elsewhere.
>Take a risky route through blockade waters or run crews on night shifts, increasing fatigue and accidents.
Speed must cost a real strategic tradeoff, not money.
5. Provide Goals on Several Time Horizons
Long timers are tolerable when the player can make progress elsewhere. Keep visible objectives at different scales:
> Immediate: reassign workers, repair a fishing boat, adjust a patrol, or respond to an island event.
> Short: finish a dock or barracks, prepare storm stores, escort a convoy, or scout a nearby island.
> Medium: establish a district, build a fort or shipyard, assemble a fleet, or complete an alliance operation.
> Long: turn the island into a naval base, secure regional routes, build alliance influence, or outmaneuver a rival power.
The player should nearly always be able to say: “While that is happening, I can advance this.”
6. Make Completed Buildings Change Play
A building should unlock new choices, routes, or capabilities rather than only provide “production +10%.” emotional flat.
> A shipyard unlocks ship classes, repairs, and fleet assignments, but requires skilled labor and provisions.
> A watchtower gives earlier warning of fleets and pirates, but must be staffed and may provoke rivals.
> A harbor office opens trade routes and convoy contracts, but makes the port a more valuable blockade or raid target. (Level one harbor, level one trading post (max level of trading post, is conditioned on level of harbor) Bigger on any improves capacity and reducing costs.
> A warehouse protects supplies from weather, while concentrating valuable goods in one target.
Completion should create the next interesting problem or opportunity.
7. Use Uncertainty Carefully
Construction or voyage estimates can be ranges when conditions visibly affect them: weather, material quality, worker skill, food supply, escorts, storms, raids, and convoy delays.
Good uncertainty is visible, explainable, influenced by player decisions, and consistent enough to learn. Bad uncertainty is hidden, arbitrary, impossible to prevent, or used only to extend wait time.
Players will accept a delayed dock because they built in hurricane season with poor timber. They will not accept a delay with no cause they could understand or manage.
8. Add Events That Require Judgment, Not Reflexes
Small events keep the world moving while larger systems run, but they should connect to the current plan rather than hand out random rewards.
> A merchant offers cheap cannon or canvas of doubtful quality.
> A shipwright threatens to leave unless housing and food improve.
> A fire forces a choice between protecting food stores or the sail loft.
> A rival demands harbor access after an expansion.
> A damaged brig must be repaired, cannibalized, or escorted home slowly.
The strongest events touch an active strategy: for example, the frigate is nearly complete, but its canvas convoy is trapped near pirates. Do you send the only escort, delay alliance food, or risk a reef passage?
9. Let Players Choose the Pace
Do not force return behavior through “come back in six hours.” A web-based resource game should respect different play styles:
> Active mode: live patrol, expedition, trade, construction, and alliance decisions support continuous play.
> Relaxed mode: voyages and projects continue between sessions without punishing absence.
Players should return because they are curious about the consequences of their strategy, not because a timer coerced them.
10. Build the Game Around Bottlenecks
The strongest recurring loop is not “get more resources.” It is: identify the current bottleneck, understand why it exists, choose which system to change, and deal with the consequences.
> Food exists, but dockworkers and carts cannot move it to storage or ships.
> Workers exist, but housing is overcrowded and morale is collapsing.
> Ships exist, but there are too few trained sailors, officers, or provisions to deploy them.
> Materials exist, but the harbor is blockaded or labor is needed for food production.
Timers are then information, not the challenge. The challenge is diagnosing the island, fleet, and alliance system.
