Others attempted to build from scratch or port it without the original developer's involvement. I worked directly with Michael and built a bridge layer into his existing codebase rather than rewriting it.
I am working with Michael to remaster it. He transferred the domain name to me and I just redid the website. I'm not sure when the last time he updated Roninsoft website, but he has "retired" from working on WSR, although has been a huge help with the remaster. https://www.roninsoft.com/#:~:text=!!!%20Check%20out%20WallS...
I built an FFI via event dispatching and shared memory pointers/matching structs. Imported the C++ UI layer as a DLL via Win32 LoadLibrary. The PB shares a big array for storing global pointers allowing them to read/write each other's memory. The C++ has an event queue and has DLL functions the PB can call to peek/pop the next event. It actually isn't that complicated, just took me forever to come up with the idea.
As for languages, PB, C++, and JavaScript (Electron/Preact). I chose a no-build UI framework so that it could be modded by players without installing any build tools, just edit the text files in the game folder, and it has been a very good decision.
If I can't get a response from a publisher here soon, I will be setting an Early Access release date of 1-2 months from now to give me some time to build up more wishlists before I pull the trigger.
Yes, it parses based on the from email. The short answer is that it doesn't protect against email spoofing. I do have some filtering set up, but it hasn't been effective in my testing.
However, you do receive a confirmation email after every new post. So if someone spoofed your email to make a post, you would get a notification email about that post. In the notification, you'd see what had been posted and could easily delete it. (Note that the email address associated with an account isn't made public anywhere, so someone would need to have doxxed you in this scenario.)
Of course, it would be pretty easy for a determined attacker to set up a mailbomb that flooded someone's page with hundreds of spoofed posts. At that point I would have to disable email posting for that account to stop the attack.
reply