Defining the Core Player Fantasy

Good to see you again. Last lesson treated battle royale games as design decisions rather than as feature lists: PUBG emphasizes tense survival, Fortnite emphasizes flexible counterplay and spectacle, and Apex Legends emphasizes squad mobility and coordination. You also identified that an opportunity for your game should serve a particular player need, not merely look different.

This lesson turns that insight into a central design statement: your game’s player fantasy. By the end, you will have a concise definition of the role, emotional experience, and recurring match story your battle royale should reliably deliver. It will be specific enough to guide future choices about movement, weapons, the map, visual direction, and animation.

---

A player fantasy is not a setting or a feature

A player fantasy is the sustained feeling of inhabiting a meaningful role in a game. It combines:

• Who the player is meant to feel like
• What they repeatedly get to do
• Why those actions feel emotionally satisfying
• What pressure makes that role meaningful

It is the game’s emotional promise, not its plot synopsis.

Consider these statements:

Statement	What it is	Why it is insufficient as a player fantasy
“A futuristic battle royale on a flooded Earth.”	Setting	It tells us where the game happens, but not who the player feels like.
“A battle royale with grappling hooks.”	Feature	It names a mechanic, but not the experience that mechanic should create.
“Be the last squad standing.”	Victory condition	It states how a match ends, but not what makes the journey distinctive.
“Lead a scavenger crew through a violent storm, turning limited tools and sharp coordination into improbable escapes.”	Player fantasy	It establishes a role, actions, feelings, and a source of tension.

The distinction matters because a feature can serve very different fantasies. A grappling hook might make players feel like agile urban hunters, reckless stunt performers, desperate survivors crossing dangerous terrain, or futuristic rescue specialists. The same button input does not create the same experience in every context.

The player profile you made earlier tells you who you are designing for and why they play. Player fantasy tells you what it should feel like when the game succeeds for them.

For example, “Strategy” and “Community” are motivations. They do not yet tell a designer whether players should feel like military commanders, clever smugglers, explorers, arena champions, or a trusted rescue team. Your fantasy supplies that missing identity.

---

Begin with the feeling, then reason back to the systems

Game designers often begin with a mechanic because it is easy to describe: “players build,” “players slide,” or “players choose heroes.” But mechanics are the means, not the final purpose.

The MDA framework offers a useful way to reason from game rules to player experience:

1. Mechanics are the rules and systems you design: loot scarcity, weapon recoil, a revive system, traversal tools, and zone damage.
2. Dynamics are the behaviors those rules encourage: scouting, rushing, sharing ammunition, flanking, hiding, or coordinating a retreat.
3. Aesthetics are the player’s emotional responses: resourceful, tense, dominant, inventive, connected, or vulnerable.

Watch this short segment from How To Think Like A Game Designer by Game Maker’s Toolkit. It explains MDA and, crucially, treats “aesthetics” as the player’s emotional response rather than the game’s visual style.

For a battle royale, imagine that your desired fantasy is:

Be a resourceful squad leader who turns dangerous rotations and imperfect information into decisive team victories.

That fantasy should cause design consequences.

Layer	Possible supporting choice	Behavior encouraged	Feeling reinforced
Information	Clear pings, readable landmarks, and map markings	Players make and communicate plans quickly.	Capable, coordinated
Combat	Enough survivability to reposition after an error	Squads assess, adapt, and recover rather than instantly collapse.	Tactical, resilient
Loot	Useful tools with meaningful trade-offs	Players improvise rather than wait for one “correct” loadout.	Resourceful
Map	Several viable routes, cover options, and risks	Teams weigh safety, speed, visibility, and likely enemies.	Clever under pressure
Animation and feedback	Clear movement starts, reloads, revives, and enemy reactions	Players understand what is happening during fast decisions.	In control rather than confused

Notice that the fantasy does not require every match to feel comfortable or successful. A resourceful squad leader needs uncertainty, setbacks, and difficult calls. The consistency lies in offering players meaningful opportunities to respond to pressure through observation, judgment, and teamwork.

By contrast, randomly removing information, making deaths unreadable, or making one loadout overwhelmingly superior would undermine this fantasy. Those choices may create difficulty, but they do not reliably create the feeling of resourceful leadership.

---

Make the fantasy precise enough to exclude ideas

“An exciting battle royale” is too broad to guide design. Most battle royales seek excitement. “A tactical battle royale” is a little better, but still leaves unanswered questions: tactical in what way, for whom, under what pressure, and with what emotional reward?

Understanding the Fantasy by Extra Credits makes the case for getting specific: a theme becomes useful only when you identify the particular experience within it that players want to inhabit.

Personal fantasy, world fantasy, and team fantasy

Most games blend several kinds of fantasy, but one should lead.

Primary lens	Core question	Battle royale example
Personal fantasy	“Who do I get to be?”	“I am an elusive rooftop hunter who always finds a way out.”
World fantasy	“What kind of place do I get to inhabit?”	“I survive in a beautiful but unstable world that is constantly being reclaimed by nature.”
Team fantasy	“What kind of group experience do we create?”	“My friends and I are a skilled salvage crew whose plans hold together under pressure.”

A battle royale can contain all three. A compelling flooded-world setting may support the fantasy of being an improvising scavenger; a squad communication system may turn that into a shared team fantasy. But avoid trying to promise three unrelated experiences with equal force. “A lonely horror survival game, a relaxed social hangout, and a high-speed esports arena” creates immediate conflict unless you find a coherent way to connect them.

A useful rule is:

Choose one primary role and emotional promise; let setting, team structure, and mechanics reinforce it.

---

The five components of a strong fantasy statement

A usable player-fantasy statement usually contains five components.

1. Role
   Who does the player become? Avoid generic labels such as “a player” or “a survivor” unless you make them more distinctive.

2. Signature verbs
   What actions define that role? Examples include outmaneuver, scavenge, infiltrate, rally, track, defend, rescue, outwit, and escape.

3. Emotional payoff
   Select a small group of precise feelings. “Fun” is not useful enough; inventive, calm under pressure, dangerous, connected, and hard-earned pride are more actionable.

4. Pressure or opposition
   What makes the fantasy earned? In a battle royale, this may be rival squads, scarcity, exposure, a collapsing environment, incomplete information, or time pressure.

5. Distinctive context
   What makes this role belong in your game rather than any battle royale? This is where the game’s setting, signature mechanic, or social structure can contribute.

You can write the first draft with this structure:

Be a/an [specific role] who [signature verbs] through/in [distinctive context], making the player feel [two to four emotions], while facing [meaningful pressure].

Here are three examples at different levels of quality:

Draft	Diagnosis
“Be the best fighter in a battle royale.”	Too generic. It identifies competition, but not a distinctive role or emotional experience.
“Be a cyberpunk fighter with cool guns and abilities.”	Mostly theme and feature language. It does not state what the player should feel or repeatedly do.
“Be a black-market courier racing across a quarantined vertical city, using local knowledge, daring movement, and temporary alliances to deliver vital cargo before rivals close in.”	Specific role, distinctive context, verbs, pressure, and an implied emotional mix of speed, cunning, and daring.

The last example does not yet specify the exact game systems. That is intentional. At this stage, fantasy should give direction without prematurely locking you into a particular weapon, character class, or movement ability.

---

Use fantasy as a filter, not decoration

A fantasy statement earns its place in the design document only if it helps you make decisions. The reading below distinguishes core gameplay activity from player fantasy, and explains why meaningful choices must feel thematic rather than merely numerous.

When considering a proposed feature, run a simple consistency check:

Question	What a useful answer looks like
Does it let the player enact the fantasy?	“A directional ping lets a squad leader turn an observation into an immediate shared plan.”
Does it create a behavior that supports the desired feeling?	“Limited but reliable escape tools encourage deliberate retreats rather than helpless panic.”
Does its presentation support the tone?	“Quick, readable animation makes a skilled escape feel intentional; a long, unclear animation would make the player feel delayed and confused.”
What does it weaken or contradict?	“A random instant-kill trap may create surprise, but it clashes with a fantasy of informed tactical adaptation.”

This does not mean every feature must be solemnly explained in the fantasy statement. Cosmetic rewards, menu shortcuts, and light moments can exist. It means that the systems controlling the player’s most frequent and consequential decisions should point in the same direction.

A strong fantasy is therefore also a boundary. If a proposed feature provides spectacle but makes players feel powerless when your promise is tactical control, it probably needs redesigning or removal.

---

Draft your game’s player fantasy

Set aside roughly 10–15 minutes to turn your earlier target-player profile and genre observations into a first version. Do not try to write a slogan for a store page. Write a decision-making tool for yourself.

1. Select your emotional priorities

Choose three to four feeling words that fit the motivations of your intended players. They should work together rather than compete.

Some coherent combinations include:

• Resourceful, tense, clever, relieved
• Bold, mobile, inventive, spectacular
• Connected, trusted, alert, triumphant
• Elusive, observant, dangerous, self-reliant

Avoid a list that includes every good feeling. If “calm” and “chaotic” both matter, decide whether one is the desired state and the other is the pressure players overcome.

2. Name the player’s role

Complete this phrase in a specific way:

“In a typical match, I want the player to feel like a…”

Possible role directions include a scout, salvage captain, frontier ranger, storm chaser, urban courier, rebel operative, arena celebrity, treasure hunter, or expedition leader. The right answer is the one that fits your intended audience and the opportunity you identified in other games.

3. Identify three proof moments

A fantasy must appear during play, not only in the opening cinematic. Write three short moments that would make a player think, “Yes, this is exactly the kind of person I came here to be.”

For the resourceful squad leader example, the proof moments might be:

• Spotting another team’s route and choosing a safer path before the zone forces movement.
• Turning a weak loot situation into a win by dividing roles and using terrain well.
• Escaping a collapsing fight, regrouping, and returning from a stronger position.

These are not feature specifications yet. They are observable experiences that later mechanics must make possible.

4. Write the statement and boundaries

Your design output for this lesson should contain:

• One player-fantasy statement of roughly 35–60 words
• Three to four feeling words
• Three proof moments
• Two boundaries beginning with “This game should not make players primarily feel…”

A complete example:

Player fantasy: Be a resourceful storm-runner leading a small crew through a shifting flooded frontier, reading the terrain, salvaging what others overlook, and making daring escapes under pressure. Each match should make players feel alert, capable, connected, and proud of plans that succeed despite limited time and equipment.

Proof moments:

• Finding a submerged route that avoids an enemy-held bridge.
• Combining imperfect equipment with a teammate’s tool to escape a stronger squad.
• Choosing when to risk a valuable salvage site before the storm closes it off.

Boundaries:

• This game should not make players primarily feel helpless because a threat was impossible to read.
• This game should not make players primarily feel that victory depends on mastering a long chain of complex inputs.

The boundary statements are valuable because they expose contradictions early. They do not mean the game cannot contain surprise, failure, or mastery. They establish what should not dominate the experience.

---

Deliver consistency across the whole match

A player fantasy is not delivered once. It should recur across the match’s changing phases.

Match moment	Question to ask
Deployment	Does choosing where to land express the promised role?
Early looting	Does the player make choices that support the fantasy, even with limited gear?
Rotation	Does movement create the intended tension and opportunity for expression?
Combat	Can players demonstrate the fantasy through combat decisions, not merely raw aim?
Endgame	Does the final pressure intensify the fantasy rather than replace it with a different game?
Elimination	Even in defeat, does the player understand what happened and see how a better expression of the role might have helped?

For instance, a game about daring storm-runners should not have a thrilling opening, then spend most of the match in featureless flat terrain with no route decisions, and finally end in a generic static firefight. The fantasy needs reinforcement through level layout, loot, encounter design, audiovisual feedback, and the rules of the shrinking zone.

You will make those systems concrete later. For now, retain the central test:

If a player describes an exciting match to a friend, does their story sound like the role and feeling our game promised?

---

Key takeaways

A player fantasy is the game’s consistent emotional and role-based promise. It is not simply the setting, the genre, a slogan, or a list of mechanics.

• Start with the role, signature actions, emotional payoff, pressure, and distinctive context.
• Use target-player motivations as input, but translate them into a precise experience: “strategy” can become the fantasy of a resourceful leader, planner, infiltrator, or explorer.
• Work from mechanics to likely behavior to emotional response. Rules, visual direction, sound, story, and animation should reinforce the same experience.
• Give your fantasy boundaries. They make it possible to reject features that would pull the game in a conflicting direction.
• Capture your first version as a statement, a small group of feeling words, proof moments, and boundaries.

Next, you will turn this fantasy into three to four design pillars: short, practical principles that help every later system decision stay aligned with the experience you want to deliver.