Baldur's Gate 3 List of bugged actions and reactions

가이드: bg3 · 게시일 2026년 8월 14일 · 3,440 자 · 약 18 분

작성자 BG3 Hub Editorial · 최근 업데이트 2026년 8월 15일 · 검수 BG3 Hub Editorial

bg3 in-game screenshot — Steam CDN · shared.akamai.steamstatic.com

Quick Answer: The Baldur's Gate 3 List of bugged actions and reactions is a reference catalogue of abilities that do not behave as their tooltips suggest, or that have missing, misleading, or inconsistent descriptions, effects, or locations.

What This List Covers

The Baldur's Gate 3 List of bugged actions and reactions covers actions and reactions that fail to match their in-game description, plus entries with missing or misleading information about how they work. The key point is not that every listed ability is unusable; it is that the game’s text, icon, or trigger logic does not line up cleanly with the actual result you get in play.

That distinction matters because BG3 has a lot of layered systems: class actions, racial actions, item-granted reactions, passive triggers, and temporary combat-only effects can all interact in ways that are easy to misread. A player may assume a reaction is broken when the real issue is that the trigger condition is narrower than expected. In other cases, the tooltip is the problem and the ability is functioning consistently with the underlying implementation, just not with the wording.

The current wiki list is explicitly not comprehensive. That is important because it means you should treat it as a living reference, not as a complete bug registry. If you are troubleshooting an odd combat result, the list is useful for checking whether the game has a known mismatch between the displayed behavior and the actual mechanics. It is less useful as a full guarantee that an effect is clean, tested, or safe to build around.

Concrete examples from the list

Boon of the Unstoppable: when the Bhaal cultists chant the ritual that triggers this action, it applies a bugged status that displays as Unstoppable but lacks the actual damage reduction for the first hit each round.
Charge (Deep Rothé): this ability can target dead creatures, which creates unintended interactions with effects such as Cull the Weak.
Clench of the North Wind: unlike other Way of the Four Elements actions, it still keeps a HasVerbalComponent spell flag from Hold Person, so it cannot be used while Silenced.

Those are the kinds of entries this reference is built around: real in-game names, real trigger conditions, and real failure modes rather than vague community suspicion. For the underlying catalogue itself, see the list page.

Definition, Effect, and Requirement

The list exists to document actions and reactions that do not function as expected, and its practical effect is simple: if an entry appears here, you should assume the tooltip, trigger, or location may be unreliable until confirmed in your own run. That is especially true for combat reactions, because those are often timing-sensitive and can misfire in ways that are hard to notice until a turn has already resolved.

In gameplay terms, there are three broad categories to keep in mind. First are effects that display the wrong outcome, such as a status that appears to grant protection but does not fully do so on the first instance. Second are actions with hidden or inherited restrictions, such as a spell-derived action still obeying a verbal component rule when players expect it not to. Third are abilities with targeting or interaction issues, such as an attack that can target dead entities and therefore triggers other on-hit logic in ways that should not happen.

This matters most for build planning. If you are building around a reaction-heavy character, or around a combat route that depends on a specific class action landing every time, a bugged entry can distort the value of the whole setup. A monk action that fails under Silenced, for example, is much less flexible than the same action would appear from a casual tooltip read. Likewise, a status that looks like Unstoppable but does not actually reduce the first instance of damage the way the proper version does can mislead you in a fight where burst damage matters.

What the list is actually telling you

The ability may be visually correct but mechanically wrong.
The tooltip may be incomplete, especially on inherited or transformed abilities.
The trigger may happen in situations the design clearly did not intend.
The listed location or source may be misleading, making the ability harder to verify in your own save.

When to treat an entry as high risk

When the action is part of a boss sequence or scripted combat.
When the reaction protects a key character from burst damage.
When the effect depends on status application, especially Silenced, Unstoppable, or on-hit chaining.
When the ability comes from a form, summon, or item grant rather than a clean class entry.

For broader cross-checking, keep a sibling reference handy such as reaction timing guide or status condition reference so you can compare how a normal action should read against how the bugged one behaves.

bg3 gameplay screenshot — In-game screenshot

Where These Bugged Actions Come From

Bugged actions and reactions in Baldur's Gate 3 usually come from a few predictable sources: class features, condition-triggered boss abilities, item-granted reactions, and actions inherited from another spell or form. That origin matters because it tells you where to verify the behavior and what kind of character is most likely to run into it.

The cleanest example is Clench of the North Wind. The list notes that it retains the HasVerbalComponent SpellFlag from its parent spell Hold Person. That means its bug is not just “this action is broken”; the actual issue is that the inherited spell metadata is still being applied. If you know the source, you can already predict the failure case: Silenced combat states will block it even though another player might reasonably expect a martial-style action from the subclass to ignore that restriction.

Boon of the Unstoppable is different. It is not a player-picked action from a standard leveling menu. It is triggered by a ritual from Bhaal cultists, which means the source is environmental or encounter-driven rather than build-driven. That matters because the bug only appears during a specific scripted combat context. You are not testing this on your hotbar at camp; you are seeing it inside a boss-adjacent encounter where a misleading status icon can alter your threat assessment.

Charge (Deep Rothé) is yet another type. It is a creature ability, and the practical issue is targeting logic. If an ability can target dead creatures, it may accidentally interact with effects like Cull the Weak or other on-hit systems in ways that seem absurd in normal play. That is not just a visual bug. It changes combat resolution and can create edge cases around corpse targeting, cleanup damage, and kill confirmation.

Common source types

Class actions that inherit from a different spell.
Creature abilities tied to summon or transformation states.
Scripted boss or cultist combat actions.
Reactions attached to conditions, gear, or passive procs.

What that means in practice

Check whether the ability is native or inherited.
Check whether silence, concentration, or status immunity should matter.
Check whether the bug appears only in one encounter or everywhere.
Check whether the issue is with targeting, trigger logic, or the resulting status.

If you are building a route around one of these systems, pair this reference with class action reference and boss mechanics guide so you can separate ordinary restriction from actual defect.

Notable Entries and Their Real Impact

The most useful way to read the list is by impact, not by raw number of entries. A bug that only changes a visual label may be annoying; a bug that changes whether a first hit is reduced, or whether a reaction can be triggered at all, can swing a fight. The entries exposed in the current list show both kinds.

Boon of the Unstoppable is the clearest high-impact case. The list says the cultist ritual applies a bugged Unstoppable status that displays correctly but lacks actual damage reduction for the first damage instance each round. In practice, that means your first burst window into the target is stronger than the status icon suggests. The subtle part is that later hits in the same round are properly reduced to 1 by the correct Unstoppable status condition. So this is not a simple “status does nothing” bug. It is a split behavior bug, and that split can mislead players who are judging the whole round off the first hit.

Charge (Deep Rothé) has a different kind of impact. Allowing a charge to target dead creatures sounds minor until you remember how many BG3 effects key off hit confirmation, corpse states, and on-hit triggers. If an ability can lock onto a dead body, it can become a delivery mechanism for unintended proc chains. The list specifically mentions Cull the Weak, which is exactly the sort of system that turns a targeting edge case into a combat exploit or a rules headache.

Clench of the North Wind is more about consistency and planning. A Way of the Four Elements action that still obeys a verbal component restriction is not necessarily useless, but it does mean the subclass is less self-contained than the player may think. In a Silenced zone, or against enemies that can impose silence, the action can fail where a similar-looking martial technique would otherwise have worked. That can ruin a turn if you were counting on it to control the field.

Practical examples of impact

A boss opens with a status that appears to make it safe to burst, but the first hit is not reduced as expected.
A summoned beast or transformed creature hits a corpse and accidentally triggers another effect.
A monk action fails in silence despite looking like a non-spell technique.

How to judge whether an entry matters to you

If it changes damage taken, treat it as high priority.
If it changes trigger conditions, test it before a serious fight.
If it changes only the tooltip or display text, note it, but do not overbuild around it.
If it affects a boss or encounter-specific action, assume the encounter script may be part of the risk.

For players tracking build reliability, this section is where a build planning checklist or combat status guide becomes more valuable than a pure bug list.

How to Check, Trigger, or Verify These Entries

You verify bugged actions and reactions in Baldur's Gate 3 by testing them in the exact context they claim to work in, then checking whether the displayed description, trigger requirement, and combat log all agree. That sounds basic, but it is the only reliable way to sort a true bug from a misunderstanding of BG3’s layered rules.

The first step is to trigger the ability in a controlled encounter if you can. For example, if the issue involves Silenced, you need a combat or field state where silence is definitely active. If the issue involves a status like Unstoppable, you need a target that can actually receive the status and survive multiple hits long enough for the round-based behavior to show itself. If the issue involves targeting dead creatures, you need a scenario where a corpse is present and the ability is available before the combat state changes.

The second step is to watch for hidden inheritance. Clench of the North Wind is the classic example from the current list because it keeps the HasVerbalComponent flag from Hold Person. That means the ability may be acting “correctly” according to inherited data while still being misleading to the player. If you do not check the underlying source effect, you can waste time assuming the ability should behave like its subclass identity rather than its parent spell.

The third step is to compare what happens in combat to what the tooltip claims. This is especially important for actions that look like passives, or actions that are triggered automatically by a script. The list is built around discrepancies between expected and observed behavior, so the “bug” is often visible only once the combat log or a specific damage event is reviewed closely.

A practical verification routine

Save before the encounter or test.
Use the ability in a state that matches the tooltip.
Repeat the test in a second situation, such as silenced, on a corpse, or after the first hit of the round.
Compare the result with the listed behavior rather than with a broad intuition about how the system should work.

Things that commonly fool players

A status icon appears right, but the underlying mitigation is wrong.
A subclass action inherits a hidden spell flag.
A creature ability is usable on an invalid target.
A scripted combat action behaves differently from the same word used elsewhere in the game.

For more disciplined testing, cross-check with condition rules reference and combat log guide. Those sibling references help separate visual state from actual resolution.

Best Uses and When to Skip Them

The best use of a bugged action or reaction is usually not to lean into the bug itself, but to understand the risk so you can either exploit the stable part of it or avoid the unstable part. The list is most valuable when it helps you decide whether an ability is trustworthy enough for a serious build or encounter plan.

Boon of the Unstoppable is a good example of a mixed-use entry. If you are facing it, the fact that the first damage instance each round is not reduced by the bugged status means burst opening matters more than the tooltip suggests. If you are on the receiving side of that effect, do not let the Unstoppable label overstate the protection. In both cases, the practical lesson is to treat the first hit separately from the rest of the round.

Charge (Deep Rothé) is best treated as a cautionary example rather than a centerpiece. A charge that can target dead creatures is not the kind of thing most players should build around. It is more useful as a reason to avoid assuming corpse targeting is harmless. If you are running an on-hit build with effects like Cull the Weak, you should be especially careful about any action that can legally point at a dead target. That kind of interaction can muddy damage sequencing and waste a turn.

Clench of the North Wind is the sort of entry where skipping is often the right call if your party expects silence-heavy encounters. If you are relying on it for control, and your route regularly includes Silenced zones or enemies that apply silence, you should prioritize a different control tool with clearer rules. If, however, your party rarely faces silence and the action fits your rotation, the bug may be inconvenient but not fatal.

Good reasons to keep an ability despite a known bug

The bug only affects a narrow encounter script.
The wrong behavior is easy to play around.
The action still performs its main job consistently.
Your party has redundant options if it fails.

Good reasons to replace it

The bug changes survival math or damage reduction.
The action fails in common status conditions.
The ability is central to your turn economy.
A clean alternative exists with the same role.

Example replacement thinking

Replace a silence-sensitive action with one that does not inherit a verbal restriction.
Replace a reaction with a more transparent damage-prevention tool if the tooltip is unreliable.
Replace a creature ability if it is only valuable through an edge-case bug.

For adjacent guidance, reaction priority guide and party role guide are the most natural sibling links here.

Troubleshooting Common Misreads

The most common misread is assuming every weird result means the game is bugged in the same way. In practice, many BG3 “bug reports” are actually rule mismatches, hidden inheritance, or special-case encounter scripting. The list helps because it names the exact mismatch, but you still need to read the situation carefully.

A classic misread is the Unstoppable problem. Players see the icon and assume all incoming damage should be reduced. The list shows a more specific issue: the bugged version does not reduce the first damage instance each round, while the correct Unstoppable status does handle subsequent instances properly. So if you see one hit landing for full value and the rest dropping to 1, that is not random. That is the pattern the list is warning you about.

Another common mistake is assuming subclass identity overrides inherited spell data. Clench of the North Wind disproves that assumption. Because it keeps the HasVerbalComponent flag from Hold Person, it can be blocked by Silenced even though the player may think of it as a monk action rather than a spell. That is a rule-source issue, not a simple usability issue. If you ignore the source, you will keep encountering what looks like inconsistent behavior.

A third misread is treating corpse targeting as harmless because the target is already dead. Charge (Deep Rothé) shows why that is unsafe. If an ability can point at a dead creature, it can still influence other systems that care about hit events, target legality, or on-hit consequences. Dead does not always mean inert in BG3’s combat engine, and that matters whenever you are using a build that chains effects off one another.

Fast checks when something feels wrong

Confirm whether the target is alive, dead, or in a special scripted state.
Confirm whether silence, darkness, fear, or another condition is suppressing the action.
Confirm whether the icon is describing the effect or merely displaying a status label.
Confirm whether the ability is native, inherited, or encounter-scripted.

When the issue is probably not a bug

The action is blocked by a visible status in the combat log.
The target is immune to the condition being applied.
The effect only works on a subset of enemies.
The ability is part of a scripted phase change rather than a normal action.

For players who want to keep their runs stable, this is the point where a status immunity reference and encounter scripting guide pay for themselves.

The best sibling guides for this topic are the ones that help you interpret the same combat systems from another angle. A bug list becomes more useful when you can compare it against clean reference pages for conditions, reactions, and class actions.

Useful internal links:

These are the nearest practical matches because the bug list is not a build guide on its own. It is a reliability map. If you are using Boon of the Unstoppable, the status reference helps. If you are testing Clench of the North Wind, the monk action guide helps. If you are trying to understand why a reaction fired at the wrong time, the combat log guide is the one that usually clears things up faster than trial and error.

Sources

스크린샷

검수

BG3 Hub Editorial

Editor · GameFleet

전문 분야: Editorial team behind BG3 Hub. Content is compiled from official patch notes, community wikis, and playthrough notes, then reviewed and updated on schedule.

편집 정책

출처

🔥 지금 뜨는 검색어

articleType.reference_guide

발더스 게이트 3 네크로맨서 아이템 최고 추천 죽음 영역 클레릭

BG3의 죽음 영역 클레릭을 위한 최고의 네크로맨서 아이템을 정리합니다. Cherished Necromancy의 지팡이 포함, 획득 위치와 언제 스킵할지까지 다룹니다.

articleType.reference_guide

발더스 게이트 3 Enver Gortash의 활동 보고서

BG3에서 Enver Gortash의 활동 보고서를 찾아 읽고 활용하는 방법을 확인하세요. 전승상 의미, Devil’s Fee 맥락, 그리고 가장 좋은 활용처까지 정리했습니다.

articleType.reference_guide

Baldur's Gate 3 Mind Claw of Tu'narath 클래스 액션

BG3의 Mind Claw of Tu'narath는 W’wargaz의 Honour Mode 전설 행동입니다. 이게 뭘 하는지, 어디서 등장하는지, 그리고 어떻게 대응하는지 알아보세요.

articleType.reference_guide

Baldur's Gate 3 전설 행동: Weird Magic Surge 조건

Auntie Ethel의 Honour Mode Weird Magic Surge 조건이 무엇인지, 어떻게 작동하는지, 어디에서 등장하는지, 그리고 어떻게 대응해야 하는지 설명합니다.

📋 패치 노트 해설

모든 패치 노트 보기 →

🛠️ 인기 도구

이 가이드가 도움이 되었나요?

더 나은 가이드를 위해 평가해 주세요.

Share your own tip

Found something not in the guide? Submit it below — our editors review every tip before publishing. No account required.

Baldur's Gate 3 List of bugged actions and reactions