Baron Balatro Joker

Needs hand size and a King-rich deck; it is not a generic played-card Joker.

It is unlockable and can appear through normal shop play.

Baron gives X1.5 Mult for every King held in hand, so its plan is to keep Kings rather than play them. Build hand size, convert cards toward Kings, and choose a scoring hand that leaves as many Kings unplayed as possible. It is a held-in-hand engine with a high ceiling, but it needs a deck shape and room to breathe before its multiplier becomes reliable.

Baron has no Joker-board direction, but hand layout and played-card choice matter. Keep Kings in hand and score with another completed hand whenever possible. In a King-heavy deck, reserve four Kings, play the minimum cards needed to make a legal scoring hand, and let those held Kings supply the multiplier. Put Brainstorm’s copied target on the far left if it is copying Baron.

Blueprint and Brainstorm are premium partners once several held Kings already make Baron strong; copying an underfed Baron is rarely exciting. Triboulet can share a King-focused deck, but it uses played Kings while Baron uses held Kings, so decide how many to reserve versus score. Hand-size support improves both consistency and the number of active held Kings.

Skip Baron when the deck is not King-rich, when hand size is low, or when the run must play its Kings to score. It is poor as an emergency purchase because a single ordinary hand with no held Kings produces no value. Take a direct scoring option first if the current blind is already difficult.

The classic mistake is playing all the Kings in the scoring hand and expecting Baron to pay for them. It only checks Kings held in hand. Do not confuse it with Triboulet’s played-card trigger. Also avoid copying Baron with Blueprint or Brainstorm before your deck and hand size support the original; two empty engines are still empty.

Treat the current in-game tooltip as the source of truth: patches, platform versions, and mods can change values, availability, or interactions. This rating is editorial rather than permanent; it weighs copy value, scaling ceiling, route stability, and required setup. When a version changes, the tooltip is checked before strategy notes and tiers are revised.