Combat logging in roleplay is when a player intentionally leaves or disconnects from the server to avoid a fight, danger, or in‑character consequences during an active RP situation. Most roleplay communities treat it as cheating and a serious rule break because it ruins the story and denies others their scene.

What combat logging means

  • It usually happens when a character is:
    • In a gunfight, fistfight, or active combat.
* Being chased or hunted by other players or police/LEO.

* About to be arrested, robbed, or otherwise face negative consequences.
  • The key idea: you use logging out as an out‑of‑character escape button from in‑character danger, instead of playing the situation out.

In many server rule sets, even “convenient crashes” that always happen under pressure are treated as intentional combat logging if it becomes a pattern.

Why it is a big deal in RP

  • It breaks immersion:
    • Other players suddenly lose their target, suspect, or scene with no in‑world explanation.
  • It dodges consequences:
    • The player avoids death, jail time, losing gear, fines, or story fallout they normally would have to face.
  • It can waste other players’ time:
    • People who set up a sting, chase, or ambush lose the payoff of their story because one person hit “disconnect”.

Many serious RP servers treat this as worse than some other rule breaks, because it shows a lack of intent to roleplay losses as well as wins.

Common examples in roleplay servers

“Combat logging is defined as logging out when roleplay is active.”

Typical examples you’ll see in rules pages:

  1. Logging out:
    • During a firefight or brawl.
 * While being arrested, cuffed, or transported by police.

 * During or right after a robbery, drug deal, or crime gone wrong.
  1. Disconnecting just as:
    • Your car is disabled in a chase and you’re about to be caught.
 * You’re downed and waiting for medics, to avoid the outcome.
  1. Repeated “crashes” only when you are about to lose, with no attempt to contact others or return, which servers may treat as intentional.

By contrast, if you genuinely crash or your internet dies, many communities expect you to rejoin and/or contact involved players in Discord or similar as soon as possible to continue or fairly close the scene.

How servers usually punish it

Many RP communities:

  • Mark combat logging as:
    • Exploiting or metagaming, since you’re using OOC mechanics to alter IC outcomes.
  • Use strong punishments, for example:
    • Community strikes or temporary bans on lighter servers.
* Permanent bans on stricter, serious‑RP communities.

Some servers explicitly state that:

  • Logging out at any point during active RP is considered exploiting, including rage‑quitting, saving gear, or leaving while restrained.
  • Staff may review context and any attempt you made to reconnect or resolve the scene before deciding on the final punishment.

Quick checklist: am I combat logging?

You are probably combat logging if:

  • You know your character is:
    • In combat, being chased, arrested, robbed, or otherwise in an ongoing scene.
  • And you:
    • Disconnect, close the game, or “let your connection drop” to avoid losing, dying, going to jail, or facing RP consequences.

You are usually safe if:

  • You crash unintentionally or must leave for a real‑life reason, and:
    • You return as soon as possible, or
    • You contact involved players/staff to explain and arrange a pause or follow‑up.

In short, combat logging in roleplay is using a logout to dodge the story when things go bad, instead of staying in character and accepting the outcome.

Information gathered from public forums or data available on the internet and portrayed here.