I've seen a couple of people suggesting that nhcustom2 should have a graphical user interface. While it sounds appealing on paper, I've decided not to create one, for the following reasons: - I don't have the time. - The code would likely become more complicated than it already is. I'm a big sucker of the KISS philosophy, and since the codebase hurts my eyes enough as it is, I don't want to add another layer of complexity to it all. More complex code would also imply more time spent on debugging and maintenance too. All this is without talking about cross-compatibility between Windows and Linux (remember that it runs on both OSes), which is a whole can of worms on its own. And if I ever stop maintaining this program, I would like to hope that someone else might pick it up. In that regard, keeping the code simple is a priority. - Nothing would really be gained. Text files allow you to easily save, distribute and edit your configs. And once you understand the syntax (others have, I assure you), it becomes relatively easy to read too. Sure, a GUI would seem less obscure to new users, but that's about it. If someone ever wants to create a GUI, go for it. But for the reasons I cited, I won't merge any code that adds a graphical interface (not that I received any contributions, lol). You could make a web frontend for it, that would honestly be the sanest thing to do, imho. but like do whatever you want bruh, shit's in the public domain and all dawg