Yes, you are no doubt right, but I suspect the ‘proper solution’ will require a huge amount of work and break every module that uses $PlayerSide$ = blah in a propertyMatch. I guess we could add special code to the PropertyFilter…
Thanks for kicking around some possible solutions for this issue. Brent, your idea sounds like it could work. As you mentioned, I, too, would hate to see dozens of modules become “broken” as a result of a “fix” for this issue. I think at this point I’d like to stand back while you two experienced VASSAL developers toss around the possibilities, although I definitely will be watching with interest and will pop in if required.
I was just checking in to see if any more thought had been put into any of these issues since we last communicated. My apologies for my forwardness, but these particular issues are of great interest to me.
We’re still working on releasing 3.1.0-beta1, so, no, no progress has
been made directly on these. The tabs RFE I intend to work on for either
3.2 or 3.3.
Thank you for the update, Joel. I’d love, Love, LOVE to see RFE 893639 (allow a player to join more than one side) be added, but I know you fellows are very busy and I will gladly take whatever enhancements you can offer.
I was talking about this with Gregory on Friday. I think what’s needed
is the ability to specify sets of players everywhere that players can
be specified now. (That would make, e.g., pieces, which are owned by
a single player now, owned by a singleton set containing that player.)