It has come to my attention that there is a huge problem with some of the old artefacts on Windows. Namely, something has broken the JTextField listeners etc so that they are laggy and do not respond properly. This means that the client key, secret key, and telegram ID fields get nulled – I am not exactly sure how this is happening – and this causes the program to crash on restart because the autosave file now contains null keys. For arcane reasons, rebuilding the jar in modern Java fixes it. I have no idea why this is a solution.
This is the first actual release since version 8.2 in 2018 and the first pre-release since version 9.pre2 in 2020. There have been some substantial improvements to the parser documented in the change log. Among them are:
- Inclusion and exclusion of nations by regular expression
- Inclusion and exclusion of regions by region tags
These have been available in the repository if you built the jar yourself for some time. I have tested that they work myself in some tests, especially when recruiting for Europe. I am rather confident that these new syntaxes work. I have also updated the code to be more resilient to strange changes in the autosave.txt file. Hopefully this class of errors does not recur.
I have tested for this JTextField problem on Windows Java 22 and macOS Java 17 and the issues do not seem to be recurring. My thanks to Bisofeyr for reporting this problem. Because I have not tested the Marconi jar, I am not releasing it. I have now tested and built a reduced jar with dependences with Maven for both Communique and Marconi.