Social Contagion in Experience Abstraction — How Abstraction Spreads Between Players

Understanding Social Contagion — The Most Dangerous Mechanic

Social contagion is the proximity-based mechanic that makes Experience Abstraction fundamentally different from simple survival games. When a player becomes abstracted, their presence creates an invisible zone around them that puts nearby normal players at risk of abstraction. This is not a choice — the abstracted player does not activate or control the contagion. It is a passive effect that simply exists around any abstracted character.

Social contagion is the fastest abstraction trigger and the most difficult to manage. Understanding how it works, how far it reaches, and how to respond to it is essential for every player regardless of their play style.

How Social Contagion Works in Practice

When an abstracted player is on the server, the following occurs:

1. The abstracted player emits a contagion zone — an area around them where normal players are at risk
2. Normal players within this zone have their proximity trigger activated
3. The longer a normal player stays in the zone, the higher their risk of abstracting
4. The abstracted player does not need to take any action — the effect is entirely passive
5. The contagion zone moves with the abstracted player as they walk around the map

Visual identification: Abstracted players appear as dark heavy creatures with bright multicolored eye-like markings. If you see this visual, you are potentially within the contagion zone.

What contagion is NOT:

• Contagion is not a projectile or attack — it does not "shoot" at players
• Contagion does not require the abstracted player to target anyone
• Contagion is not instant — it requires sustained proximity
• Contagion is not blocked by walls or obstacles — if the abstracted player is near you, you are at risk

The Contagion Zone — What We Know and Do Not Know

The contagion zone around an abstracted player has several properties, some confirmed and some estimated:

Key implication: Because the zone size and duration requirements are unknown, you cannot calculate a "safe distance" or "maximum exposure time." The only guaranteed safe behavior is to create as much distance as possible from abstracted players.

Contagion Cascades — When One Abstraction Leads to Many

A contagion cascade occurs when one player's abstraction leads to further abstractions through proximity, which leads to even more abstractions. This chain reaction is one of the most dramatic events in the game and can affect a significant portion of a 30-player server.

How cascades develop:

1. Player A abstracts (through isolation, darkness, or proximity to another abstracted player)
2. Player A's contagion zone puts nearby players B and C at risk
3. Player B abstracts through proximity to A
4. Now Players A and B both have contagion zones, doubling the risk area
5. Player C abstracts through combined proximity to A and B
6. The cascade accelerates as each new abstraction adds another contagion source
7. Eventually, all players near the cascade center have abstracted

Cascade stopping conditions:

• Remaining players create enough distance from all abstracted players
• The abstracted players move away from the remaining normal players
• New players join the server and are not immediately near the abstracted cluster
• The cascade "runs out" of nearby normal players to affect

How to survive a cascade:

1. Move away from the center of the cascade immediately
2. Do not stop to watch — keep moving until you are well clear
3. Head for the stage or the opposite side of the central floor
4. Stay with other surviving players to maintain group protection
5. Use chat to alert other players: "Cascade happening near [location] — move away"

Managing Proximity Risk — Practical Strategies

Strategy 1: The Perimeter Rule

Stay on the outer edge of the central floor, away from the center where abstracted players are most likely to approach. This gives you maximum reaction time when a threat appears.

Strategy 2: The Observer Protocol

When you see an abstracted player, stop and observe their movement before reacting. If they are moving away from you, you do not need to flee. If they are moving toward you, move calmly to the opposite side of the floor.

Strategy 3: The Buddy System

Pair up with one other player. Agree that if either of you sees an abstracted player, both of you move together. This prevents one of you from accidentally staying in the contagion zone while the other flees.

Strategy 4: The Scatter-and-Rally Pattern

When an abstracted player enters a group, the group scatters in different directions. This breaks the group but gets everyone out of the contagion zone. After 10-15 seconds, all scattered players rally at the stage.

Contagion and Stacking

Social contagion is even more powerful when combined with other triggers. If an abstracted player enters a dark area where normal players are present, those players face both proximity and darkness triggers simultaneously. This stacked condition significantly accelerates the abstraction process.

How to avoid stacked contagion:

• If an abstracted player enters a dark area you are in, leave immediately — you are facing two triggers at once
• If an abstracted player approaches while you are isolated, you are facing two triggers (proximity + isolation) — return to the group
• Never voluntarily enter a dark area where an abstracted player is present

The Abstracted Player's Perspective

Understanding social contagion also means understanding what happens after you abstract. If you choose to abstract (for Caine summoning, for example), you become a contagion source yourself. This means:

• Other players may flee from you — this is not personal, it is survival
• Your presence near the group is dangerous to them
• You can help by moving to low-traffic areas after abstracting, away from other normal players
• You can coordinate with a partner to stay near them for a Caine summon while other players keep their distance

Etiquette for abstracted players:

• Do not deliberately chase normal players — this is considered griefing by the community
• Stay near the stage or in a dark side route where players expect abstracted characters
• Use chat to communicate your intentions: "I am abstracted. I am staying near the stage for a Caine attempt."

Contagion and Server Architecture

The social contagion mechanic interacts with the server's 30-player architecture in specific ways:

Contagion by Server Population

Contagion and Map Topology

The map's layout creates different contagion dynamics depending on where abstracted players are positioned:

The central floor paradox: The central floor is where contagion spreads fastest (many players in range) but is also where escape is easiest (open space, multiple directions to move). The room hallway is where contagion spreads slower (fewer players in the corridor) but escape is harder (narrow passage). This creates an interesting strategic trade-off.

Contagion Chain Scenarios — How Chains Form and Break

Understanding specific contagion chain scenarios helps you predict and manage cascade events. Here are the most common patterns observed in Experience Abstraction servers:

Scenario 1: The Single-Source Cascade

One abstracted player enters the central floor from a dark side route. The group is concentrated near the stage. As the abstracted player approaches, three players closest to them abstract first. These three new abstracted players create three overlapping contagion zones, which then threaten the next ring of players. The cascade accelerates until most of the group has either abstracted or fled. Break point: If the first three players to abstract had moved away instead of staying near the original abstracted player, the cascade would have stopped at one source.

Scenario 2: The Room Hallway Containment

An abstracted player enters the room hallway. Players in the corridor have limited escape routes (only two exits). Two players abstract in the hallway. However, because the hallway is narrow and has fewer players than the central floor, the cascade is contained — it does not spread to the central floor because the abstracted players remain in the corridor. Break point: The room hallway's limited population acts as a natural firewall against cascade expansion.

Scenario 3: The Cross-Zone Cascade

An abstracted player on the central floor is moving toward the room hallway. Some players scatter into the room hallway, but the abstracted player follows them in. Now the abstracted player is in the narrow corridor with fleeing players who have no room to maneuver. The contagion cascades in the hallway and then back onto the central floor as new abstracted players exit. Break point: Fleeing to the stage (open area) instead of the room hallway (confined area) prevents this cross-zone cascade.

How to Break a Contagion Chain

If you recognize a cascade forming, take these actions immediately:

The most important action: Creating distance from abstracted players. Every meter of distance reduces the contagion risk. The cascade only stops when normal players are far enough from all abstracted players that the proximity trigger becomes inactive.

Frequently Asked Questions

Can I cure myself of abstraction?

No cure system has been confirmed. Once abstracted, you remain in that state for the session. Rejoining the server returns you to normal form.

Does contagion affect abstracted players?

No. Abstracted players are already transformed. The contagion zone only affects normal players.

Can I see the contagion zone?

No visual indicator for the contagion zone has been confirmed. You cannot see how far the effect reaches — you must assume any proximity to an abstracted player carries risk.

How many abstracted players does it take to create a cascade?

Even one abstracted player near a cluster of normal players can start a cascade. The more normal players near the abstracted player, the more likely a cascade becomes.