Size glitch bands to reliably show 2-3 scanlines each

Heights were down to 4-7px after the last shortening pass, which (given
scanlines repeat every 4px) could land entirely between two scanline
rows and show none at all, depending on exact alignment. Bumped back up
to 10-13px, which reliably shows 2-3 scanlines regardless of phase.
This commit is contained in:
poprhythm committed 2026-10-08 18:42:34 -04:00
1 parent bdd5993ed1
commit 5f9bc11e47
1 file changed
+13 -8
+13 -8
View File
@@ -368,14 +368,19 @@ GLITCH_STATES_PER_CYCLE = 4
# height) -- see the note above GLITCH_HOLD_TICKS for why that's the only # height) -- see the note above GLITCH_HOLD_TICKS for why that's the only
# part grounded in anything observed rather than invented. # part grounded in anything observed rather than invented.
GLITCH_STATE_POOL = [ GLITCH_STATE_POOL = [
(3, 6, -2, 150.0, 19, 5, 2, -60.0), # Scanlines (see _glitch_scanlines below) repeat every 4px, so each
(2, 5, 2, 150.0, 20, 6, -3, -60.0), # band's height needs to be at least ~9-13px to reliably show 2-3 of
(5, 4, -3, 150.0, 17, 7, 1, -60.0), # them, regardless of the band's exact vertical alignment against the
(1, 7, 1, 150.0, 21, 4, -2, -60.0), # scanline grid -- much shorter and a band can land entirely between
(6, 4, 1, 150.0, 14, 6, 3, -60.0), # two scanline rows and show none at all.
(0, 5, 3, 150.0, 24, 4, -1, -60.0), (3, 12, -2, 150.0, 19, 11, 2, -60.0),
(4, 4, -1, 150.0, 12, 7, 2, -60.0), (2, 11, 2, 150.0, 20, 12, -3, -60.0),
(2, 6, -3, 150.0, 22, 4, 1, -60.0), (5, 10, -3, 150.0, 17, 13, 1, -60.0),
(1, 13, 1, 150.0, 21, 10, -2, -60.0),
(6, 10, 1, 150.0, 14, 12, 3, -60.0),
(0, 11, 3, 150.0, 20, 10, -1, -60.0),
(4, 10, -1, 150.0, 12, 13, 2, -60.0),
(2, 12, -3, 150.0, 22, 10, 1, -60.0),
] ]
# render.Sequence doesn't loop on its own (see _glitch_scanlines below), so # render.Sequence doesn't loop on its own (see _glitch_scanlines below), so
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.