Release 2.4.0

CONTRIBUTING.markdown

@@ -1,5 +1,7 @@
 # Contributing
 
+There's currently a bunch of issues marked with the `help wanted` label. You can also have a look [here](https://github.com/cardillan/mindcode/discussions/167). 
+
 ## Guidelines
 
 Mindcode uses JDK17, Maven and Spring Boot. 

doc/syntax/SYNTAX.markdown

@@ -34,7 +34,7 @@ Supporting tools:
 * [Command line tool](TOOLS-CMDLINE.markdown)
 * [Mlog Watcher](TOOLS-MLOG-WATCHER.markdown)
 * [Schematics Refresher](TOOLS-REFRESHER.markdown)
-* [Mlog Decompiler](TOOLS-REFRESHER.markdown)
+* [Mlog Decompiler](TOOLS-MLOG-DECOMPILER.markdown)
 
 Additional information on Mindcode and Mindustry Logic:
 

doc/syntax/TOOLS-CMDLINE.markdown

@@ -163,7 +163,6 @@ run options:
   Options to specify if and how to  run  the  compiled  code  on  an  emulated processor. The emulated processor is much
   faster than Mindustry processors, but can't run instructions  which  obtain information from the Mindustry World. Sole
   exceptions are memory cells (cell1 to cell9) and memory banks (bank1 to bank9), which can be read and written.
-  
 
   --run                  run the compiled code on an emulated processor.
   --run-steps {1..1000000000}

doc/syntax/TOOLS-MLOG-DECOMPILER.markdown

@@ -2,7 +2,8 @@
 
 The Mlog Decompiler allows to **partially decompile** an existing mlog file into Mindcode. The resulting file cannot be compiled by Mindcode right away, but needs to be manually edited to create loops, conditional statements, functions and other high-level control structures that may be directly or indirectly present in the original mlog.
 
-The decompiler is mainly useful to produce expressions and function calls in the correct Mindcode syntax, saving time and possible mistakes that would otherwise be needed to rewrite mlog into Mindcode by hand.   
+The decompiler is mainly useful to produce expressions and function calls in the correct Mindcode syntax, saving some time and possibly helping to avoid some mistakes
+compared to a manual rewrite of the entire mlog code from scratch.
 
 Mlog can be decompiled by both the [command line tool](TOOLS-CMDLINE.markdown) and the [web application](http://mindcode.herokuapp.com/mlog-decompiler).
 

pom.xml

@@ -21,7 +21,7 @@
     <properties>
         <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
         <spring.version>4.3.5.RELEASE</spring.version>
-        <revision>2.3.0</revision>
+        <revision>2.4.0</revision>
     </properties>
 
     <dependencies>

toolapp/src/main/java/info/teksol/mindcode/cmdline/CompileMindcodeAction.java

@@ -90,8 +90,7 @@ void addRunOptions(Subparser subparser, CompilerProfile defaults) {
                         Options to specify if and how to run the compiled code on an emulated processor. The emulated \
                         processor is much faster than Mindustry processors, but can't run instructions which obtain information \
                         from the Mindustry World. Sole exceptions are memory cells (cell1 to cell9) and memory banks \
-                        (bank1 to bank9), which can be read and written.
-                        """);
+                        (bank1 to bank9), which can be read and written.""");
 
         runOptions.addArgument("--run")
                 .help("run the compiled code on an emulated processor.")

webapp/src/main/resources/templates/mlog-decompiler.ftlh

@@ -7,7 +7,8 @@
         be directly compiled by Mindcode.</strong> Jump instructions in the original mlog are transcribed as <strong>if</strong>
         and <strong>goto</strong> statements which aren't supported by Mindcode and must be rewritten using conditional
         statements, loops and other high-level constructs. The decompiler is mainly useful to produce expressions and
-        function calls in the correct Mindcode syntax.
+        function calls in the correct Mindcode syntax, saving some time and possibly helping to avoid some mistakes
+        compared to a manual rewrite of the entire mlog code from scratch.
 </p>
 
 <div class="w-full">