You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 exactly am not sure how this is happening – and this causes the program on restart because the autosave file now contains null keys which the program loads, causing it to crash. For similarly arcane reasons, rebuilding the Jar in modern Java fixes it.
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.
This discussion was created from the release Communique 12.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
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
JTextFieldlisteners 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 exactly am not sure how this is happening – and this causes the program on restart because the autosave file now contains null keys which the program loads, causing it to crash. For similarly arcane reasons, rebuilding the Jar in modern Java fixes it.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:
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.txtfile. Hopefully this class of errors does not recur.I have tested for this
JTextFieldproblem on Windows Java 22 and macOS Java 17 and the issues do not seem to be recurring. My thanks toBisofeyrfor reporting this problem. Because I have not tested the Marconi jar, I am not releasing it.This discussion was created from the release Communique 12.
Beta Was this translation helpful? Give feedback.
All reactions