Reports from multiple servers point to a serious Throne and Liberty castle siege issue: a player takes the throne early, becomes effectively unkillable, and can hold the objective long enough to swing the entire siege outcome. Because siege rewards and ownership can influence a server’s economy, the community impact goes beyond “one unfair win” and can ripple into market prices, guild politics, and how players plan their progression.

This article summarizes what’s being claimed and observed without providing a how-to. You’ll learn the common signs of the abuse, why it’s so disruptive, what actions to take during a siege, and how to reduce the damage to your guild’s long-term plans (including how to think about Throne and Liberty Lucent spending when the economy gets shaken up).

What’s happening: a throne-holder who can’t be damaged

The core allegation is simple: during castle siege, a player interacts with the throne objective and then triggers a state where they can still be targeted, but incoming damage does not register. In practice, this looks like a “permanent immunity” or “invulnerability” state that lasts long enough to decide the siege.

Community chatter suggests it’s not just “good gear” or “evasion stacking.” The pattern described is closer to a collision or geometry interaction near walls or throne-room structures where attacks fail to connect properly. The result is a throne-holder who can be focused by dozens of players and still take zero meaningful damage.

Why this is a big deal for sieges and the economy

Castle siege is designed around coordinated objective pressure: you trade cooldowns, rotate groups, and commit resources to dislodge whoever controls the throne. If a single character becomes immune to damage, the siege stops being a contest of strategy and becomes a contest of whether anyone can bypass the bugged state.

That matters because siege outcomes can affect:

• Guild progression and recruitment (wins attract players; losses cause churn).
• Server economy stability (ownership and rewards can shift supply and demand for high-value items).
• Player currency planning, including how people budget premium currency for upgrades, traits, and market purchases.

When a siege is decided by an exploit, legitimate groups often respond by over-investing in counter-builds, consumables, and “just in case” gearing. That can create inflation pressure and make it harder for newer or mid-tier players to keep up.

Common loadouts mentioned in reports (and what that does and doesn’t mean)

Multiple reports associate the abuse with tanky weapon setups, most commonly Sword and Shield as a foundation. You may also see people speculate about pairings like Sword and Shield plus a high-mobility offhand (for example, a dagger) to reach the throne quickly and survive initial focus.

Important context: none of this proves those weapons are “the problem.” Sword and Shield is naturally strong at objective play, and many legitimate defenders run it. The key difference is not “they’re tanky,” but “they are taking no damage at all” in situations where even the best defensive builds should still be losing health under concentrated fire.

How to recognize the exploit during a live siege (without false accusations)

Because sieges are chaotic, it’s easy to mistake strong mitigation for illegitimate immunity. Use a higher standard before calling it out.

• Zero damage intake under sustained focus from many players, including burst windows.
• No visible health movement even when crowd control lands and the target is clearly being hit.
• The target remains targetable (you can click them), but attacks behave as if they are not connecting.
• The behavior occurs at a specific spot near throne-room structures or walls, and repeats when they return there.

What can look similar but may be legitimate

• Strong shielding and healing rotations (health moves, but quickly returns).
• Damage reduction stacking (damage numbers appear, but are low).
• Temporary invulnerability effects that have clear durations and downtime.

If the target’s health never moves and the pattern is location-dependent, that’s when it aligns most closely with the exploit reports.

What to do if you encounter it in your siege

You can’t “outplay” a bug the same way you outplay a build, but you can reduce its impact and preserve evidence for enforcement.

1) Switch from “kill the throne-holder” to “control the siege map”

If the throne-holder is truly immune, dumping your entire raid into them can lose you the rest of the siege. Instead, reassign groups to:

• Control choke points to limit reinforcements reaching the throne room.
• Disrupt enemy respawn routes and pick off supports and runners.
• Win side objectives that still contribute to siege momentum and pressure.

Even if the throne is stalled, denying the enemy the ability to stabilize can create windows if the exploit state breaks or if the player is forced to move.

Take a look at: the KR patch notes preview that mentions siege fixes

2) Force displacement and repositioning

Reports suggest the issue may be tied to specific geometry. Without relying on any one “magic counter,” prioritize tools that make the throne-holder move. If your comp has knockbacks, pulls, fears, or displacement-style crowd control, coordinate them in waves to push the target away from the suspected bugged location.

This won’t always work, but it’s one of the few responses that targets the likely underlying trigger: positioning.

If you suspect exploit abuse, capture:

• 30–60 seconds of continuous focus where many attacks land and health does not change.
• Clear timestamps and the siege context (throne room, objective state).
• Multiple perspectives if possible (a healer view plus a DPS view helps).

Clean clips matter more than angry chat logs. Enforcement teams typically need unambiguous proof.

4) Report it through official channels, not harassment campaigns

Exploit reports are most effective when they’re specific and repeatable for QA. Keep reports factual: who, where, when, and what you observed (immune to damage while targetable, location-dependent behavior, etc.). Avoid brigading or witch-hunting, especially when defensive builds can legitimately look “unkillable” for short periods.

Risk reality: exploit use can lead to permanent bans

Community accounts repeatedly mention severe penalties for players who used similar siege exploits in the past, including permanent bans and action against associated accounts or guildmates who materially assisted. Even if someone “gets away with it” once, it’s the kind of behavior that tends to be investigated after the fact, especially when siege outcomes are publicly visible and heavily reported.

If your guild leadership is tempted to respond with “fight fire with fire,” don’t. The short-term win is rarely worth losing an account, a roster, or months of progress.

How this affects Lucent planning (without turning your budget into panic spending)

When siege integrity is questioned, players often react by making rushed purchases: emergency gear swaps, expensive trait changes, or overpaying on the marketplace. That’s exactly when your progression budget can get inefficient.

Instead, treat this like any other economy shock:

• Delay impulsive upgrades until you confirm what’s actually needed for your role.
• Prioritize flexible power (general survivability and consistent damage) over niche “anti-one-player” tech.
• Keep a reserve for normal progression needs like enhancements, traits, and consumables.

If you’re short on time and want to keep your build plans on schedule, some players choose to buy Lucent to avoid falling behind during chaotic weeks. If you do, focus on steady, planned spending rather than reacting to one siege incident. The goal is stability, not revenge gearing.

What developers typically need to fix issues like this

While only the dev team can confirm root cause, the description fits a common category of MMO bugs: collision/line-of-sight or hit registration failing when a character is positioned in a spot where the server believes attacks cannot connect. Fixes usually involve:

• Adjusting collision meshes near objectives and walls.
• Validating hit registration differently in objective zones.
• Adding failsafes that cancel objective control if damage can’t be applied correctly.
• Improving detection for abnormal “damage taken = 0” patterns during siege.

Until a confirmed fix lands, the best community response is consistent reporting with high-quality evidence.

Take a look at: our Lucent planning guide for long-term progression

Build a “siege incident” checklist

• Assign 1–2 players to record key moments (not everyone).
• Decide who files the report and what evidence format you’ll use.
• Define a mid-siege pivot plan if the throne-holder can’t be killed.

Train objective discipline

Even without exploits, many sieges are lost because too many players chase kills. Drill the basics:

• Rotate groups on the objective instead of stacking everyone at once.
• Maintain a backline screen so supports aren’t free-cast targets.
• Save burst for coordinated windows rather than random cooldown dumps.

If an exploit appears, disciplined teams adapt faster and bleed less time.

Keep your economy resilient

When the server mood swings, marketplace prices can spike. A simple approach:

• Stock core consumables during calm weeks.
• Upgrade in planned milestones, not after losses.
• Use premium currency only when it clearly advances your next content goal.

This is where Throne and Liberty Lucent farming routines and careful budgeting matter most: steady income and steady spending beat emotional spending every time.

Frequently Asked Questions

Strong tanks still take damage under concentrated focus. The reports describe a state where the target remains targetable but effectively takes none, which points to a bug rather than normal mitigation.

Should we change our comp to counter this?

Don’t rebuild your entire roster around one incident. Add more displacement and objective control tools if your comp is lacking them, but keep your core siege plan intact.

What’s the safest way to respond if we see it live?

Pivot to map control, attempt coordinated displacement to force movement, and record clear evidence. Avoid harassment and focus on reporting.

Can using or assisting with siege exploits get you banned?

Yes. Exploit abuse in competitive modes is typically treated as a major violation, and community reports have repeatedly mentioned permanent bans for similar behavior.

How should I handle my currency budget when siege drama spikes prices?

Stick to planned upgrades and avoid panic buys. If you use premium currency for progression, keep it targeted to upgrades you were already planning, such as Lucent for gear upgrades, rather than reactive spending.