Posts

Newest Post: VoidShell Library: Destiny Notes

Good afternoon, readers. Oh yeah, this is going to be the first blog entry of 2026, so let us begin by talking about the VoidShell library's future. As many of you can guess, this library initially started as an ASM x86 program inside a ST file, which was loaded by the engine through a SuperNull exploit (The StateDef Overflow engine vulnerability was used as main vector back then), and despite you could expect, it was simpler than the current version. "Eikidankai" was the first name given to said library and early build versions were used on a few known characters (such as x00x00x or Void.Schmelze) to withstand most SuperNull enemies from the past decade. However, there was no real defense behind it, as it just seals most of the engine vulnerabilities while hooking some primary functions, causing their exploits to be effectively blocked but also rendering them unstable. They were eventually left as PoC characters while the Eikidankai program had to be reworked from scrat...
0

Eikidankai Development Log(1)

Eikidankai Development Log: Catching the WinMUGEN primary thread. The development of Eikidankai has been somewhat tedious to program, as when there is an interesting function to add into the coding, it mostly implies to modify the structure of all the code to implement it, or else I would not be able to perform that. That is why I am taking over 2 years or more to program that, well... One of the functions I had implemented some months ago was the ability to manipulate the primary thread of WinMUGEN, which in the previous versions of Eikidankai were not able to perform it. In this case, I used the SuspendThread function from an external thread to freeze the primary one. WinMUGEN before getting suspended by Eikidankai. Done!.. The suspend count has been increased by 1. That is all for now, have a nice day or night. Stay tuned for upcoming posts!
0