Decide debug overlay layout and content #151
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Question
Given the available drawing primitives (from the debug drawing API research), what should the debug overlay show and how should it be laid out on the battlefield?
Candidates:
Which of these are essential for the proof-of-concept, and what's the visual layout?
Parent map: #147
Blocked by: #148
Resolution
Elements to display:
Layout: Mixed.
Error logging: Per-evaluation to stdout:
tick=N error=12.3° reward=0.075. One line per wait-then-evaluate cycle. No on-screen error display — stdout is sufficient.