Place magenta band 3-5px above cyan in every glitch state

GLITCH_STATE_POOL previously had independently-random top positions for
the two bands. Now top2 (hue -60.0, magenta) is always top1 (hue 150.0,
cyan) minus a 3-5px gap, so magenta consistently sits just above cyan
rather than their relative order/spacing varying per state.

Verified 0 black-corner hits across 265 frames, 260KB payload.
This commit is contained in:
poprhythm committed 2026-10-09 19:03:59 -04:00
1 parent 7156fa71ae
commit c950b9db17
1 file changed
+12 -8
+12 -8
View File
@@ -398,14 +398,18 @@ GLITCH_STATE_POOL = [
# scanlines within a given band (that required ~9-13px against
# _glitch_scanlines' 4px repeat), so a band can land entirely between
# two scanline rows; accepted, since the shorter height was the ask.
(3, 3, -2, 150.0, 18, 4, 2, -60.0),
(2, 4, 2, 150.0, 20, 3, -3, -60.0),
(5, 2, -3, 150.0, 16, 4, 1, -60.0),
(1, 4, 1, 150.0, 22, 2, -2, -60.0),
(6, 3, 1, 150.0, 14, 3, 3, -60.0),
(0, 2, 3, 150.0, 24, 4, -1, -60.0),
(4, 3, -1, 150.0, 19, 2, 1, -60.0),
(2, 4, -3, 150.0, 26, 3, 1, -60.0),
#
# hue2 (-60.0, magenta) is placed 3-5px *above* hue1 (150.0, cyan) in
# every entry (top2 = top1 - a 3-5px gap) -- a fixed relative offset
# rather than independently-random positions, per request.
(10, 3, -2, 150.0, 6, 4, 2, -60.0),
(14, 4, 2, 150.0, 11, 3, -3, -60.0),
(8, 2, -3, 150.0, 3, 4, 1, -60.0),
(20, 4, 1, 150.0, 16, 2, -2, -60.0),
(6, 3, -1, 150.0, 3, 3, 3, -60.0),
(24, 2, 3, 150.0, 19, 4, -1, -60.0),
(12, 3, -2, 150.0, 8, 2, 1, -60.0),
(18, 4, 1, 150.0, 15, 3, -3, -60.0),
]
# 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.