That tone is really not helpful. This is just a bloody hobby and I would like not to burn out from community pressure again.
That user’s problem has nothing to do with the new database, you are bordering on misinformation there. The user has a Java installation/setup issue and that is neither my fault nor anyone else’s. It’s not my job either to figure out how to get it to work on their particular system. You do it?
Nothing has changed for the Quake Injector. It can still read the old existing “database” XML format file. That file still is being served (with all the releases, up until the development on the new database started and no one bothered to update the old database anymore). All the download and screenshot links are perfectly working. Nothing about the Injector is broken. It will just not receive any more data updates. Unless someone builds a dumbed down export feature for the new database or rebuilds the Quake Injector to support the new database.
The Quake Injector is open-source. Anyone can make it better. The new website is not open-source yet but if you, dear reader, want to help or build something on it, just reach out and I will try my hardest to support you!
And yes, it would be nice to add some notes about this. But development was focused on more important things and I felt that I have been pretty clear about breakage.
Literally the first point under How you can help five years ago:
If there is confusion, the solution is simple: Come here or better yet, to the official Quake Injector repository on GitHub, and ask. It would be nice if there was a “we”, not a “you”.