CaT Issues

The last parts of ORBATs and rules are now edited and put together. As far as rules and ORBATs go I'm quite confident they will be ready at the time of the NATO module release. That would only leave the counters and TO&Es left to be done when the new module arrives.

However, a much more serious matter has returned; unfortunately the problems with the CaT seem to be coming back again. I'm experiencing some severe stability issues with MapTool, the application used as Camapign Tool (CaT).
MapTool is in constant development and the developers are quick to release new builds - unfortunately not all of them are stable.

Since the CaT uses Java I'm trying different combinations of java versions and builds of MapTool. Hopefully I'll find a combination that might work as a solution to the problems; going back to earlier, more stable builds of MapTool is one of the solutions I've tried to no avail so far.

I'm also reviewing the installed version of Java, but frankly, if a solution to the problems can't be found by tweaking the settings for MapTool itself, then I'm afraid I might have run into a dead end. Changing to another CaT would be a huge undertaking at this late moment in the development; most of the data is already put into the CaT at this stage.

Other than these new stability issues MapTool is doing a great job as a graphical campaign manager. But it is crucial that the CaT of the MC is stable, otherwise it can not be realeased to the OPCOs/TACCOs of the MC.

We quite simply cannot have a CaT that keeps chrashing. I'll get back on this matter as soon as there is anything new to report!