You were correct in identifying the problem. The range functions for the Pawns did not take into account the value of fps. However, replacing 2 with fps would not allow for first Pawn moves that are shorter than the maximum possible distance. For example, if fps were set to 3, this would include 3-space moves, but it would not include 2-space moves. This is what I ended up with:
def White_Pawn-Range mergeall where #ori -1 1 where #ori 1 1 filter lambda (onboard #1) aggregate lambda (where #ori 0 #0) range 1 var fps =ori;
def Black_Pawn-Range mergeall where #ori -1 -1 where #ori 1 -1 filter lambda (onboard #1) aggregate lambda (where #ori 0 neg #0) range 1 var fps =ori;
These use aggregate to create an array of spaces a Pawn may advance forward to, and they use filter to weed out non-spaces that are out-of-range. They use a named parameter in order to use its value in the lambda function used by aggregate.
I have since modified the functions above to use the filter on all results:
def White_Pawn-Range filter lambda (onboard #1) mergeall where #ori -1 1 where #ori 1 1 aggregate lambda (where #ori 0 #0) range 1 var fps =ori;
def Black_Pawn-Range filter lambda (onboard #1) mergeall where #ori -1 -1 where #ori 1 -1 aggregate lambda (where #ori 0 neg #0) range 1 var fps =ori;
Finally, I replaced aggregate with an expanded version of the values operator. With a lambda function and an array, it will work just like filter except that it returns a sequential array of each value calculated by the lambda function. Unlike aggregate, it will include values of zero, because it does no filtering on the results it calculates. As it did before, it will return the values of an array if that is what's passed to it. If it does not get a lambda function or an array, it will return the rest of the arguments following it as a single array.
def White_Pawn-Range filter lambda (onboard #1) mergeall where #ori -1 1 where #ori 1 1 every lambda (where #ori 0 #1) range 1 var fps =ori;
def Black_Pawn-Range filter lambda (onboard #1) mergeall where #ori -1 -1 where #ori 1 -1 every lambda (where #ori 0 neg #1) range 1 var fps =ori;
You were correct in identifying the problem. The range functions for the Pawns did not take into account the value of fps. However, replacing 2 with fps would not allow for first Pawn moves that are shorter than the maximum possible distance. For example, if fps were set to 3, this would include 3-space moves, but it would not include 2-space moves. This is what I ended up with:
These use aggregate to create an array of spaces a Pawn may advance forward to, and they use filter to weed out non-spaces that are out-of-range. They use a named parameter in order to use its value in the lambda function used by aggregate.
I have since modified the functions above to use the filter on all results:
Finally, I replaced aggregate with an expanded version of the values operator. With a lambda function and an array, it will work just like filter except that it returns a sequential array of each value calculated by the lambda function. Unlike aggregate, it will include values of zero, because it does no filtering on the results it calculates. As it did before, it will return the values of an array if that is what's passed to it. If it does not get a lambda function or an array, it will return the rest of the arguments following it as a single array.