Change Details

While scripting, I suddenly got a sever problem: The local, experimental server would stop at the message: "Lade Mission" (ge. for Load Mission), there is no class description in DayZ Workbench and when closing the Workbench, it just crashes. Closing the local server would still let the process run in the backgroung, requiering me to end with the Taskmanager. Looking at the crash log revealed nothig: it just seemed to stop working. The Wordbench still gives me an error that I always ignore, since I could successfully create mods in the past. The only difference is that it crashes when I close the script editor and that I don't get any class descriptions and "intellisense". Compiling the mod anew also makes no difference and also throws no errors. After further researtch, I found actually 2 bugs, which you can try to replicate yourselfe, though, I do not know if it is just an exception for me. There was actually an error thrown when opening the Workbench. However, this faulty code lies in the mission script module which get's overshadowed by another error in the game script module (above mentioned error that I ignore). **steps to reproduce:** In Order to replicate this bug, you need to do this in any module (it's better to write it in another editor and later open it with DayZ Workbench as a project): # Write a comment section "/* comment section */" and comment it out. # Write in this section any method and end it with "))". It should look something like this: ``` // /* Print("Hello World")); */ ``` Now, if you include it your ScriptModulePathClass like "always" and open DayZ Workbench, it should take effekt as describted above. **additional information ** My theorie on all of this is that the the "))" is what actually makes this silent error. The commented out comment section only lets this code run or be read by the system, which results in this error. Similary, you can leave the comment section out and just leave the method with the "))" in, which results in the same behavior. The "))" itself probably puts the system in an infinite loop since, though not everything, it still takes up resources when it apparently does nothing. It may not be system breaking, but it still deliveres a lot of fustration, since you thought that you commented this section out, which, in fact, is not commented out and still at least seems to work. Is this intended behavior? Was this already reported? Can this be fixed with an update, please?

While scripting, I suddenly got a sever problem: The local, experimental server would stop at the message: "Lade Mission" (ge. for Load Mission), there is no class description in DayZ Workbench and when closing the Workbench, it just crashes. Closing the local server would still let the process run in the backgroung, requiering me to end with the Taskmanager. Looking at the crash log revealed nothig: it just seemed to stop working. The Wordbench still gives me an error that I always ignore, since I could successfully create mods in the past. The only difference is that it crashes when I close the script editor and that I don't get any class descriptions and "intellisense". Compiling the mod anew also makes no difference and also throws no errors. After further researtch, I found actually 2 bugs, which you can try to replicate yourselfe, though, I do not know if it is just an exception for me. There was actually an error thrown when opening the Workbench. However, this faulty code lies in the mission script module which get's overshadowed by another error in the game script module (above mentioned error that I ignore).

While scripting, I suddenly got a sever problem: The local, experimental server would stop at the message: "Lade Mission" (ge. for Load Mission), there is no class description in DayZ Workbench and when closing the Workbench, it just crashes. Closing the local server would still let the process run in the backgroung, requiering me to end with the Taskmanager. Looking at the crash log revealed nothig: it just seemed to stop working. The Wordbench still gives me an error that I always ignore, since I could successfully create mods in the past. The only difference is that it crashes when I close the script editor and that I don't get any class descriptions and "intellisense". Compiling the mod anew also makes no difference and also throws no errors. After further researtch, I found actually 2 bugs, which you can try to replicate yourselfe, though, I do not know if it is just an exception for me. There was actually an error thrown when opening the Workbench. However, this faulty code lies in the mission script module which get's overshadowed by another error in the game script module (above mentioned error that I ignore). **steps to reproduce:** In Order to replicate this bug, you need to do this in any module (it's better to write it in another editor and later open it with DayZ Workbench as a project): # Write a comment section "/* comment section */" and comment it out. # Write in this section any method and end it with "))". It should look something like this: ``` // /* Print("Hello World")); */ ``` Now, if you include it your ScriptModulePathClass like "always" and open DayZ Workbench, it should take effekt as describted above. **additional information ** My theorie on all of this is that the the "))" is what actually makes this silent error. The commented out comment section only lets this code run or be read by the system, which results in this error. Similary, you can leave the comment section out and just leave the method with the "))" in, which results in the same behavior. The "))" itself probably puts the system in an infinite loop since, though not everything, it still takes up resources when it apparently does nothing. It may not be system breaking, but it still deliveres a lot of fustration, since you thought that you commented this section out, which, in fact, is not commented out and still at least seems to work. Is this intended behavior? Was this already reported? Can this be fixed with an update, please?