258dd8561d
`entity_geometry` ran `cracks()` twice per frame: once for the block-entity pass that draws `render_breaking`, once for the overlay near the end of the same function. Each run walked `mining` and the `destroying` map, and formatted `block/destroy_stage_<n>` for every crack it found before looking that string up in the atlas. The list is computed once, at the top of the function, and the passes read it. The ten stage names are a const table, so a crack costs one lookup and no allocation. Nothing between the two passes touches `mining` or `destroying`, which are only read there, so the list the second pass used to rebuild was always identical to the first one. No behaviour change: the same ten sprite names, and a stage above 9 still finds no sprite and skips the crack. Co-Authored-By: Hermes Agent (Nous Research) <noreply@nousresearch.com>