From Round 22 usability feedback (minecraft tester, self-scored 4/10, 5 round trips).
Arming --mode trace --max-history 100 on a line that runs every frame retains only ~1.6s of history at 60fps, so the frame of interest (a jump input) was already evicted by the time pause-point-status was read. The tester had to abandon trace mode and fall back to two single-shot pause points.
Requested improvements (either would solve it):
- Conditional capture at arm time (e.g.
--hit-when verticalVelocity>0) so an every-frame line can be captured only on the interesting frame.
- A history retention policy switch (e.g.
--history-keep first|last) so the frames right after the input survive.
Also: the help has no note that trace on an every-frame line overflows within a single CLI round trip; the tester only learned this by failing once.
From Round 22 usability feedback (minecraft tester, self-scored 4/10, 5 round trips).
Arming
--mode trace --max-history 100on a line that runs every frame retains only ~1.6s of history at 60fps, so the frame of interest (a jump input) was already evicted by the timepause-point-statuswas read. The tester had to abandon trace mode and fall back to two single-shot pause points.Requested improvements (either would solve it):
--hit-when verticalVelocity>0) so an every-frame line can be captured only on the interesting frame.--history-keep first|last) so the frames right after the input survive.Also: the help has no note that trace on an every-frame line overflows within a single CLI round trip; the tester only learned this by failing once.