So let’s say there is this really nicely done module. But it is a block game, and there is no place that one could “shuffle” their blocks without it being pretty trackable. The sides hands only accept cards, not blocks.
So I added a couple of sided private windows. Seems to work as easily as it should.
And I would like to put it out there, but is that ethical? I asked the module developer if there was a missing “tray” where I could do this, and he didn’t seem to really grasp my question? Anyway, it’s a pretty minor thing, but I think people might find it useful as I do. But don’t know if that is cool to do and how I don’t want to attribute my shoddy work as being the module designer’s job to maintain, etc.
I’ve been in this situation, so here is my advice:
If it is a high quality module that is being actively maintained, I would recommend asking the designer to fix it. I recommend NOT making a minor tweak to an actively maintained module unless the maintainer gives you the ok…
If they are unwilling to, make whatever change(s) you want, but don’t post it… Just share it w/ you friends to use in your games.
If you are making a LOT of updates that will have widespread appeal, you can “fork” into a unique version and post it. IF you do this, I HIGHLY recommend doing a lot of playtesting prior to posting a new version. Make sure you add notes on the module page regarding the change(s), maintainer, etc.
It’s easy to fix the problem you are talking about without making any module changes. Simply “hide” all the blocks, stack them, then move them around in the stack. I do this all the time w/ block games I play.
Are you certain about this? As far as VASSAL is concerned, there is no difference between a “card” and a “block” (or any other piece). It’s certainly possible to add checks to prevent the blocks from being moved to a Player Hand window (or rather, to instantly return them to their previous position if dropped there), but it requires some effort, so I have my doubts…
From what I can tell the only “hidden to the opponent side” in this module is the “hand” window. And there is certainly a place where you can mark what is allowed to go into that window, (cards and/or blocks), and the hand only accepts cards. Defer to your knowledge, but that wasn’t what I saw when I was mucking about with the window properties.
I just took a look at the module, and the designer did indeed put in the effort to send blocks straight back to their previous location if they are dropped in a Player Hand window. However, I see no reason why Korval’s #4 suggestion shouldn’t work; select the stack, use right-click menu to flip all pieces (or use Ctrl-F), double-click the stack to expand it, drag the individual pieces to reorder them, double-click again the compress the stack, click somewhere else to deselect the current piece, re-select the stack, right-click menu to flip pieces back over (or Ctrl-F again).
Note that if you skip the step of clicking somewhere else then re-selecting the stack, you will only flip the piece you last moved, not all of them.
I tried this with both sides and it worked fine.
Edit: I am slightly confused about how this will do any good, though, as the mouse-over stack viewer clearly shows the order the blocks are in for both sides.
I did see it. And your suggested fix would do it I think. Going back to the same position is the problem, as it seems to be trackable info in vassal log files, without a private hand to do the splitting/shuffling. Better that there are no movement trails. And I wasn’t really looking to make work for you. And didn’t name you because I hadn’t asked your permission to do so.
But even in our prior exchange on BGG, you said "I’d only play it on Yucata Which I have started doing. Lost my first game to an interface mistake on my part, and am now losing without any excuses…
And, I more just wanted to know what the established protocols were for such module mods. It has been very helpful in that regard.
Your original query brought to my attention that the position of a revealed block is subsequently trackable in the module via its position in a stack and I think we agree that the update would fix that.
Block movement reporting to the log file doesn’t have to an issue, since blocks are hidden during the Movement phase, in which case Mon and strength is not reported. Also, Location is not reported when a player reveals a block, only when moved which is not necessary during combat. The module’s suggested combat method is to expand the stacks involved, reveal blocks directly within the stack and press the “Hide Blocks” button at the end of the combat.
I was interested to hear from you and once I picked up on the issue you were raising, I wanted to address it.
I can’t recall saying that but I did say that my work on the module was partly “based in what I knew from yucata”. That said, it’s true that I played many more games on that platform than on Vassal.
In conclusion, I will release the update to prevent tracking of block positions within a stack. If you still see a need for extra windows or some other mods, then perhaps do them for your own use initially, based on that update. Of course, I’ll be interested to know how you get on.
Which I have started doing. Lost my first game to an interface mistake on my part, and am now losing without any excuses…