starflight-reverse

Thanks to this project here: https://github.com/s-macke/starflight-reverse this has now become a piece of cake for the agent. The hard part has already been done. The question now is: how familiar is the agent with Forth?

Yes, my comment came across a bit harsh, and it’s fine to pick up a few negative karma points. But I keep seeing Forth posts every two weeks where everyone has just built yet another interpreter. Actually I did a few projects with Forth and I find it very cool: [0] https://github.com/s-macke/Forthly [1] https://github.com/s-macke/starflight-reverse [2] https://s-macke.github.io/concepts-of-programming-languages/...

Here is my approach to reverse-engineer a DOS game: Starflight [1]. Actually, all the tools failed to disassemble the code and I had to write all tools myself. What I find most fascinating is that reverse engineering these kind of games is very satisfying and even more fun than playing them. [1] https://github.com/s-macke/starflight-reverse

if I understand correctly, you're the author of decompiler for StarFlight game. The most famous game written in Forth. And maybe most popular piece of Forth software of all times. So I think you surely know more about Forth than many modern Forthers do :) Sorry, if I reveal this link too early, but this is very impressive work of you and StarFlight game/engine really deserves more popularity! https://github.com/s-macke/starflight-reverse

Thanks for posting the link. I found the archive a few month ago and downloaded the few documents that were left. The table here https://github.com/s-macke/starflight-reverse/blob/master/sr... is based on these documents and I filled some gaps of the symbol table. To start the game they used the word "LET-THERE-BE-STARFLIGHT", in the binary you see only part of it: "LET-TH". I wish this "someone" would provide a full copy of the archive :)

One of the most complex games Starflight of the 80th's is written in Forth. I had a lot of fun decompiling it. https://github.com/s-macke/starflight-reverse It turns out to be very portable because the assembler code is only about 1000-2000 lines. The rest is implemented in Forth itself. They use indirect threading to produce very dense code. They kept even most of the debugging symbols inside the code and kept the forth interpreter itself in the code.