From Round 22 usability feedback (minecraft tester, self-scored 4/10, 3 round trips).
When a --trigger click lands on the same timing as a pause-point hit, the response says:
"Button 'Left' press was already delivered to the game before the pause; Unity CLI Loop released it from bookkeeping, so the game may have registered the press."
"may have registered" leaves the world-state change indeterminate. In this session the click did mine a block, and the tester only discovered it later by back-tracking an unexpected Air coordinate (3 extra commands).
Requested: return a definite DeliveredToGame: true/false (whether the game observed the input event that frame). If that is technically impossible, extend the guidance to say the world state may have changed and should be re-checked around pause-point-status.
From Round 22 usability feedback (minecraft tester, self-scored 4/10, 3 round trips).
When a
--triggerclick lands on the same timing as a pause-point hit, the response says:"may have registered" leaves the world-state change indeterminate. In this session the click did mine a block, and the tester only discovered it later by back-tracking an unexpected Air coordinate (3 extra commands).
Requested: return a definite
DeliveredToGame: true/false(whether the game observed the input event that frame). If that is technically impossible, extend the guidance to say the world state may have changed and should be re-checked aroundpause-point-status.