Thnks, I was coming to the same conclusions myself (the need for another work deck where I do the initial shuffle or the right click command to shuffle etc).
However, then I thought one could try to exploit the “DeckPosition” property, but that’s no go either. Note that the order of cards in a deck is known to the engine, with any reshuffle setting, as the “draw specific cards” command does show them in the actual order you put them in (in the module editor or by drag and drop during a test game). Therefore, I guess DeckPosition should be a well defined property even for cards in a “reshuffle always” deck.
So, one could hope that the deck GCK that issues “DOWN” with Matching Properties set to “DeckPosition=1” and “Fixed Number of Pieces = 1” (or, alternatively, “All Pieces”) should do the job.
However, DeckPosition=1 just never ever fires (fixed=1 or all setting).
I tried then DeckPosition=2 and it works… randomly… sometimes the card showing at the top goes to the bottom, sometimes nothing happens (this with fixed number of pieces set to 1, with “all pieces” setting sometimes one card is sent to the bottom, sometimes two cards and sometimes all three). And the order seems to be always preserved (as checked by “draw specific cards”)! Please, see example module attached (this done with 3.3.1).
I also tried DeckPosition=4 and it also fires in unpredictable ways. Note that there are only 3 cards in this test deck.
Bug with DeckPosition?
Issues with DeckPosition were already reported in previous threads:
https://forum.vassalengine.org/t/deckposition-bug/6671/1
https://forum.vassalengine.org/t/deckposition-does-not-seem-to-work-vassal-3-2-0-beta4/5455/1