This website requires JavaScript.
Explore
Help
Sign In
ReaperOfVeriod
0 Followers
·
0 Following
Joined on
2026-07-03
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.
User to block:
Optional note:
The note is not visible to the blocked user.
Cancel
Block
Repositories
9
Projects
Packages
Public Activity
Starred Repositories
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-14 01:10:25 +00:00
39462d2cf9
Correct: overlay.bin is the seven-section program, not the .lit section
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-14 01:06:37 +00:00
4ca0308499
SBlk body head: the DAW size, stored twice
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-14 01:04:50 +00:00
ec433e3341
Correct my own "VIF packets" reading: the split is real, the identification is not
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-14 00:56:59 +00:00
4ab30e1f4d
Retract the tie texcoord field: a dominant-value artifact, one level down
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-14 00:52:12 +00:00
1e90c7de6d
Verify the Phase 2 gate, and give every blocked item an unblock condition
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-14 00:49:50 +00:00
67ce068c7f
Tie vertex regions are two encodings, not one; mark Phase 3's port done
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-14 00:37:41 +00:00
a94704de18
port Phase 3: overlay masking + code-identity + relocation
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-14 00:20:33 +00:00
8030dbf006
close: tie LOD distance ordering exceptions - 80/1864 classes have mid=8192 far=8190
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-14 00:05:40 +00:00
e5cd3df40e
Retract the tie vertex position claim; the stride is not 16
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-13 16:07:06 +00:00
855aadf523
Record the tie terminator defect in the format doc, plus two failed fixes
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-13 15:40:32 +00:00
572cd1898d
Record a defect packet slicing found: the tie block terminator is early
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-13 14:48:52 +00:00
1cfe744501
Settle the tie packet length, and correct the retraction that hid it
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-13 11:22:51 +00:00
4abce518e5
Decode the overlay's load base, from its own profiler table
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-13 06:59:42 +00:00
55ea619b4c
Decode the tie class header's +0x0c word: three LOD record counts
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-13 06:20:39 +00:00
f1f0b517a5
Pin the extracted tree, which every disc test reads and nothing verified
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-13 06:18:21 +00:00
8ccc3ddda4
Retract the uniformity claim everywhere it still stood, including the API docs
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-13 06:11:36 +00:00
2d3880b624
The class-ID retraction goes further: the claim was wrong before the fix
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-13 06:04:09 +00:00
d159195510
General guard for the over-read class, and the audit showing it was unique
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-13 06:02:32 +00:00
92aa0fe49f
Audit what the record-boundary fix contaminated: one retraction, one survivor
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-13 05:59:24 +00:00
4fab4d0359
Fix the record boundaries after all, and retract a claim built on the bug
Previous
9
Next
