Feels a bit strange that we return "no_error" if there is an error. Should we not add a "unknown_error" to the Player error api? This seems likely to be the reason why this failed in the first place?
« Back to merge proposal
Feels a bit strange that we return "no_error" if there is an error. Should we not add a "unknown_error" to the Player error api?
This seems likely to be the reason why this failed in the first place?