Just a thought: What if this could be done with i^pfmR? Would that confuse things too much?
I don't see the logic of that; considering that ^ in the captureMatrix means "cannot hop" combining it with p seems more confusing than helpful. And if there is to be a special XBetza modifier for friendly hopping, there should also be one for hopping only over enemy pieces. It is true that allowing non-alphanumeric caracters as modifiers solves the shortage-of-lower-case problem, but ^ seems a bad choice. I once did consider using p' and p" for friendly and enemy hopping, or using general 'limiters' in the form {...} behind modifiers to restrict their action to the enclosed piece types. But it seemed bad to have piece ids, which are very variant specific, appear in the XBetza notation, where capitals already mean something completely different. The capture matrix seems a much cleaner solution for all type-specific interactions. And color is just one aspect of type, so it can also be used to resolve the color-blindness of some of the XBetza modifiers.
I don't see the logic of that; considering that ^ in the captureMatrix means "cannot hop" combining it with p seems more confusing than helpful. And if there is to be a special XBetza modifier for friendly hopping, there should also be one for hopping only over enemy pieces. It is true that allowing non-alphanumeric caracters as modifiers solves the shortage-of-lower-case problem, but ^ seems a bad choice. I once did consider using p' and p" for friendly and enemy hopping, or using general 'limiters' in the form {...} behind modifiers to restrict their action to the enclosed piece types. But it seemed bad to have piece ids, which are very variant specific, appear in the XBetza notation, where capitals already mean something completely different. The capture matrix seems a much cleaner solution for all type-specific interactions. And color is just one aspect of type, so it can also be used to resolve the color-blindness of some of the XBetza modifiers.