Currently Command requests are implemented with a retry count, and when the PlayerComms have been prompted too many times the Battle just provides no Commands and continues. Like in #11 Command validity is domain-specific, and providing no Commands is unacceptable for some domains in some circumstances. More control needs to be afforded to mitigate this. Consider:
In some domains and situations failure to provide a Command is a logical failure that cannot be recovered from
Some domains will prefer to model a failure to provide commands as a timeout rather than a retry count
Currently Command requests are implemented with a retry count, and when the PlayerComms have been prompted too many times the Battle just provides no Commands and continues. Like in #11 Command validity is domain-specific, and providing no Commands is unacceptable for some domains in some circumstances. More control needs to be afforded to mitigate this. Consider:
In some domains and situations failure to provide a Command is a logical failure that cannot be recovered from Some domains will prefer to model a failure to provide commands as a timeout rather than a retry count