Obelisk Balatro Joker

Build a high-count hand early, then pivot away from it.

It is unlockable and can appear through normal shop play.

Obelisk asks for a deliberate pivot. First make one poker hand your historical most-played hand, then begin playing other hands consecutively to grow its XMult. Track that history before buying: the card is powerful only if you can avoid the leader without sacrificing every blind. Flexible deck editing and several playable hand types make the transition safer.

Obelisk has no Joker-board direction, but its “position” is the poker-hand history. Make one hand type the obvious historical leader early, then lay out the deck to score with a different hand. For example, establish High Card as most played during setup, then pivot to upgraded Pair or Two Pair without touching High Card for the streak.

Burnt Joker helps establish reliable hand levels before the pivot, and Yorick fits discard-heavy decks that can search for an alternate hand. Brainstorm can copy Obelisk after the streak is already safe, not before. The practical synergy is a deck with enough consistency to score through a different hand type while preserving the intentionally inflated historical leader.

Skip Obelisk if one hand is the only thing your deck can play, if the current most-played hand is not safely ahead, or if a forced pivot would fail the next blind. It is not a generic scaling card: breaking the streak by playing the historical leader can erase the plan at exactly the wrong time.

A common failure is buying Obelisk and immediately playing the hand with the highest count. Before each round, check which poker hand is currently most played rather than trusting memory. Do not mistake the best current scoring hand for the correct Obelisk hand; the right play is the strongest hand that is not the historical leader.

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.