Survivor Reflections: Same Game, Different Skills

There is something very satisfying about watching confidence collide with specialisation.

Fortnite recently provided a particularly good example.

A group of players known primarily for competitive Build Fortnite went up against players who specialise in Zero Build.

Beforehand, there had been plenty of confidence from the Build side.

Clix, one of the most recognisable competitive Build players involved in the wider discussion, had been openly dismissive of how the Zero Build specialists would fare.

A widely shared clip from the argument also attributes to him the much stronger prediction that the Zero Build players would not even qualify for the finals.

I have not been able to find a clean original VOD containing that exact line, so I am not going to pretend I have.

What is considerably easier to establish is the general argument:

Build pros were expected to be able to step into Zero Build and beat the specialists there too.

Then people actually started playing.

And that assumption did not survive particularly well.

The Zero Build specialists won the series of direct challenges, with discussion around the matchups recording a 4–0 result across the recent contests.

Naturally, the internet immediately started doing what the internet does.

Build players are washed.

Zero Build players are better.

Building apparently means you cannot aim.

Pick a side.

And I think that misses the most interesting part of what happened.

Because the result does not prove Zero Build players are universally better at Fortnite.

It proves something much simpler.

Being exceptional at one version of a game does not automatically make you exceptional at another.

Same Fortnite, Different Fortnite

On the surface, Build and Zero Build are obviously still Fortnite.

Same characters.

Same weapons.

Same movement.

Same map.

Same basic Battle Royale objective.

Drop in.

Get equipped.

Stay alive.

Be the last player or team standing.

Epic even runs separate competitive events for Battle Royale and Zero Build.

They share enormous amounts of DNA.

But remove building and something fundamental changes.

In Build mode, players can create their own cover.

They can control pieces.

Edit structures.

Protect themselves almost instantly.

Turn an open area into a defensible position.

Create angles that did not exist seconds earlier.

A highly skilled Build player is doing far more than simply aiming and shooting.

The building itself is a massive skill.

Anyone pretending otherwise has probably never watched high-level Fortnite and tried to understand what is actually happening on screen.

Some of the mechanical speed involved is ridiculous.

But Zero Build removes that entire layer.

And removing one skill does not necessarily make everything else irrelevant.

Sometimes it makes the remaining skills matter more.

You Can’t Just Put Up a Wall

This is probably the biggest difference.

In Builds, getting caught in a bad position does not automatically mean the fight is over.

A good player can react.

Wall.

Ramp.

Box.

Edit.

Reset.

Suddenly the opponent who had the advantage has to deal with a structure that did not exist moments earlier.

Zero Build does not give you that option.

If you run across an exposed area and somebody starts shooting at you, the game does not care that you can perform twelve edits before I have finished working out which button places a wall.

There is no wall.

You picked the wrong route.

Now you have a problem.

Natural cover matters more.

Movement matters differently.

Terrain matters.

Rotations matter.

Knowing when to cross open ground matters.

Knowing where the next safe position is matters.

And because you cannot manufacture protection whenever you need it, mistakes in positioning can become much harder to recover from.

That is a skill set.

Just a different one.

I Learned That on a Much Smaller Scale

I have played Fortnite myself in the past.

I was bad at Builds.

There really is not a more generous way of describing it.

Someone would start constructing a small housing estate around me and I would still be trying to remember what I wanted to build in the first place.

Zero Build was different.

I did alright.

Not professionally.

Not spectacularly.

I am not about to announce my late entry into competitive Fortnite.

But I was considerably more comfortable.

The things Zero Build asked me to think about suited me better.

Movement.

Where I was standing.

Where my cover was.

Whether crossing an area was actually a sensible idea.

My experience is obviously several galaxies away from what professional players are doing.

But the underlying point is the same.

Removing building did not simply make Fortnite easier for me.

It changed which skills the game was asking me to use.

Building Is a Skill Too

And I think this needs saying because otherwise the argument simply swings too far in the opposite direction.

Zero Build specialists beating Build pros does not prove building is some sort of crutch.

Building is an enormous part of competitive Fortnite.

Piece control.

Editing.

Defensive building.

Box fighting.

Resource management.

Creating advantageous angles.

Knowing how to take control of a fight vertically as well as horizontally.

Those skills take an absurd amount of practice.

Put Zero Build specialists into high-level Build fights against the same calibre of Build professionals and I would expect a completely different result.

And that is the point.

They are specialists too.

The Zero Build players involved in the recent argument were not pretending that they would walk into Builds and suddenly dominate.

They seemed perfectly aware of whose territory that would be.

Specialists are specialised.

That really should not be controversial.

The Recent Challenge Doesn’t Prove Everything Either

There is another important bit of context.

These recent matchups were not simply a full competitive Zero Build Battle Royale tournament where the Build pros entered and got destroyed.

They included smaller Creative team fights and wagers.

That tests plenty of relevant Zero Build skills.

Aim.

Movement.

Positioning.

Team fighting.

Using cover.

But it is not identical to surviving an entire high-level Battle Royale lobby.

Drop strategy matters there.

Rotations across an entire map matter.

Storm management matters.

Knowing when not to fight matters.

So I would be equally cautious about using these results to declare that Zero Build specialists will now automatically destroy Build professionals in every future Zero Build tournament.

That has not been proven either.

What the challenges did demonstrate was narrower.

The assumption that elite Build players could simply enter the Zero Build specialists’ environment and comfortably beat them did not hold up particularly well once they actually tried it.

That is interesting enough without turning it into something bigger.

Build Pros Have Already Proven They Can Adapt

There is another reason this should not become a victory lap against Build players.

Established Fortnite professionals from the Build scene have already demonstrated that those skills can transfer successfully into Zero Build.

In 2023, Kami and Japko won the $2 million Gamers8 Zero Build tournament.

That same year, Malibuca and Th0masHD won DreamHack Summer, another major Zero Build event.

These were not players who suddenly lost all of their Fortnite ability because somebody disabled building.

They adapted.

Which tells us something important.

Skills transfer.

Aim transfers.

Game sense transfers.

Communication transfers.

Experience under pressure transfers.

Understanding Fortnite at an elite level obviously gives somebody an enormous head start.

But having transferable skills is not the same as instantly inheriting expertise in every version of the game.

You still have to learn how that version works.

PUBG and Warzone Are Both Battle Royales

This becomes even easier to understand once you move outside Fortnite.

Take PUBG and Call of Duty: Warzone.

Both are Battle Royales.

You enter a large map.

You acquire weapons and equipment.

The playable area gets smaller.

Players are eliminated.

Last player or team standing wins.

Clearly there are transferable skills.

Someone who is genuinely elite at PUBG is probably not going to load into Warzone and suddenly forget how to aim.

They understand positioning.

Communication.

Target acquisition.

Rotations.

When to engage.

When to disengage.

How Battle Royale matches flow.

But would I expect an elite PUBG player to install Warzone for the first time and immediately start beating the best Warzone professionals?

Of course not.

Because Warzone is not PUBG.

The Details Change Everything

PUBG itself describes its Blue Zone as something that shapes when players move, where they position themselves and what risks they choose to take.

Terrain and rotation decisions can dictate what options are available several minutes later.

A bad movement across the map can destroy a match before the shooting even starts.

Warzone shares the basic Battle Royale DNA but has historically layered very different systems over it.

Gulags.

Buy Stations.

Cash.

Loadouts.

Redeployment systems.

Activision’s own 2026 Black Ops Royale announcement actually demonstrates the point nicely: it specifically describes how removing the Gulag, Buy Stations, cash and loadouts makes that mode different from traditional Warzone Battle Royale.

Change a few systems and suddenly players have to make different decisions.

Being great at Battle Royale helps with both.

Being great at one Battle Royale does not automatically make you elite at another.

Nobody finds that particularly surprising.

Yet because Build and Zero Build happen inside the same game, people sometimes act as though their skills should transfer perfectly.

They don’t.

Rocket League Might Be an Even Cleaner Example

Rocket League makes the same point without even requiring us to change games.

The car is the same.

The ball is the same.

The boost is the same.

The physics are the same.

The controls are the same.

Yet Rocket League has formal high-level competition across 1v1, 2v2 and 3v3 formats.

And those formats do not ask exactly the same thing from a player.

In 1v1, there is nobody rotating behind you.

There is nobody covering the goal because you decided that challenge definitely looked like a good idea at the time.

An overcommit can immediately turn into a goal.

Kick-offs carry enormous importance.

Boost management changes.

Defensive positioning changes.

The risk attached to every challenge changes.

Move into 3v3 and suddenly rotations, passing, spacing and teammate coverage become much larger parts of the decision-making process.

The mechanical ability transfers.

The understanding of Rocket League transfers.

But the decisions change.

Same game.

Same mechanics.

Different specialisation.

Counter-Strike and Valorant Share DNA Too

Then there are games that are clearly relatives without being the same game.

Counter-Strike 2 and Valorant are obvious examples.

Both are highly competitive tactical shooters.

Both reward precise aim.

Crosshair placement.

Map knowledge.

Communication.

Economy management.

Knowing when to take a fight.

Understanding angles.

Playing around teammates.

An elite Counter-Strike player moving into Valorant is hardly starting from zero.

They arrive with years of relevant experience.

But Valorant then adds something fundamental.

Agents.

Abilities.

Different ways of controlling areas.

Different combinations of utility.

Riot itself describes Valorant as a 5v5 tactical shooter combining sharp gunplay with Agents carrying unique tactical abilities.

Those systems create decisions that simply do not exist in exactly the same way in Counter-Strike.

And the reverse applies too.

An elite Valorant professional does not load into Counter-Strike and magically know every grenade lineup, timing, smoke interaction and piece of accumulated map knowledge because they are good at another tactical shooter.

The shared DNA gives them a substantial head start.

It does not hand them mastery.

Harder Does Not Mean Every Skill Is Harder

I think part of the Fortnite argument comes from the belief that Builds has a higher mechanical skill ceiling.

There is a perfectly reasonable argument for that.

Building adds an enormous mechanical system that Zero Build does not have.

If two modes share shooting, movement and weapons while one adds building on top, it is easy to look at that and conclude:

Builds is harder.

Maybe as a complete mechanical package, it is.

But that does not mean every individual skill required to succeed is automatically harder in Builds.

Zero Build removes the ability to create cover.

That changes positioning.

It changes how exposed movement is punished.

It changes the importance of terrain.

It changes which fights are sensible.

It changes how mistakes can be recovered from.

You can remove one mechanic and increase the importance of another.

A simpler ruleset does not automatically mean mastery is simple.

Being Good at the Game Isn’t One Thing

I think this is what I like most about the whole situation.

People talk about being “good at Fortnite” as though that describes one ability.

It doesn’t.

Someone can have incredible aim and mediocre positioning.

Someone can understand rotations brilliantly but struggle in close-range fights.

Someone can be mechanically absurd in Builds and still make poor decisions when building is taken away.

Someone else can understand Zero Build terrain perfectly and have absolutely no idea what to do when another player boxes them in and starts editing walls at a speed normally associated with industrial machinery.

Games contain overlapping skills.

Not identical ones.

The same applies to PUBG and Warzone.

Rocket League 1v1 and 3v3.

Counter-Strike and Valorant.

And plenty of other games that look similar enough that we assume expertise should transfer automatically.

It rarely does.

Respect the Specialist

That is really where I land on the recent Fortnite result.

There is nothing embarrassing about an elite Build player not immediately being the best Zero Build player.

Why should they be?

They have spent thousands of hours refining a particular competitive skill set.

Likewise, there is nothing surprising about somebody who has dedicated huge amounts of time to Zero Build understanding its fights better than somebody who normally plays another mode.

That is what specialisation is.

The mistake was assuming expertise in one automatically granted expertise in the other.

And the Zero Build players seemed to understand the reverse.

Put them into Builds against elite Build professionals and they were not pretending everything would be fine.

They knew whose territory they would be entering.

That is not weakness.

That is recognising expertise.

Same Game, Different Skills

The funniest part of this whole argument is that both sides can be exceptional Fortnite players at the same time.

There does not actually need to be a loser in the larger argument.

Build professionals can be mechanically incredible.

Zero Build professionals can be incredible at Zero Build.

Build players can learn Zero Build and become excellent at it.

We already know some have.

Zero Build players can learn Builds too.

Nothing about one group’s success needs to invalidate the other.

What happened recently was simply a useful demonstration of something games regularly teach us.

Being great at something related is an advantage.

It is not a substitute for experience.

Skills transfer.

Talent transfers.

Game sense transfers.

Expertise still has to be earned.

Because sometimes it can be the same map.

The same weapons.

The same characters.

Even the same game.

And still require a completely different way of surviving.

Survivor Reflection: Confidence Is Not Evidence

There is a particular kind of internet conversation that always makes me laugh.

Someone tells you that you are wrong.

Not “I think you might be wrong.”

Not “That isn’t how I remember it.”

Not even “Have you got a source for that?”

Just:

You are wrong.

Then, if you push back, the confidence somehow increases.

Where is your evidence?

They never said that.

You cannot prove they said that.

And then you post the screenshot.

Silence.

Beautiful, immediate silence.

The Dead by Daylight Incident

One of my favourite examples came from a discussion about Dead by Daylight.

There had been some controversy around a joke made during a developer discussion and, more specifically, the context surrounding it.

The useful thing about this particular example is that the original moment is still there to watch for yourself.

Behaviour Interactive also later addressed what had happened and explained that the comment had been intended as a joke.

I still have the screenshot of that statement too.

That became rather useful when I mentioned the developer explanation in a comment and somebody confidently told me I was wrong.

Not that they interpreted the statement differently.

Not that they disagreed with what the developers meant.

According to them, the developers simply had not said what I claimed they had said.

Then came the challenge.

Where was my evidence?

Apparently, I could not provide any proof that the developers had actually said it.

Which was unfortunate.

Because I had the screenshot.

So I attached it.

There were the developers, explaining the exact thing I had just been told they had never explained.

And then…

Nothing.

The conversation stopped.

I would love to claim I handled this moment with enormous maturity and felt absolutely no satisfaction whatsoever.

That would be a lie.

It was very funny.

But the interesting part was not that I had managed to “win” an internet argument.

It was how quickly absolute certainty disappeared once evidence entered the conversation.

Before the screenshot, there was apparently no room for doubt.

After the screenshot, there was apparently no room for a reply.

Asking for Evidence Is Good

There is an important distinction here.

Someone asking me to prove something does not bother me.

They should.

If I make a factual claim, especially one about something a developer, company or creator supposedly said, asking for a source is perfectly reasonable.

We should probably do that more often.

The problem starts when:

“Do you have evidence?”

quietly becomes:

“There is no evidence because I already know you are wrong.”

Those are not the same position.

The first leaves room for new information.

The second has already decided what the answer is going to be.

That is where confidence starts pretending to be evidence.

The Burden of Proof Works Both Ways

I have had another argument where somebody asked me to provide evidence for what I was saying.

Fair enough.

So I did.

I supplied the evidence supporting my position.

Then I asked them to do the same.

That was apparently where our shared enthusiasm for evidence ended.

They pretty much refused.

The conversation then went in a direction that I will politely leave out of this Reflection.

It certainly did not involve them producing a source.

That exchange stuck with me because it highlighted something important about the burden of proof.

If I make a factual claim, the burden is on me to support it.

But if you make a factual claim in response, the same applies to you.

It is not a special rule that only exists for the person you disagree with.

You cannot reasonably say:

“Prove it.”

Receive the evidence.

Make your own counterclaim.

And then decide that you somehow do not need to support yours.

If both people are making factual claims, both people have something to back up.

Evidence Is Not Absolute Certainty

There is another distinction worth making.

Providing evidence does not necessarily mean you have proved something beyond any possible doubt.

Evidence can be strong.

It can be weak.

It can be incomplete.

Two people can look at the same evidence and reasonably disagree about what conclusion it supports.

That is where an actual discussion can happen.

You compare sources.

You look at context.

You question assumptions.

You decide how much confidence the available evidence actually justifies.

But there is a big difference between:

“I don’t think your evidence proves that.”

and:

“You have no evidence.”

Especially when the evidence is currently sitting underneath your comment.

Confidence Sounds Convincing

The internet rewards certainty.

“This might be the case” does not travel particularly far.

“This is DEFINITELY what happened” does.

Someone can write a completely unsupported claim with enough confidence and suddenly everybody else has to disprove it.

You see it constantly with games.

A developer supposedly abandoned something.

A mechanic supposedly works a particular way.

A studio definitely promised something.

A game is definitely dead.

Something was definitely never said.

Sometimes those claims are correct.

Sometimes they have simply been repeated so often that nobody remembers where they originally came from.

And sometimes somebody posts a screenshot that makes the whole conversation very awkward.

I Am Not Immune to This Either

It would be very easy for me to write this as if I am the heroic keeper of screenshots who has never been confidently wrong about anything.

That would itself be a very confident claim with very little supporting evidence.

I have remembered things incorrectly.

I have misunderstood things.

I have been certain about something, checked it, and discovered that my brain had helpfully rewritten history.

That is normal.

Being wrong is not really the problem.

What matters is what you do when somebody produces better evidence.

If someone shows me that I got something wrong, then I got it wrong.

Fair enough.

Change the position and move on.

There is no leaderboard.

You do not lose Internet Points.

The Screenshot Does Not Care

That is probably why these exchanges amuse me so much.

You can argue with someone’s opinion.

You can disagree with their interpretation.

You can debate what a developer meant.

But if the argument is:

“They never said that.”

and someone produces a screenshot of them saying it…

There is not a huge amount of room left to manoeuvre.

The screenshot does not care how confident anybody was five minutes earlier.

It just sits there.

Menacingly.

Receipts Still Need Context

Of course, screenshots are not magical truth machines either.

Things can be cropped.

Statements can be taken out of context.

Developers can change their minds.

Something said years ago might no longer reflect the current game.

That is why, with the Dead by Daylight example, I would rather provide both pieces.

The original moment.

And the later explanation from the developers themselves.

Readers do not have to take my word for it.

They can look at the evidence themselves.

That is how it should be.

Certainty Is Cheap

I think this is the bit that interests me most.

Being confident costs nothing.

Checking does.

You have to search for the original post.

Find the interview.

Read the patch notes.

Look through old announcements.

Make sure you remembered it correctly.

It takes more effort than simply typing:

“No they didn’t.”

That probably explains why the second one happens so often.

But confidence is not evidence.

Volume is not evidence.

Ten people repeating the same thing is not evidence.

And somebody sounding absolutely certain does not magically make their memory more reliable than everyone else’s.

Sometimes the boring person with the screenshot wins.

Leave Yourself Somewhere to Go

There is a really easy way to avoid most of this.

Leave yourself a little room to be wrong.

“I don’t remember them saying that.”

“I thought it worked differently.”

“Have you got the source?”

Those sentences do exactly the same job without planting a flag on a hill you might have to evacuate five minutes later.

Because one day somebody might actually have the screenshot.

And when they post it, suddenly your very confident argument has become somebody else’s favourite internet story.

Trust me.

I have one.

Confidence is useful.

Evidence is better.

Blog at WordPress.com.

Up ↑