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 02:15:13 +00:00
0b660cb0ce
The extracted alpha rule disagreed with the renderer; the renderer was right
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-14 02:13:20 +00:00
31f4ba3f7c
GS alpha test and blend: all four rules the item names are now present
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-14 02:12:10 +00:00
81ec17857a
GC starts: the GS's own rules, as a module with tests
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-14 02:10:51 +00:00
3bc6c2d155
Phase 3 gate, second half: cross-check our masking against an independent hash
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-14 02:08:58 +00:00
56d8dee836
Close Phase 3's level table: 27 keys, and 21 is not one of them
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-14 02:03:55 +00:00
88bc9566f2
Narrow moby_anim: the class header has no pointer to anything external
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-14 01:56:52 +00:00
4776db199b
Attempt the moby_anim unblock: a location and a failure, not a result
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-14 01:54:32 +00:00
b3b4d47d97
Search for the tie vertex stride: 64 where one exists, none for 62%
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-14 01:49:33 +00:00
7b6de36958
Mark the two tie tests that still measure the retracted 16-byte layout
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-14 01:48:18 +00:00
412ef4707b
Withdraw the tie "not a joint index" claim: the measurement never settled it
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-14 01:47:17 +00:00
f182a4a0ac
Transcribe the 256-byte MobyInstance; oClass closes the instance-to-routine loop
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-14 01:42:44 +00:00
3785195ecd
The dispatch tables hold 4,737 behaviours, not 5,822 records
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-14 01:41:00 +00:00
18af702420
Read a moby handler: the chain works, with two caveats and a 110 discrepancy
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-14 01:38:47 +00:00
d611026f07
All three dispatch tables decode, and the check that matters is the remainder
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-14 01:36:04 +00:00
94819f4a79
oClass is a global id, not an index into the class table
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-14 01:34:37 +00:00
199ce33dd8
The moby class-id space is known: lvl.vtbl, and the old bound was simply wrong
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-14 01:25:33 +00:00
9f4f4acecb
The collision assert string is never referenced: the last route is closed
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-14 01:18:04 +00:00
66a96111d7
Kill the 48-byte loop lead: the function takes no pointer arguments
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-14 01:16:19 +00:00
2f5979e652
Update the decomp; read .text, and fix the disassembler that made it unreadable
ReaperOfVeriod
pushed to
main
at
ReaperOfVeriod/Going-Commando
2026-10-14 01:11:14 +00:00
508a03fa4a
The decomp names both collision functions; their addresses are not ours
Previous
8
Next
