Slay the Spire 2 Cut Its Rainbow Easter Egg, but Players Are Still Arguing

Slay the Spire 2 players have been dissecting a hidden bit of code that points to a “pride rainbow” easter egg, with the discussion spreading across the game’s community after the clue was first surfaced by Madeline Zhizao Xian. According to player testing, changing a device’s date to June 25 makes the game’s menu switch to a rainbow-themed screen. After the 1.06 update, however, both the related code and the image were removed, turning what began as a small discovery into a much broader argument about intent, presentation, and silence from the developer.

For a game built around climbing runs, deckbuilding, and repeated trial and error, an easter egg would normally feel like one extra door at the edge of the map. Sometimes it opens onto a harmless joke. Sometimes it sets off the entire room. In Slay the Spire 2, it has clearly become the latter. Players first followed scraps in the code to hidden content, then noticed that the door had been shut again after a patch. Why it was put there, and why it was later removed, quickly pushed the conversation beyond simple discovery and toward questions of expression.

What makes the situation more notable is that the dispute is not just about a single menu image. Based on player tests, setting the device date to June 25 causes the menu interface to display the corresponding rainbow-themed screen. That means this was not ordinary always-visible content, but a hidden event gated behind a specific condition. For many longtime players, that design is familiar enough: developers leave jokes in the code, hide special images, or tie easter eggs to specific dates as a kind of wink to the audience. But once an easter egg carries a clear cultural symbol, it rarely stays at the level of a harmless detail.

The community response has split along a few obvious lines. One group is focused on consistency: if the team added it, why remove it in 1.06? Another is more concerned with boundaries, arguing that hidden insertion of this kind inevitably invites extra interpretation. A third group is taking the practical view, caring less about position than whether the developers will explain any of it. So far, there has been no public response on the hidden code, the easter egg setup, or the decision to remove it. As a result, the discussion keeps circling back to speculation and second-order readings, and the heat has not really dropped.

Viewed through the usual lens of games coverage, this feels a lot like a side quest in an RPG: the trigger condition is obscure, the reward does not affect the main path, but it exposes one of the world’s most contested corners. The real issue for Slay the Spire 2 is no longer whether the rainbow menu ever existed. Players have already pieced together the code, the testing, and the post-patch removal step by step. The question now is whether the developers are willing to step in and give that side quest an ending.

For players still undecided on Slay the Spire 2, the sensible approach is to separate this controversy from the game’s overall quality. Based on the public information available now, this is a community dispute triggered by a hidden easter egg and its removal; there is no evidence that it directly changes the core gameplay or the game’s purchase value. If you were already interested primarily in card-building and the tower-climbing loop, it makes sense to keep watching future updates and any official response rather than rush to a conclusion over an unexplained menu secret. On the other hand, if you care strongly about how a studio handles communication with its community, this is absolutely an issue worth tracking, because silence itself becomes part of how players judge a developer.