Describe the bug
It seems to be the case where the first arena (index 0) passMark is being skipped or not being set correctly when a new configuration is called from unity.
To Reproduce
Steps to reproduce the behavior:
Set passMark to any value for arena index 0
Run unity by pressing play
Observe the debug (already in the code in the branch)
You will notice that whatever the passMark you set in the yaml file it will be displayed as 0 in unity debug logs. This is only the case for arena == 0.
Expected behavior
As for all other arenas defined in the yaml file, the passMark should be defined and correctly set individually and must correspond to the expected values in unity. i.e. arena = 0, passMark = 50 / expected value for passMark in unity debugs = 50.
I suspect this is related to the first arena being skipped but I can't find a connection with training mode and manual mode passMark definition.
Screenshots
n/a
Desktop (please complete the following information):
Describe the bug It seems to be the case where the first arena (index 0) passMark is being skipped or not being set correctly when a new configuration is called from unity.
To Reproduce Steps to reproduce the behavior:
Expected behavior As for all other arenas defined in the yaml file, the passMark should be defined and correctly set individually and must correspond to the expected values in unity. i.e. arena = 0, passMark = 50 / expected value for passMark in unity debugs = 50.
I suspect this is related to the first arena being skipped but I can't find a connection with training mode and manual mode passMark definition.
Screenshots n/a
Desktop (please complete the following information):
Additional context n/a