09-25-2020, 10:23 AM
(09-25-2020, 07:56 AM)Eric Piette Wrote: I modified (sites Group) in one of the previous release to be generic for such cases with a condition thanks to the "if:" parameter but I did not updated the (count Group) in the same way for now.I don't think I understand. My issue is specifically with (sites Group) in this case. The "if:" parameter is great, but it only sets a restriction inside the context of a decision the ludeme makes automatically based on the "at:" parameter. If the site given in "at:" is occupied by one of my DoubleCounters it computes a group consisting of only sites occupied by my DoubleCounters. I can't force it to be more generic, so I can't make it compute a group consisting of my pieces, not specifically my DoubleCounters.
It would be great if the generic property that connects the sites in the group (in addition to adjacency) can be set in a paramenter. In that way I could compute a group of sites connected by a chain of adjacencies between sites with "some property" set by me. A group could then (if one sets this optional parameter) cut across sites occupied by different players. An example is a group of all sites connected by a chain of adjacencies between sites whose state is even. Is this the intended effect of "if:"?
Sorry for just throwing out wishes. I understand that you have a lot todo. And I really appreciate your work!