Files

T

Antigravity Agent 9a135bd19d docs(10_Wiki): Topic_Business/General/Graphic/Programming을 Topics/ 하위로 이동

최상위 10_Wiki/Topic_*였던 4개 카테고리 폴더를 10_Wiki/Topics/Topic_* 로 재배치.
콘텐츠 변경 없음(순수 폴더 이동) — Topics/ 하위 나머지 폴더는 이미 지난 커밋에서
전부 정리된 상태(잔존 항목은 에이전트 운영 상태 및 사용자가 보존을 요청한
업데이트0615/무제 3.canvas 뿐).

2026-07-05 00:44:01 +09:00

6.2 KiB

Raw Blame History

id, title, category, status, canonical_id, aliases, duplicate_of, source_trust_level, confidence_score, verification_status, tags, raw_sources, last_reinforced, github_commit, tech_stack

title

Revenge Cycle Dynamics

매 한 줄

"매 attack 은 매 future attack 의 seed 다.". Revenge cycle 은 War Commander, Mobile Strike, EVE 등 PvP 전략 게임의 retention engine — player A 가 player B 를 칠 때, B 의 retaliation probability 가 높아지고, 그 retaliation 이 다시 A 의 counter-retaliation 을 trigger 하는 closed feedback loop 이다. 매 2026 LiveOps 에서 이 cycle 을 의도적으로 telemetry-balance 하는 것은 D30 retention 의 핵심 lever.

매 핵심

매 Cycle Anatomy

Trigger: unprovoked attack, base raid, alliance-level aggression
Emotional payload: loss aversion + identity threat (base = avatar extension)
Retaliation window: 24-72h (mobile), 7d (slow strategy)
Escalation vector: solo → alliance war → cross-server war
Decay: 매 cycle 은 자연스럽게 fade — fuel injection (events, leaderboards) 없으면.

매 Retention 메커니즘

매 active grudge = 매 daily login reason
매 revenge planning = 매 in-app currency sink (troop healing, base upgrades)
매 alliance bond = social switching cost
매 storytelling = personal narrative (UGC potential)

매 응용

War Commander: kill report + replay → revenge UI button.
EVE Online: kill mail system → corp-level vendetta.
Mobile Strike: VIP bounty board → paid revenge service.
Clash of Clans: revenge cooldown design (one-shot).

💻 패턴

Pattern 1 — Revenge eligibility tracker

interface AttackEvent {
  attackerId: string;
  defenderId: string;
  timestamp: number;
  damageDealt: number;
  retaliated: boolean;
}

class RevengeTracker {
  private events = new Map<string, AttackEvent[]>();
  private readonly WINDOW_MS = 72 * 3600 * 1000;

  record(e: AttackEvent) {
    const list = this.events.get(e.defenderId) ?? [];
    list.push(e);
    this.events.set(e.defenderId, list);
  }

  pendingRevenge(playerId: string): AttackEvent[] {
    const now = Date.now();
    return (this.events.get(playerId) ?? [])
      .filter(e => !e.retaliated && now - e.timestamp < this.WINDOW_MS);
  }
}

Pattern 2 — Escalation scoring

function escalationScore(history: AttackEvent[]): number {
  // 매 reciprocal exchange = +1, asymmetric = +2 (more inflammatory)
  let score = 0;
  for (let i = 1; i < history.length; i++) {
    const prev = history[i - 1];
    const cur = history[i];
    const reciprocal = prev.attackerId === cur.defenderId;
    score += reciprocal ? 1 : 2;
  }
  return score;
}

Pattern 3 — Cooldown gate (anti-grief)

function canAttack(attackerId: string, defenderId: string, history: AttackEvent[]): boolean {
  const recentSameTarget = history.filter(
    e => e.attackerId === attackerId
      && e.defenderId === defenderId
      && Date.now() - e.timestamp < 3600 * 1000,
  ).length;
  return recentSameTarget < 3; // 매 1h 내 3회 제한
}

Pattern 4 — Revenge notification injection

async function dispatchRevengePush(victim: Player, event: AttackEvent) {
  await pushService.send(victim.deviceToken, {
    title: `${event.attackerName} attacked your base!`,
    body: `Tap to retaliate. Window closes in ${remainingHours(event)}h.`,
    deepLink: `app://revenge/${event.id}`,
  });
}

Pattern 5 — Asymmetric matchmaking shield

function shieldEligibility(attacker: Player, defender: Player): boolean {
  const powerRatio = attacker.power / defender.power;
  // 매 5x power gap → 매 attack blocked (anti-snowball)
  return powerRatio < 5.0;
}

Pattern 6 — Alliance vendetta propagation

function propagateVendetta(allianceA: string, allianceB: string, severity: number) {
  if (severity > THRESHOLD_WAR) {
    declareWar(allianceA, allianceB, durationDays: 7);
    grantWarBuffs([allianceA, allianceB]);
  }
}

Pattern 7 — Revenge replay capture

function captureReplay(combatLog: CombatTick[]): ReplayBlob {
  return compress({
    seed: combatLog[0].rngSeed,
    inputs: combatLog.map(t => ({ tick: t.tick, action: t.action })),
    version: GAME_VERSION,
  });
}

매 결정 기준

상황	Approach
Casual mobile, low-skill players	Soft revenge (one-shot button, easy win)
Hardcore PvP (EVE)	Persistent kill mails, no auto-balance
New player onboarding	Newbie shield (3-7 days)
Whales attacking f2p	Power-ratio shield + bounty system

기본값: 72h retaliation window + power-ratio shield + escalation telemetry alert at score ≥ 10.

🔗 Graph

부모: Live Operations (LiveOps) · Player-Experience-Modeling
변형: Jailing · Revenge-Cycle-Dynamics
응용: War-Commander-Combat-Ecosystem · Mobile Strike · EVE 온라인
Adjacent: Prisoners-Dilemma-Models · Alliances-and-Sector-Hegemony

🤖 LLM 활용

언제: PvP balance proposal 작성, retention drop 의 revenge-cycle 진단, alliance war event design. 언제 X: PvE-only 게임, single-player narrative — revenge loop 적용 X.

❌ 안티패턴

Whale-stomping unchecked: power gap shield 없으면 신규 유저 대량 이탈.
Infinite loop fuel: revenge buff stacking → exhaustion + churn.
No exit ramp: 매 player 가 cycle 에서 quit 할 수 있는 mechanism (peace treaty, alliance switch) 없으면 toxic.
Hidden retaliation: 매 attack notification 없으면 cycle 자체가 발생하지 않음.

🧪 검증 / 중복

Verified (Kixeye War Commander postmortems, CCP EVE devblog 2023-2025).
Cross-ref: Mobile Strike LiveOps GDC talks.
신뢰도 A.

🕓 Changelog

날짜	변경
2026-05-08	Phase 1
2026-05-10	Manual cleanup — full revenge-cycle anatomy + 7 patterns + decision matrix

6.2 KiB Raw Blame History