I really like the game. Hackhub has the best UI and real-life tool parity I have seen in the Hacker sim genre. My vision, and I'm not sure it aligns with the devs one, is that it *could* become almost a game training lab for aspiring pentesters, but it does need some growth before that can happen. a) The devs will need to add a true, **simulatated** Linux system, like in Grey Hack. Currently, there are several missing directories, and the ones that are there have missing files. There are no terminal programs in /bin for example. No Kernal, no /usr/bin, no /proc etc. These things need putting in and actually be simulated. Same goes for Networking Infrastructure and a fully functional in-game OSI model. Then we would be able to hack a router, login to it using our web browsers, and mess with port forwarding and firewall rules to achieve our nefarious aims! Also, at the moment, executing MITM attacks with Wireshark is way too easy and doesn't make sense. B) The POSIX standards need fleshing out. Currently there is no chmod, chgrp, chown etc in the game. This is needed as manipulation of these file and directory permissions/privileges are core to privilege escalation phases in pentesting. This is another element of Linux that needs fleshing out and simulating accurately. C) Educational depth - The game is good at explaining what needs to be done, but not good at what the commands you are typing are actually doing, and how they are exploiting inherent system weaknesses. An annotated Handbook would be a good idea. This is important if HackHub is to become an valuable education game. D) Finally, maybe post v1.0, consider adding Windows/SMB targets. Dealing with the differences between systems is a real-world issue pentesters face.

I love the loop of this game, but the coding implementation is an absolute abomination. It has a total identity crisis: you're working in a Python UI, using JavaScript syntax, while trying to follow C# structural logic. As someone with 1,000+ lines of actual coding experience (C#, Terraria modding), it’s frustrating to watch the syntax highlighting go 'dead white' on valid code just because the engine is confused.
​The core issue isn't that the terminal is broken; it's that it suffers from a massive Logic Identity Crisis. The UI labels files as Python (.py), but the engine rejects Python structure. Instead, it forces you to use JavaScript logic (backticks and ${}) and Java-style commands, all while demanding a C#-style async function Main setup.
​For a coder with real-world experience, this is a nightmare because the syntax highlighting is misleading—core operators and functional logic stay white, making it impossible to debug at a glance. You end up hunting for 'ghost spaces' or 'semicolon tails' rather than solving actual hacking puzzles. Since this is in Early Access, the devs should pick a single language and stick to its rules. It’s a 5-tab juggle right now just to bypass a parser that doesn't know what language it’s speaking. Also do not use the 'Quick Fix' tool. If you highlight your code up to the async function Main line and click the suggestion, the editor doesn't fix the syntax—it deletes your entire script. It’s a destructive tool masquerading as a helper.

gamifying hacking is peak