Where do the cozy ingredients come from?

They come from a design think tank, not from a genre list. At Project Horseshoe 2017, a group of eight designers wrote a report on coziness. The group included Tanya X Short of Kitfox Games and Daniel Cook of Spry Fox. The report calls coziness an ingredient that works in both casual and core genres.

The report gives three parts: safety, softness and satisfied needs. It also says that coziness helps retention, because players control the pace and stay engaged while they rest. That claim is a design opinion from experienced developers. It is not a measured result, so you should test it in your own data.

This checklist uses five ingredients: safety, abundance, softness, pace and warmth. The first three follow the report. Pace and warmth are our grouping of the report's notes on pressure, rewards and social presence. The A Short Sail rating checklist asks the same kind of questions from the player's side, with a score out of 25.

Sources: Project Horseshoe 2017 report; A Short Sail blog (player view).

What are the 25 checks?

Each check is a yes or no question about your build, with one thing to measure. Run it on a vertical slice, a demo or a full game. Answer for the first hour of play, because that is where most players decide.

The 25 cozy checks, grouped by ingredient, with the event or metric to watch for each one.
IngredientCheckWhat to measure
SafetyNothing can hurt the player, or danger is far away and optionalQuits within 2 minutes of the first threat
SafetyNo progress or items can be lostQuits after a loss event
SafetyEvery activity is opt-inShare of players who skip each activity
SafetyMistakes have no lasting costUndo or retry use per session
SafetyOther players cannot enter your space unaskedReports and blocks per 100 sessions
AbundanceBasic resources are easy to getTime spent at zero of a key resource
AbundanceThe world looks generous and fullScreenshots or photo mode use
AbundanceWaiting costs nothingQuits after an idle period
AbundanceThe game shows that all is well, such as a sleeping catTime spent in safe spaces
AbundanceRewards feel like gifts, not a wageShare of rewards that are opened or used
SoftnessColors and light are warm and gentleBrightness and contrast settings changed
SoftnessSounds are soft and have a clear sourceMusic and sound volume changes
SoftnessSpaces are small enough to knowTime to first get lost, from map opens
SoftnessNo pop-up interrupts playQuits within 30 seconds of a pop-up
SoftnessThe camera moves gentlyCamera comfort settings changed
PaceThere is no timer or countdownQuits after a timer appears
PaceThe player can stop and save at any timeSession end points, by place in the game
PaceThere is no daily chore with a penaltyReturn rate after a missed day
PaceActivities are fun on their own, not only for the prizeRepeat use of each activity
PaceA small ritual has a known lengthMedian length of the ritual
WarmthThere is a character, pet or neighbor to care aboutTalks or gifts per session
WarmthGifts are free, with no debtShare of players who give a gift back
WarmthSolo play is fine, and company is optionalSolo share of sessions
WarmthThe player has a place of their own to arrangeDecoration actions per session
WarmthThe game welcomes the player as a person, not as a hero with a jobTutorial completion rate

Sources: Project Horseshoe 2017 report. The checks and the measures are our own design review, not research results.

How do I score the checklist?

Give one point for each yes, then read each ingredient on its own. A total of 20 can hide a weak ingredient. A game with 5 points in safety and 1 point in pace still feels rushed, whatever the total says.

  1. Play the first hour of your build with the checklist open, or ask three new players to play while you watch.
  2. Score each check 1 for yes and 0 for no or not sure.
  3. Add the points for each ingredient. Each ingredient has 5 points.
  4. Mark every ingredient below 3 as a design risk.
  5. For each risk, add the matching event from the table to your tracking plan before the next playtest.

Sources: our own scoring method.

Which events show that a check fails?

Events that mark the moment the mood changes, followed by a quit. A cozy game rarely fails at one big wall. It fails when small pressures pile up. So track the pressure points, and look at what players do right after them.

Name events after what the player sees, and add properties for the place and the build. Then a funnel from the pressure event to session end shows the quit rate after that moment.

  • timer_shown, with the activity name, to find quits after a countdown appears.
  • resource_empty, with the resource name, to find scarcity that the player feels.
  • popup_shown, with the popup name, to find interruptions.
  • item_lost or progress_lost, to check that loss really never happens.
  • settings_changed, with the setting and the new value, to see which sensory parts players turn down.
  • session_end, with the area and the last activity, to map where people stop.

Sources: Manalens product documentation (funnels and event properties).

How do I read the results after a playtest?

Compare the quit rate right after each pressure event with the quit rate at a calm moment. If players often quit within 2 minutes of a timer, and rarely within 2 minutes of a calm moment, the timer is the problem. The 2 minute window is our rule of thumb. Pick one window and keep it the same from test to test.

Then compare builds. If you remove a timer in build 12, the quit rate after that activity should fall in build 12. Day 1 return rate for players who started on build 12 should not get worse. If it does, the timer was doing a job, such as giving a goal, and you need a softer way to give that goal.

Sources: Manalens product documentation (funnels and retention).

How do I track the checklist in one place?

Manalens is the analytics and growth engine built for games. Send the checklist events from the Unity, Godot or web SDK. Then build a funnel from each pressure event to session end, and compare D1 and D7 retention by build.

Sources: Manalens product documentation.

Frequently asked questions

What are the main ingredients of a cozy game?

The 2017 Project Horseshoe report names safety, softness and satisfied needs. This checklist splits them into five parts: safety, abundance, softness, pace and warmth. A cozy game has no real danger, plenty of resources, soft looks and sound, no time pressure, and characters or places the player can care about.

Can a game with combat still be cozy?

Yes, in parts. The Project Horseshoe report calls coziness an ingredient that works in casual and core genres, and gives the campfire in Dark Souls as an example of a safe space in a dangerous game. Make the safe spaces clear, and keep danger optional or far away from them.

How many checks should a cozy game pass?

There is no researched pass mark. Our rule is to mark any ingredient with fewer than 3 of its 5 points as a risk. Look at each ingredient on its own, because a high total can hide one ingredient that breaks the mood, such as a single timer in a calm game.

Which single event is most useful to track?

Track session_end with the area and the last activity as properties. It shows where players stop and what they did just before. Compare it with pressure events such as timer_shown or popup_shown, and you can see if a quit follows the pressure or happens at a natural break.

Sources and implementation