Baldur's Gate 3 Cloud of Jellyfish: Shocking Sting

Quick Answer: Cloud of Jellyfish: Shocking Sting is a free Swarmkeeper Ranger reaction in Baldur’s Gate 3 that can be triggered once per turn when you hit an enemy, using your jellyfish swarm to shock the target if it fails a Constitution save.

What Baldur's Gate 3 Cloud of Jellyfish: Shocking Sting Does

Baldur's Gate 3 Cloud of Jellyfish: Shocking Sting is the Swarmkeeper Ranger’s jellyfish-based combat reaction that applies a shock effect through a Constitution save after you land a hit. In practical terms, it is one of the three Cloud of Jellyfish options tied to the subclass feature set, alongside the swarm’s attack and teleport functions. The important part is that this is not a passive aura or a separate summon command in the usual sense; it is a free reaction-style combat option that exists specifically to convert a successful hit into battlefield pressure.

The ability matters because it gives the Swarmkeeper a second layer of value after the initial weapon strike. A weapon hit can already carry damage rider effects from weapons, enchantments, and ranger support tools, and Shocking Sting adds a control check on top. That means the ability is strongest when you are already connecting reliably, because the swarm’s effect is layered onto an attack you were going to make anyway.

A few concrete points define its combat identity:

• It is a free action / free reaction-style option rather than a spell slot spender.
• It is available to Swarmkeeper Rangers who selected Cloud of Jellyfish.
• It can be used once per turn when you hit an enemy.
• The target makes a Constitution save to avoid being shocked.
• At level 11, the upgraded version becomes Cloud of Jellyfish: Mighty Shocking Sting, which adds Disarm.

That last point is the major scaling breakpoint. Before level 11, Shocking Sting is a straightforward shock application tool. After level 11, it becomes a stronger swing tool because adding Disarm changes the role from “light control rider” to “melee threat suppression,” especially against weapon users.

This also helps explain where the ability sits inside the Swarmkeeper kit. The subclass’s Cloud of Jellyfish package includes multiple branches: one branch for extra Lightning damage, one for shock, and one for repositioning. So when players ask what Baldur's Gate 3 Cloud of Jellyfish: Shocking Sting is, the clean answer is that it is the control-oriented branch of the jellyfish swarm, designed to punish enemies you already hit rather than replace your primary action economy.

Related sibling guides

• Cloud of Jellyfish: Attack guide
• Cloud of Jellyfish: Teleport guide
• Swarmkeeper Ranger guide

Effect, Requirements, and Limits

Cloud of Jellyfish: Shocking Sting is a Swarmkeeper Ranger feature that requires you to have chosen Cloud of Jellyfish as your swarm type, and it functions as a free action that can be used once per turn after you hit an enemy. The target must then pass a Constitution save or be shocked.

The key requirement is subclass choice. This is not a universal Ranger feature, and it is not shared by other martial classes unless they are specifically interacting with Ranger multiclassing and the Swarmkeeper feature line. The game treats it as a unique feature of the Swarmkeeper subclass, meaning the ability is tied to your character build rather than to an item, spell scroll, or environmental source.

The effect is simple but impactful:

Element	Details
Feature name	Cloud of Jellyfish: Shocking Sting
Class source	Ranger, Swarmkeeper subclass
Swarm choice required	Cloud of Jellyfish
Action economy	Free reaction / free action style effect
Trigger	After hitting an enemy
Frequency	Once per turn
Save type	Constitution save
Result on failure	Target is shocked
Upgrade	Level 11: Cloud of Jellyfish: Mighty Shocking Sting
Upgrade bonus	Adds Disarm

The once-per-turn cap is one of the most important limits because it prevents the ability from snowballing across multiattack chains or dual-wield spam. In other words, if you are imagining a scenario where every hit repeatedly shocks the same target, that is not how this feature is described. The feature is designed to be a reliable occasional rider, not a full status-lock engine by itself.

The Constitution save also shapes how often it feels effective. Enemies with strong Constitution tend to resist it more often, while low-Constitution targets are more vulnerable. In real play, that means the ability tends to perform better against certain caster, skirmisher, or lightly armoured targets than against hardy frontline bruisers. Since the effect is attached to a hit, it still rewards accuracy, advantage, and attack bonuses even though the save itself is the final gate.

The level 11 upgrade is the clearest “requirement plus limit” breakpoint worth remembering. Mighty Shocking Sting is not a different feature you separately unlock from a book or item; it is the upgraded form of the same swarm-based effect at higher Ranger level. That matters because it changes how the feature should be evaluated in builds that expect to reach late-game Ranger thresholds. If your campaign is ending in the midgame, you are evaluating the base shock effect. If you are planning for the full late-game kit, the disarm upgrade becomes part of the calculation.

For players comparing swarm options, this also helps clarify that the jellyfish swarm is the control-forward variant. If you want more direct damage, the attack branch exists. If you want relocation and safety, teleport exists. If you want a CC rider that can punish weapon carriers later, Shocking Sting is the branch to look at.

You might also like

• Baldur's Gate 3 how save arabella daughter mother father thief locke komira kagha snake tieflings
• Baldur's Gate 3 Is There Crossplay Updated 8/3/2023 Crossplay for is currently unavailable Beginner Guide
• Baldur's Gate 3 dark urge romance reactions astarion laezel shadowheart
• Baldur's Gate 3 dungeons and dragons spells players expect work same: what actually changes
• Baldur's Gate 3 next update patch 2 origin character epilogues explained

Where to Get It and How It Unlocks

You get Cloud of Jellyfish: Shocking Sting by playing a Swarmkeeper Ranger and choosing Cloud of Jellyfish as your swarm feature selection. It is not crafted, bought, looted, or equipped from a separate inventory slot. It is part of the subclass feature progression, which means the unlock path is build-based rather than item-based.

The most important practical step is the subclass selection itself. If your character is not a Swarmkeeper, you do not have access to this feature line. If you are a Swarmkeeper but chose a different swarm, you also do not get this exact effect. The game’s feature structure distinguishes between the various gathered swarm options, and the jellyfish version is the one that grants Shocking Sting.

Here is the acquisition flow in plain terms:

• Create or respec into a Ranger.
• Choose the Swarmkeeper subclass.
• Select Cloud of Jellyfish as your swarm type.
• Use Shocking Sting after landing a hit on an enemy.
• Reach level 11 to upgrade into Mighty Shocking Sting.

Because this is tied to subclass identity, the respec angle matters. If you started as another Ranger subclass and want this tool later, you need to rebuild your Ranger choice through a respec rather than hunt for a physical unlock item. That distinction is easy to miss when players search for the ability as if it were a spell, weapon special, or Act-specific reward.

There are also a few common confusions around “acquiring” the feature that are worth clearing up:

• It is not a consumable.
• It is not an equipment passive from boots, gloves, or a staff.
• It is not a scroll-castable effect.
• It is not tied to a quest reward in the data available here.
• It is not a summon you can recruit as a separate creature.

The wording around the swarm can make it sound like a pet, and in some descriptions it is easy to mentally group it with conjured allies. But mechanically, the jellyfish swarm is better understood as a subclass resource or feature package that modifies combat choices after your attacks.

If you are building toward it, the best way to think about the unlock is that it sits inside the Ranger progression curve. That means the major decision point is not “where do I find it?” but “do I want the Swarmkeeper branch that provides this utility?” If the answer is yes, then your acquisition path is entirely level-and-subclass driven.

Practical acquisition checklist

• Confirm you are on Ranger.
• Choose Swarmkeeper at subclass selection.
• Pick Cloud of Jellyfish.
• Check that the feature appears in your combat options.
• Continue leveling to 11 if you want the upgraded version.

Best Uses in Combat

Cloud of Jellyfish: Shocking Sting is best when you want to turn a good hit into a tempo gain, especially against enemies whose turn you want to disrupt. The ability does not need to be your whole game plan; it works best as a layered control rider on top of an already functional attack routine. Because it triggers after hitting an enemy, it naturally fits builds that attack consistently and can force meaningful save pressure over time.

The strongest use cases usually fall into three categories:

• Disrupting melee enemies that rely on weapons and direct approach.
• Punishing priority targets after you have already connected with a weapon attack.
• Supporting control-heavy party play where a small shock effect helps open windows for allies.

The level 11 version is especially valuable in encounters where Disarm is a meaningful payoff. If you are fighting enemies whose weapon attacks define the encounter, stripping that option can be more valuable than raw damage. In late-game encounters, that makes the upgraded version feel much closer to a true utility control piece than a simple rider.

The ability also pairs naturally with builds that already want to attack on the front line or from midrange. Since the trigger is “when hitting an enemy,” the feature rewards characters who can reliably land weapon hits and stay in range to keep taking advantage of the once-per-turn effect. In that sense, it is often most comfortable on Rangers who fight in a steady rhythm rather than on builds that frequently disengage, reposition, or spend most turns on non-attack actions.

A few examples of when Shocking Sting shines:

1. Against a dangerous swordsman or bruiser: the shock can force a failed save on a target that is threatening your frontline, and the level 11 upgrade can completely blunt the target’s weapon pressure.
2. Against a lightly protected backliner: a hit followed by shock can create a narrow but useful opening for the party to focus-fire.
3. During a sustained boss or elite fight: if the enemy is likely to survive multiple turns, a repeated once-per-turn rider can matter more than a one-off damage spike.

It is also worth noting the feature’s role alongside the other Cloud of Jellyfish options. If you are already using the jellyfish swarm for attack or teleport utility, Shocking Sting becomes part of a flexible toolkit rather than a standalone gimmick. That flexibility is the main reason to keep it in a build even when it is not the flashiest option in a single combat log.

Good scenarios for Shocking Sting

• Locking down weapon-based enemies with the Mighty Shocking Sting upgrade.
• Pressuring targets after a high-accuracy opening hit.
• Supporting a party that already has knockbacks, prone setups, or hard crowd control.
• Playing a Ranger who wants useful value even when not spending spell slots.

Examples of pairing it with party roles

• Frontline fighter pressure: after the Fighter commits to a target, your hit can tack on shock pressure.
• Paladin burst turns: your follow-up hit can help reinforce focus-fire on the same enemy.
• Control caster setup: even if the enemy saves against a larger spell, Shocking Sting still adds a secondary check after your attack.

When to Skip or Replace It

Cloud of Jellyfish: Shocking Sting should be skipped or deprioritized when your build or campaign context values raw damage, teleport utility, or a different control profile more than a once-per-turn shock rider. The feature is good, but it is not automatically the best member of the jellyfish package in every situation.

The most obvious reason to replace your emphasis on it is target profile. Because the effect relies on a Constitution save, enemies with robust Constitution can reduce its reliability. If you are consistently fighting opponents that shrug off light control, the shock side of the feature will feel more modest. In those cases, the attack or teleport branches of Cloud of Jellyfish may contribute more to the actual outcome of the fight.

You may also want to skip it if your Ranger build is designed around other priorities:

• Pure damage scaling: if your build is tuned to maximize weapon output and on-hit damage, a CC rider may be secondary.
• Highly mobile play: if your turns are built around constant repositioning, the teleport branch can be the better swarm choice.
• Spell-heavy support: if your plan is to use Ranger spells and battlefield control tools rather than weapon attacks, the “after you hit” trigger may not be as often relevant.
• Campaign timing: if you will not realistically reach level 11, the upgrade path loses one of its biggest late-game selling points.

The compare-and-skip question often comes down to whether you need control that changes enemy behavior or value that directly shortens fights. Shocking Sting is the former. If your party already has enough control through effects like prone, fear, or hard disables, then the jellyfish shock rider may be redundant. If your party lacks that kind of utility, then the feature becomes much more attractive.

A useful way to evaluate replacement choices is to compare the three Cloud of Jellyfish branches side by side:

Jellyfish option	Main combat value	Best for	When to favor another option
Shocking Sting	Shock on hit, later Disarm	Control and weapon disruption	When damage or mobility matters more
Attack	Extra Lightning damage	Direct damage pressure	When you need control rather than DPS
Teleport	Self repositioning	Safety and movement	When you can already hold position

This comparison is why Shocking Sting is often a “good but contextual” pick rather than an always-on answer. In parties that already have enough movement tools and burst, you may prefer damage or teleport utility. In parties that need a clean way to punish a dangerous enemy after every hit, the shock rider earns its place.

Situations where replacement makes sense

• Your party already has multiple strong crowd-control sources.
• You are fighting enemies that resist or shrug off Constitution-based pressure frequently.
• You need more movement security than another debuff rider.
• You are not planning to reach the level 11 upgrade breakpoint.

Troubleshooting, Misreads, and Common Mistakes

Cloud of Jellyfish: Shocking Sting is most often misunderstood as a passive shock aura or a separate summoned creature, but it is actually a triggered subclass feature tied to your Swarmkeeper choice. That misunderstanding causes most of the practical problems players run into when they expect it to behave like a permanent pet or a spell effect.

The first common mistake is expecting it to work on demand every time you want. It is described as being usable once per turn when hitting an enemy, so if you miss your attack, the trigger does not happen. If you have already used it on that turn, it will not repeat until the next turn. Players sometimes read “free reaction” and assume they can fish for multiple activations in the same round. That is not the case based on the available feature description.

The second mistake is overlooking the save type. The target makes a Constitution save, so high-HP and physically resilient enemies often resist it more often than frailer targets. That means the feature can feel inconsistent if you use it against the wrong profile and then assume the ability itself is weak. In reality, it is often just being pointed at the wrong target.

The third mistake is ignoring the upgrade at level 11. Many players evaluate the base Shocking Sting and never factor in Mighty Shocking Sting, which adds Disarm. That upgrade materially changes the feature’s late-game value, especially against martial enemies. If you are planning a full Ranger run, you should judge the ability across the full progression, not just the early version.

The fourth mistake is treating the jellyfish swarm as if it were a separate combat summon with independent timing. The sourced descriptions here frame it as a subclass feature package with action options, not a normal summoning spell with its own full AI turn. If you are trying to use it like a conventional summon, expectations can drift away from how the feature actually behaves.

Common misreads and the correct interpretation

Misread	Correct reading
“It shocks every hit.”	It is usable once per turn.
“It is a pet summon.”	It is a Swarmkeeper subclass feature.
“It ignores saving throws.”	The target makes a Constitution save.
“It is mainly for damage.”	Its main role is control and pressure.
“The base version is the full kit.”	It upgrades at level 11 to add Disarm.

If you are troubleshooting why it “isn’t working,” check the simplest failure points first:

• Did you actually choose Swarmkeeper?
• Did you choose Cloud of Jellyfish?
• Did your attack hit?
• Have you already used the once-per-turn effect this turn?
• Are you expecting the base version to do the level 11 Disarm upgrade?

Those checks solve most of the confusion. Once they are cleared up, the ability is usually much easier to evaluate fairly.

Related Systems and Sibling Guides

Cloud of Jellyfish: Shocking Sting makes the most sense when viewed alongside the other Cloud of Jellyfish branches and the Swarmkeeper’s overall combat loop. The ability is not a standalone gadget; it is one part of a modular subclass package built around choice after attack resolution. That is why the nearest sibling guides are the most useful cross-links, not generic Ranger primers.

The closest related systems are:

• Cloud of Jellyfish: Attack — the branch that uses the swarm for extra Lightning damage.
• Cloud of Jellyfish: Teleport — the branch that uses the swarm for repositioning.
• Swarmkeeper Ranger — the subclass identity that grants the whole suite.
• Mighty Swarm / Mighty Shocking Sting — the level 11 upgrade path that changes the status rider.

This matters because the feature’s value changes depending on which member of the swarm toolkit you are comparing it to. If your team already has enough hard control, the Lightning damage branch may be the better way to convert the swarm into immediate output. If your positioning is fragile, Teleport is often the safer pick. If you are building around disabling dangerous weapon enemies in late game, Shocking Sting becomes much more attractive because of the disarm upgrade.

It also helps to connect the feature to broader BG3 system logic:

• It benefits from attack accuracy, because you must hit to trigger it.
• It interacts with saving throws, because the target can resist the shock.
• It has clear action economy constraints, because it is once per turn.
• It scales with character level, because the upgrade arrives at level 11.

For players who like to plan builds by role rather than by flavor, that means the jellyfish swarm is best understood as a mid-to-late-game utility suite. It is not just thematic subclass dressing. The three swarm branches create real tactical differences, and Cloud of Jellyfish: Shocking Sting is the control anchor of that triad.

Nearest sibling references

• Cloud of Jellyfish: Attack guide
• Cloud of Jellyfish: Teleport guide
• Swarmkeeper Ranger build guide

Sources

• https://bg3.wiki/wiki/Cloud_of_Jellyfish:_Shocking_Sting
• https://baldursgate3.wiki.fextralife.com/Cloud+of+Jellyfish
• https://gamefaqs.gamespot.com/pc/265760-baldurs-gate-3/faqs/80865/sub-classes
• https://store.steampowered.com/app/1086940/
• https://howlongtobeat.com/?q=bg3

See also

• Baldur's Gate 3 important areas outside baldurs gate act 3
• Baldur's Gate 3 best romances dungeons dragons dnd novels feywild job
• Baldur's Gate 3 Cloud of Jellyfish: Mighty Teleport class action
• Baldur's Gate 3 how revive characters bring back life dead
• Baldur's Gate 3 best character player creations marvel witcher barbie
• Baldur's Gate 3 disco elysium harry du bois custom character
• Baldur's Gate 3 List of magic items in Act Two
• Baldur's Gate 3 List of magic items in Act Three
• Baldur's Gate 3 Baldur's Gate 3 Baldur's Gate 3's Absolute Plot Story Explained
• Baldur's Gate 3 karlach laezel human versions custom characters