Enumerate cards simplified/info management

[NBKelly]

• I added an enumerate-cards fn which is cleaner than (enumerate-str (map :title/get-title ...))`, and supports sorting where appropriate
• I updated most uses of enumerate-str throughout the game to use this
• I made it so that most of the time, the enumerated cards are sorted where they should be
  • This means for a lot of cards, you will no longer receive them in prompt-click-order (ie gachapon), but sorted order
  • Reveals, sequences of cards from hand/discard, and a few others will be in sorted order to not reveal draw-order where they shouldn't
  • Some stuff will just imperceptibly become easier to parse
• Harvest now discards instead of trashes cards
• I confirmed it does not trigger strike/steelskin, but does trigger magdalene

[NoahTheDuke]

Should we default to sorted?

[NBKelly]

I think it could be either, but:

• The default behaviour (unsorted) means if you forget the key, the info is slightly harder to parse
• The default being sorted means if you forget the key, you leak info
  So I think this is safer.

[NoahTheDuke]

How does sorted leak info?

[NBKelly]

Oh whoops, I definitely didn't think that through correctly. https://proton.me/mail/home

…

-------- Original Message --------

On Wednesday, 12/10/25 at 12:14 Noah Bogart ***@***.***> wrote: @NoahTheDuke commented on this pull request. --------------------------------------------------------------- In [src/clj/game/utils.clj](#8458 (comment)): > @@ -123,6 +123,14 @@ (str/join (str " " sep " ") strings) (str (apply str (interpose ", " (butlast strings))) (str ", " sep " ") (last strings))))) +(defn enumerate-cards + "Enumerates a collection of cards, optionally in sorted order" + ([cards] (enumerate-cards cards nil)) How does sorted leak info? — Reply to this email directly, [view it on GitHub](#8458 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ACFMQTNZ5N3IOUVZCUWVPZD4A5JTVAVCNFSM6AAAAACORP4WE2VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZTKNRQGEYDMOBRGQ). You are receiving this because you modified the open/close state.Message ID: ***@***.***>