Website review
This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.
What is Lostgarden?
Lostgarden is a long-running personal blog by game designer Daniel Cook, collecting essays on game design theory, game art, and the business of design. It is a reading site rather than a news site or portfolio: the homepage is organized around Recent Posts, Popular Posts, and All Posts.
H3 What you'll find there
- Design theory essays, often built from hands-on production problems rather than abstract rules — for example, the Value chains post on balancing faucet-and-drain economies grew out of work on Cozy Grove.
- Posts on emerging roles and disciplines, such as "What is a Social Systems Designer?" and "What is a Daniel Cook Game?"
- Talks and papers, including the Kind Games GDC 2024 talk and the prosocial multiplayer paper.
- Practical art resources for developers, notably the long-standing List of Game Artists and "How to bootstrap your indie art needs."
H3 Who it suits
- Working designers who want methods they can apply to a live project.
- Indie developers looking for art sourcing and bootstrapping advice.
- Students and researchers who want a citable body of writing on design theory.
It is less useful if you want daily industry news, reviews of new releases, or a tutorial series with step-by-step technical instruction. The archive is deep, so older posts reflect the design context of their time.
A practical next step: open Popular Posts first, since the most-linked essays (game art lists, value chains) are the ones other developers return to, then use All Posts to browse chronologically when you want to follow how a topic developed.
How can indie developers use the free game art and graphics on Lostgarden?
Indie developers typically use Lostgarden as a source of free 2D game art: the site hosts a well-known collection of downloadable sprite sheets and graphics, alongside essays on how to put them to work. The practical move is to treat it as a starting library rather than a finished art direction.
How to use the art in a project
- Prototype first. Drop the sprites into a test scene to check scale, animation frames and readability before committing to a style.
- Reskin later. Because the graphics are generic, they work well as placeholder art you replace once the game's look is settled.
- Check the license terms on the page hosting each asset. Lostgarden's art is offered for reuse, but the exact conditions are stated with the downloads, and those govern commercial use, attribution and redistribution.
- Mix sources carefully. If you combine Lostgarden assets with other free packs, keep a note of each source so you can answer questions later.
The trade-off
Free art saves weeks of drawing and lets a solo developer ship something that looks coherent. The cost is distinctiveness: assets that many developers can download will appear in other games, so your differentiator has to be mechanics, tone or level design. The site's own essay on bootstrapping indie art needs is aimed at exactly this problem, and it is worth reading before you build a pipeline around borrowed sprites.
A concrete scenario
A two-person team building a top-down life sim could use the sprite sheets for characters, props and terrain in a vertical slice, then commission or draw replacements for the handful of assets that appear on screen constantly. That keeps the demo cheap while protecting the final look.
Next step
Pick one asset pack, import it into your engine, and build a single playable scene with it. If the scene reads clearly at your target resolution, you have a usable base; if not, you have learned that before spending money on custom art.
For more on the thinking behind the assets and on the business side of indie design, browse Lostgarden. If you later want a broader pool of free assets, OpenGameArt and Kenney are established options, each with its own license terms to check.
What is social systems design and how does it fit into game development?
Social systems design is the discipline of treating players' relationships, norms, incentives and group behavior as a designed system rather than a side effect of game mechanics. Instead of asking only "is this mechanic fun?", a social systems designer asks how a mechanic shapes how players treat each other, form groups, trust, compete, exclude or cooperate — and then tunes the rules, feedback and rewards to produce the intended social outcomes.
Lostgarden frames it as an emerging game design specialization in "What is a Social Systems Designer?" (March 2025), and its "Kind Games" material extends the idea into prosocial multiplayer design. Treat those as the site's framing of the discipline, not as a formal industry standard.
What the role covers
- Incentive design: How rewards, scarcity and progression push players toward cooperation, competition, hoarding or helping.
- Norms and moderation: What behavior the community treats as normal, and what systems (reputation, reporting, matchmaking, visibility) reinforce it.
- Group dynamics: Guilds, teams, friend networks, matchmaking pools and how their size and turnover affect play.
- Onboarding into a society: How new players learn the unwritten rules, not just the controls.
- Measurement: Tracking retention, toxicity reports, cooperation rates or group formation as design outcomes.
How it fits into development
It sits alongside, not instead of, traditional disciplines. Systems designers own economies and mechanics; social systems designers own the human consequences of those mechanics and often work with community, live-ops, UX research and moderation teams. The practical difference is timing: social outcomes are hard to patch later, so this work is most valuable in pre-production and during live tuning, when you can still change matchmaking, reward structures or visibility rules.
| Question | Mechanics-focused design | Social systems design |
|---|---|---|
| Primary unit | Player and systems | Players in relation to each other |
| Typical lever | Damage, cost, progression | Incentives, norms, matchmaking, visibility |
| Success signal | Engagement, mastery | Cooperation, healthy groups, low toxicity |
| When it matters most | Throughout production | Early design plus live operations |
A concrete scenario
Suppose your co-op game rewards individual loot drops. A mechanics designer sees a working economy; a social systems designer notices that the fastest path is to let teammates fail while you collect. The fix might be shared rewards, contribution-based credit or social visibility — changes that alter player behavior without touching combat balance.
Next step: pick one multiplayer or community feature you already have and write down the behavior it currently rewards, the behavior you want, and the smallest rule change that closes the gap. If you want the source author's own definition and further reading, start with Lostgarden's "What is a Social Systems Designer?" and its "Kind Games" paper, then compare with how live-service studios describe trust and safety roles.
What are value chains and how can they help balance game economies?
Value chains are a design method for balancing a game economy by tracing how resources flow from their sources (faucets) to their sinks (drains), rather than tuning individual numbers in isolation. The concept is explained on Lostgarden in a post on creating and balancing faucet-and-drain economies, which frames the problem through a concrete example: picking up a stick in a life-sim game is not inherently fun, so the design question becomes what that stick is for.
How a value chain works
A value chain maps the sequence of transformations a resource passes through:
- Faucet: where a resource enters the economy (harvesting a stick, earning coins from a quest).
- Conversion steps: each craft, trade or upgrade that turns one resource into another.
- Drain: where value leaves the economy (consumption, crafting costs, upgrades, decay).
By writing the chain out, you can see whether the player's effort at each step is rewarded proportionally, and where the economy stalls or floods.
Why it helps balance
Balancing by feel tends to produce economies where one resource is trivially abundant and another is a bottleneck nobody intended. A value chain exposes those mismatches early:
- If a mid-chain conversion costs more than the resulting item is worth downstream, players skip it — the chain is broken.
- If a faucet produces faster than any drain consumes, inflation follows.
- If a drain is too aggressive, players feel punished for engaging with the system at all.
The method also gives you a shared vocabulary for discussing economy changes with a team, since each proposed tweak can be located at a specific link in the chain.
Practical next step
Take one resource in your game and write its full chain from source to sink on a single page, annotating the time and effort cost at each step. Then ask, for each link: is the reward here worth the cost of the previous link? If not, that link — not the global drop rate — is usually what needs adjusting.
Who this suits
The approach is most useful for designers working on life sims, crafting games and any title with interlocking resource loops, where small imbalances compound over long play sessions. It is less relevant for games with no persistent economy.
What are kind games and how can designers create prosocial multiplayer experiences?
Kind games are multiplayer games deliberately designed to encourage prosocial behavior—cooperation, generosity, and positive social interaction—rather than merely assuming that players will behave well or treating toxicity as unavoidable. Lostgarden frames this as a design problem: prosocial outcomes come from systems, incentives, and social structures, not from hoping players are nice.
Lostgarden covers this directly in its Kind Games work, including a 2024 GDC talk and a paper on designing for prosocial multiplayer. The site is the long-running design blog of Daniel Cook, a game designer known for essays on game design theory, art, and the business of design.
What makes a game "kind"
A kind game is not necessarily a relaxing or non-competitive game. It is one where the design makes prosocial behavior the natural, rewarding path. Common traits:
- Low-stakes or recoverable failure, so mistakes don't trigger blame and punishment.
- Interdependence, where players achieve more together than alone.
- Visible contribution, so helping is noticed and appreciated.
- Shared goals rather than purely zero-sum competition.
- Social affordances like gifting, reviving, trading, or building together.
How designers can create prosocial multiplayer
Start from the behavior you want and work backward to systems.
- Design the incentive structure first. If cooperation pays better than griefing, most players will cooperate. If the reverse is true, no amount of community moderation will fully fix it.
- Make helping easy and legible. Players need clear, low-friction ways to assist, and feedback that their help mattered.
- Reduce social risk. Anonymous, high-pressure, or highly punishing environments tend to produce defensive and hostile behavior.
- Model the social roles. A "social systems designer" role—explicitly named in a 2025 Lostgarden post—treats community dynamics as a design discipline rather than an afterthought.
- Test with real groups. Prosocial design is about emergent social behavior, so it has to be observed in play, not just theorized.
A practical example
If you're building a cozy crafting game, letting players leave spare resources in a shared space, see who used them, and receive a small thank-you reward creates a loop where generosity is both easy and visible—without requiring competitive pressure.
A useful next step is to read the Kind Games paper and GDC talk on Lostgarden, then map your own game's incentives: for each core loop, ask whether it rewards cooperation or punishes it.
What defines a Daniel Cook game and what design principles does it follow?
A "Daniel Cook game" is less a genre than a recognizable design signature: systems-first thinking, prosocial or cooperative framing, and an emphasis on legible feedback loops over cinematic spectacle. Cook himself treated the question as open, asking it in his own essay "What is a Daniel Cook Game?" on Lostgarden after a teammate posed it to him. The site's broader body of essays on game design theory, art and the business of design is where the principles are worked out in detail.
The recurring design principles
- Systems before content. Cook's writing on faucet-and-drain economies and value chains treats a game as a set of interlocking resource flows. The design question is not "what is the next level?" but "what does the player put in, what do they take out, and how does that balance?"
- Prosociability as a design goal. His Kind Games work, presented at GDC 2024 and developed through the Polaris Game Design Retreat, argues for multiplayer design that encourages cooperative, generous behaviour rather than pure competition.
- Legibility and player comprehension. Systems only work if players can read them. This is why his essays spend so much time on feedback, pacing and the moment-to-moment feel of an action.
- Small, honest pleasures. His example of picking up a stick in a life-sim game is telling: the core activity must be satisfying on its own, not merely a step toward a reward.
- Design as a discipline with a business side. The site explicitly covers the business of design, reflecting the view that an indie designer must reason about scope, art budgets and sustainability, not just mechanics.
Where the principles show up in practice
The clearest illustration is the stick example from his work on a life-sim harvesting and crafting system. A weaker designer would hide the unfun part behind a reward schedule. Cook's approach is to treat the basic verb as the design problem, then build the economy of faucets and drains around verbs that already feel good. That is the practical difference: the signature is not a theme or an art style, it is a habit of asking whether the loop itself is worth repeating.
How to use this
If you are evaluating your own project against this standard, pick your most frequent player action and ask three questions: Is it enjoyable before any reward? Can the player understand what it changed? Does it push players toward cooperation or toward extraction? A "no" on the first question is the one to fix first, because no economy tuning will rescue a verb nobody wants to repeat.
For the full argument, start with the essay itself and the value-chains piece on Lostgarden, then read the Kind Games material if your game has a multiplayer component.
User reviews (0)