![slay the spire cultist headpiece slay the spire cultist headpiece](https://i.ytimg.com/vi/DFiis3Y2u80/maxresdefault.jpg)
Each relic is available from each source with the exception of Shovel from Digging (since you already must have a shover to take the "Dig" option). TL DR: there's ways around the problem of "upon pickup" "normal" relics are usually quite safe so people don't bother checking them to see if they'd be a detriment I think the problem is just between these 2 relics (ded stick and ninja) and what build you're playing, so maybe an alternative would be to just change these relics.Filter: Common Uncommon Rare Boss Shop Event RelicĪll values in this table except "From Shop" only consider relics obtained from random sources.Įlite, Chest, Dig - number of times each relic was obtained from one of these sources. I think this problem only occurs with these 2 relics and how they interact with each other and with what run you're doing, so maybe they could just alter where these relics appear or something? And because time maze is active, you can't just play them to see what stuff you're going to get, so there's no way around the problem. However, when you get shot in the leg in your endless silent OTK loop run because you picked up ninja scroll and dead branch, so you're stuck with 3 brick-shivs that you can transform into other bricks, you really begin to wish you could remove certain relics. The problem is, most of the time I pick up relics from normal chests or elites without looking properly at them, getting me stuff like dead branch when I don't play any exhaust cards whatsoever, simply because pretty much all of these "normal" relics don't have any negative effects, unlike boss relics. Also, being able to re-use certain relics like the winged boots on an endless run would be super helpful. As for harmful ones, either they could fall into the unremovable catagory, or just make removing relics a complicated pain so you couldn't just spam remove everything you dont like. I think maybe they could make cetain relics un-removeable? Or an internal counter to stop you from getting them again.
![slay the spire cultist headpiece slay the spire cultist headpiece](https://www.chip.de/ii/1/2/3/1/6/8/1/8/0/152c89c67e501438.jpg)
#Slay the spire cultist headpiece free
So you would get free money essentially, as the removal of those relics don't do anything harmful to you. Upon removal, the granted things won't be removed. Originally posted by Berik Xardas:1) There are many "Upon puckup." relics (the HP fruits, Potion Belt, Whetstone etc etc), as well al some relics which power can be used up (Omamori, Matryoshka, Winged Boots). Especially when recieving relics should always be a positive experience.Īccidently picked up the dead branch, which lead to all my shivs/adrenalines filling my hand/deck with random cards every time I played them. Some possible solutions could be a UI element allowing you to remove or disable relics between fights, or perhaps you could pay money to have a relic removed at the store (or even better yet, be able to sell them, even if for a small amount of gold).Īgain, perhaps it's better that the player just learns how everything in the game interacts, but it's rough making a build breaking decision without realizing it and having no way to undo.
![slay the spire cultist headpiece slay the spire cultist headpiece](https://cdn.mos.cms.futurecdn.net/qCHTsTqMg9TVZoMW7zPYWP.jpg)
Although I am totally fine taking the blame, it seems kind of odd that there is no way to disable or remove relics that you don't want, or that beak your build (especially when some relics can be added to your inventory whether you want them or not).
![slay the spire cultist headpiece slay the spire cultist headpiece](https://4.bp.blogspot.com/-nyJ0oiJT_f8/XEil9ScQUXI/AAAAAAAAZYw/Ha80v1_E7oMO8aUcIZBhbo1QYs3jzEUrACLcBGAs/s1600/slay-the-spire-01.jpg)
I'm decently new to the game, so I just didn't realize the implications of taking the relic (details below). During a recent endless run, I made a pretty poor decision with accepting a relic that I didn't think would apply to my build (Silent Shiv), and it wrecked the run.