I suppose the question also applies to petrified, paralyzed, and stunned as they also inflict incapacitated, but unconscious was the strangest to me.


1 Answer 1


A creature immune to the incapacitated condition cannot be incapacitated unless something explicitly ignores this immunity

The unconscious condition causes the following effects:

  • An unconscious creature is incapacitated, can't move or speak, and is unaware of its surroundings.
  • The creature drops whatever it's holding and falls prone.
  • The creature automatically fails Strength and Dexterity saving throws.
  • Attack rolls against the creature have advantage.
  • Any attack that hits the creature is a critical hit if the attacker is within 5 feet of the creature.

If a creature, such as the Warforged Colossus, were immune to the incapacitated condition then only the first bullet point would be prevented. This means the creature would be unconscious, drop what it's holding, fall prone, be unable to move or speak, be unaware of their surroundings, and so forth. This would prevent the creature from doing a great number of things but it notably would not prevent them from taking actions, bonus actions, and reactions, as this is what the incapacitated condition does. Thus, yes, an unconscious Warforged Colossus would be able to take actions as per usual.

However, it is worth pointing out that there are very few ways to apply the unconscious condition to a monster aside from a GM allowing them to make death saves instead of dying outright when reaching zero hit points and a creature choosing to knock a creature unconscious instead of having them die.

  • 2
    \$\begingroup\$ It's worth pointing out that "can't move" is kind of ambiguous. A DM would probably be within their prerogative to interpret that as "cannot move their body", rather than "cannot use their Movement". Actions would therefore be limited to those which do not require motion (like an innate fear power, for example). In the case of the Warforged Colossus, perhaps the incinerating beam, but limited to an arc of fire. It would also have to guess when to fire, since it is unaware of its surroundings. \$\endgroup\$ Commented Dec 25, 2019 at 22:51
  • \$\begingroup\$ @keithcurtis Yeah the exact extent of "can't move" could probably be it's own question, except I'm not really sure what an answer would draw on... \$\endgroup\$ Commented Dec 25, 2019 at 23:09
  • \$\begingroup\$ I agree. I just wondered if it were worth folding the ambiguity into your answer. I.e. this is a valid interpretation, but not necessarily authoritative. Your call. \$\endgroup\$ Commented Dec 26, 2019 at 0:40
  • \$\begingroup\$ @kiethcurtis No, it’s almost certainly referring to “cannot take movement actions”. \$\endgroup\$
    – nick012000
    Commented Dec 26, 2019 at 0:45
  • 2
    \$\begingroup\$ @nick012000 Here is a question discussing this very thing: 'What's the difference between “can't move” and “speed becomes 0”?" \$\endgroup\$ Commented Dec 26, 2019 at 1:27

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .