i played and lost quite a lot (and got the HoS glitch on a run i thought would have won) but just won with a poison + poison ivy + healing/regenerating build. i was lucky the last boss was the joker because the manager would have made my symbols useless after one use, then cleansed the poison and made my whole run useless like he does to a lot of builds
the best moment i had was in another run where i had the automon, the generic poison symbol (cactus?), and lots of shields versus the chieftain and it was a drawn out fight to see who would out damage the other. i lost
OAB seems uniquely like the kind of game where you can lean into that sort of inactive, automatic gameplay and balance the fights around setting up a scaling build then letting it run to see if it outpaces the opponent. as i understand, fights in the game are designed to punish the player for staying in fights too long, but after that experience i think that might be the opposite of how fights should go. either way, i still really think that timing the slot machine is only a detriment to the game
i still feel that playing optimally means having foreknowledge of how enemies fight and whether you should fight them or not, which often means just avoiding fights altogether and walking around the board to collect health, cash, and shop, which is lame
in recent builds it seems like every color is more capable of doing nearly every thing, i notice that greens now can add block/retaliate when healing. in a way this makes the "why shouldn't i just use one color" problem worse, meanwhile if i were on a build that was built around retaliate i probably wouldn't be able to build into the kiwi (or whichever green symbol has it) because my whole board would probably be a different color
stolen wallet is a cool item. i'm not sure if i like the reversion to the shop sponge's reusability
in DD56 i purchased two discount artifacts, then the shop sponge's cost became a float with two decimal points. purchasing the sponge then turned my held money into a float with two decimal points. i'm unlikely to encounter the artifacts again to test this on the current version so i may as well report it now