@ReC98Project
rec98.nmlgc.net
Joined February 2015
  • Tweets2.6K
  • Following26
  • Followers731
ReC98 will end after the next delivery. I don't have it in me to compete with vibecoders, especially when y'all cheer them on for instantly delivering what you've wanted all along. And if you aren't cheering yet, you soon will; they're only getting better and more numerous.
15
17
10
77
11,325
github.com/nmlgc/rec98.nmlgc… [💰] Confirm T0440 A final €400 from Ember2528 for the announced and AI-unrelated farewell gift: Kioh Gyoku SC-88Pro BGM packs, releasing my loop builder, and better loop detection to support a mystery goal. Thank you for all the years of support. 🙏

[💰] Confirm T0440 · nmlgc/rec98.nmlgc.net@fcbc9de

A final €400 from Ember2528 for the announced and AI-unrelated farewell gift: Kioh Gyoku SC-88Pro BGM packs, releasing my loop builder, and better loop detection to support a mystery goal. Thank yo...

github.com
2
1
10
472
Second round of refunds has also been sent out.
122
On October 5, 2019, I launched the ReC98 crowdfunding website. Today, 7 years later, there really is no more incredible journey to be had. So here's is my final feature and retirement announcement. No matter how this is received, I have already won. 😮‍💨 rec98.nmlgc.net/blog/2026-10…
Screenshot of the output of the new Shuusou Gyoku command-line replay simulation tool, showing the end result of an full Extra Stage 4M10B Homing Shot replay, together with the surprisingly short amount of 179.3 ms it took to run through all 26212 frames of this replay. This translates to a validation frame rate of 179.3 ms. The caption reads: "As usual, the performance corresponds to the 32-bit Windows build running on my aging Intel Core i5-8400T. No one else gave me performance numbers."

ALT Screenshot of the output of the new Shuusou Gyoku command-line replay simulation tool, showing the end result of an full Extra Stage 4M10B Homing Shot replay, together with the surprisingly short amount of 179.3 ms it took to run through all 26212 frames of this replay. This translates to a validation frame rate of 179.3 ms. The caption reads: "As usual, the performance corresponds to the 32-bit Windows build running on my aging Intel Core i5-8400T. No one else gave me performance numbers."

Screenshot of a table that visualizes the growth in complexity of the ReC98 blog posts from 2020 to 2026, comparing total and average text bytes and asset count. Taken from the ReC98 2026-10-05 blog post. The caption reads: "Excluding the three policy-bugfix posts and the order advice post. Complexity is calculated as the geometric mean of the average text bytes increase and the average asset count increase since 2020, i.e., √((Average text bytes / 4,234) × (Average asset count / 0.9))."

ALT Screenshot of a table that visualizes the growth in complexity of the ReC98 blog posts from 2020 to 2026, comparing total and average text bytes and asset count. Taken from the ReC98 2026-10-05 blog post. The caption reads: "Excluding the three policy-bugfix posts and the order advice post. Complexity is calculated as the geometric mean of the average text bytes increase and the average asset count increase since 2020, i.e., √((Average text bytes / 4,234) × (Average asset count / 0.9))."

2
2
1
27
1,874
@cooljwilins This is the method you'll be looking for: github.com/nmlgc/ssg/blob/dc…

ssg/ssg/internal/SSG.hpp at dc63b340a7c184b456850972b89324d9a8f13c4f · nmlgc/ssg

秋霜玉 / Shuusou Gyoku. Contribute to nmlgc/ssg development by creating an account on GitHub.

github.com
1
218
Funded by Ember2528, [Anonymous], Root, WishMakers, and Arandui. May the wrong bridges stay in flames forever.
2
352
You could use this code to procedurally generate optimal Shuusou Gyoku runs from your favorite programming language via old-school machine learning or something. In reality, nobody cares, and you'll all just be here for one thing. >18,700 words coming to you in a few hours.
1. Point items with negative values? 2. Defining the scope of "game logic" • The unexpectedly big scope of RNG 3. Researching locale bloat in MSVC's sprintf() 4. Safely bypassing MSVC's C++ exception handling 5. Completing the separation of game logic • Implementation details • Changing debug invincibility 6. The birth of a shared ReC98 source port engine 7. A replay validation CLI • Validation performance 8. Future work 9. Retirement announcement • Epilogue

ALT 1. Point items with negative values? 2. Defining the scope of "game logic" • The unexpectedly big scope of RNG 3. Researching locale bloat in MSVC's sprintf() 4. Safely bypassing MSVC's C++ exception handling 5. Completing the separation of game logic • Implementation details • Changing debug invincibility 6. The birth of a shared ReC98 source port engine 7. A replay validation CLI • Validation performance 8. Future work 9. Retirement announcement • Epilogue

12
362
Finished the retirement part of the next blog post. >7,700 words with the full timeline, nuance, and plenty of burned bridges that hopefully close off any way back into this hellhole I should have left in 2011. The vibecoders will soon appear like the sanest actors in the room.
2
17
730
Now, back to the QA work that was unfortunately interrupted 6 weeks ago…
5
383
OK, received tons of words, but zero serious offers to continue working in this scene in any capacity, matching the trend started in April. Hence, this business model has run its course, I made the right call, and the decision is final. First round of refunds has been sent out.
1
9
987
(Second round merely consists of the contributions that could still go into the final 6-push delivery, and will be sent out once that one goes live.) Please respect your and my time and refrain from any further attempts at persuading me. Thank you.
1
4
641
Next release, then PC-98 text RAM JIS trail word rendering (it's been in my drafts for almost 5 years), and then it's over. All other pending contributions will be refunded.
1
14
2,650
Many thanks to this month's subscribers! RL consumed lots of time this month. Regaining focus has been tough with the final steps being as difficult as ever. Wondering how ReC98 can possibly survive after all the forks (many of them vibe-coded) I've seen in this month alone.
Active ReC98 subscriptions for June 2026: • €125 from [Anonymous] towards anything (including tooling) • €50 from Ember2528 towards better replays for Shuusou Gyoku, followed by a long-term plan to first decompile TH03, adding replays, porting it to modern systems, and then implementing netplay (although we're also going for a more short-term option of having netplay on PC-98) • €35 from [Anonymous] towards TH03 RE • €10 from Root towards porting SDL to Windows 98 to get Shuusou Gyoku running there again

ALT Active ReC98 subscriptions for June 2026: • €125 from [Anonymous] towards anything (including tooling) • €50 from Ember2528 towards better replays for Shuusou Gyoku, followed by a long-term plan to first decompile TH03, adding replays, porting it to modern systems, and then implementing netplay (although we're also going for a more short-term option of having netplay on PC-98) • €35 from [Anonymous] towards TH03 RE • €10 from Root towards porting SDL to Windows 98 to get Shuusou Gyoku running there again

13
1,358
140-175 ms for simulating the full 7 minutes of Shuusou Gyoku's Extra Stage on the command line. On an 8-year-old Core i5. Single-threaded. With MSVC's horrid codegen and several untapped optimization opportunities. And that's the heaviest case. Regular stages are much faster.
Output of the upcoming Shuusou Gyoku command-line replay simulation tool, showing the end result of two Extra Stage and one Lunatic Stage 4 replay, together with the surprisingly short amount of time it took to gather these results – 141.3 ms for a Wide Shot Extra Stage run, 173.3 ms for a Homing Missile Extra Stage run, and 44.8 ms for a Laser run of Stage 4 on Lunatic difficulty, translating to validation frame rates of 191894, 151244 and 242082 FPS, respectively.

ALT Output of the upcoming Shuusou Gyoku command-line replay simulation tool, showing the end result of two Extra Stage and one Lunatic Stage 4 replay, together with the surprisingly short amount of time it took to gather these results – 141.3 ms for a Wide Shot Extra Stage run, 173.3 ms for a Homing Missile Extra Stage run, and 44.8 ms for a Laser run of Stage 4 on Lunatic difficulty, translating to validation frame rates of 191894, 151244 and 242082 FPS, respectively.

1
7
939
Of course, this also means instant detection of desyncs. (Though only via a Game Over occurring before the game processed all inputs, since that's all data we have in the old format. The new one will record more events that could pinpoint the cause of a desync more closely.)
Output of the upcoming Shuusou Gyoku command-line replay simulation tool, showing a desyncing replay that ends 77.1% into the recorded replay data with a Game Over, after just 24.6 ms of simulation time.

ALT Output of the upcoming Shuusou Gyoku command-line replay simulation tool, showing a desyncing replay that ends 77.1% into the recorded replay data with a Game Over, after just 24.6 ms of simulation time.

2
553
Finally, Shuusou Gyoku's game logic, isolated in a reusable, freestanding DLL. No global state. No Win32 API dependencies besides GetProcessHeap(), HeapAlloc(), and HeapFree(). No instructions newer than i586. Still simulates blazingly fast. (Have fun guessing how fast exactly!)
Screenshot of the Windows 11 Properties dialog displaying the new Shuusou Gyoku game logic DLL, with a size of 73,216 bytes.

ALT Screenshot of the Windows 11 Properties dialog displaying the new Shuusou Gyoku game logic DLL, with a size of 73,216 bytes.

Screenshot of Dependency Walker running on Windows 98 displaying the new Shuusou Gyoku game logic DLL and showing off its minimal imports of GetProcessHeap(), HeapAlloc(), and HeapFree().

ALT Screenshot of Dependency Walker running on Windows 98 displaying the new Shuusou Gyoku game logic DLL and showing off its minimal imports of GetProcessHeap(), HeapAlloc(), and HeapFree().

24
1,137
ReC98 retweeted
ReC98@ReC98ProjectJun 13
(Yes, I've heard the news and will go right back to work! Just let me finish this really cool thing for Shuusou Gyoku I've been working on for the past few months, and then I'm going to spend an extended amount of time with the main business. OK?)
1
5
686
sizeof(C_SSG) is 403,280 bytes on 32-bit systems, and 405,664 bytes on 64-bit systems.
1
6
512
(Yes, I've heard the news and will go right back to work! Just let me finish this really cool thing for Shuusou Gyoku I've been working on for the past few months, and then I'm going to spend an extended amount of time with the main business. OK?)
1
5
686
Many thanks to this month's subscribers! The splitting process has escalated to not only cover Shuusou Gyoku's logic, but also my SDL-based engine, laying the groundwork for future modern-system builds. Only missing the CLI now, and of course the blog post. Mid-June, maybe?
Active ReC98 subscriptions for May 2026: • €125 from [Anonymous] towards anything (including tooling) • €50 from Ember2528 towards better replays for Shuusou Gyoku, followed by a long-term plan to first decompile TH03, adding replays, porting it to modern systems, and then implementing netplay (although we're also going for a more short-term option of having netplay on PC-98) • €35 from [Anonymous] towards TH03 RE • €10 from Root towards porting SDL to Windows 98 to get Shuusou Gyoku running there again

ALT Active ReC98 subscriptions for May 2026: • €125 from [Anonymous] towards anything (including tooling) • €50 from Ember2528 towards better replays for Shuusou Gyoku, followed by a long-term plan to first decompile TH03, adding replays, porting it to modern systems, and then implementing netplay (although we're also going for a more short-term option of having netplay on PC-98) • €35 from [Anonymous] towards TH03 RE • €10 from Root towards porting SDL to Windows 98 to get Shuusou Gyoku running there again

6
466
Load more