magic9mushroom wrote on Sat, 09 May 2020 22:05

What happens if you design ships with tech you're not supposed to have and submit that in a .x file?

Per your other comment regarding the colonizer exploit, it'd be trivial for a host to detect, so I'm not sure why you care? Esp. given I can just hack the tech level into place, which would make it more difficult to detect.

Putting more advanced tech on a ship in the .x file appears to revert back to the lowest level tech or blank. Available techs just stay/change. So I just hack the tech into the .HST file. Looks like I can add MT parts to the .HST and .M file (and the .x file) and get them to stick; it doesn't check to see if I should be able to build them (again, if it did I could just add it to the race block).

really, with access to the HST file most bets are off. And I'd bet at this point there's not much I couldn't find a way to with the .x file. But as I mentioned before, I'm not interested in hacking the .x file. From a host perspective, if someone thought someone had hacked their turn file, I could easily tell by checking at the GUI or if necessary the core block structure if it wasn't something TH didn't already catch. Not like there's enough players to make that burdensome. Much like tracing (network) packets, it'd be an interesting puzzle.

I really do encourage you to look at the TotalHost code (including the standalone scripts). From there you can experiment all you want, and I'll be glad to help you understand what you do not. There's a reason I open-sourced it ...

I mean, you know what a checksum is, so you should be able to figure it out if I could And I could always use more help.