You should beware that there is no general formula for the M-nnn nonsense. It is not part of the [%eval] format, but a situation-dependent error in it. It arises from having defined a wrong mating score in the WB2UCI adapter, i.e. with a value smaller than what the engine is actually using. So it is not even reproducible with the same engine; when you run Crafty in another situation (with other WB2UCI settings) the conversion to real mating scores would have to be completely different.
As to the score POV, it might be worth noting that last time I looked, Crafty was non-compliant in this respect: unlike other engines, it reports scores from white POV. WinBoard has a work-around option first/secondScoreAbs to corract that, but I am not sure WB2UCI can do that too, and even if it can, people producing the %eval PGNs might not have set it properly. So this could be a Crafty-specific problem.
tpetzke wrote:
I actually replace it into { +0.50/18 0.14s }
This is the format cutechess-cli outputs, I think Arena does it too in this form. And my future GUI will also write it in this form. I want to get rid of those %tag and not just replace it with something else.
.
WinBoard/XBoard uses a format like that too, although I am not sure about the padding with spaces, and the 's' for seconds. It seems to me that, when embedded between moves, the spaces would actually decrease readability. The use of a unit on the time seems redundant, and just wastes space. a plain real or integer number there could always be taken to mean seconds, as for minutes the notation min:sec could be used. There is also no unit (Pawn or cP) on the score...