It seems to all be working locally, so I’ve patched the server - and that still seems to be working OK (although I didn’t try creating a new game version).
Anyway, ms and mx will both catch < 1024 errors, although very basic checking only - you can still put in illegal args, it’s just that you won’t get away with the common case mistake :).
Also, when you want to change the value of an arg or a prop, just set it again and the new val will overwrite the old - due to a failed SQL table update some time ago which I didn’t notice, it was allowing many duplicates of the same arg and param (no primary key checks). But that’s now fixed.
And you get a warning message on the release-editing screen if your JVM is missing / invalid, so you don’t have to wait until you test before finding out :).
PS: if you noticed the site go down this evening … it’s the dreaded NIO “out of direct buffer memory” bug. I checked: no files open, just a couple of TCP connections (*). To paraphrase Cas, the developers of NIO should be hung by their toenails until they realise the importance of actually allowing people to kill buffers, and to query the state of the buffer mem AND … to FIX THEIR CODE so that it uses memory properly (as noted in several outstadning bug parade bugs, IIRC).
(*) this particular server has had hundreds of files streaming off the hard disk in parallel in this JVM without breaking sweat (before I noticed my typo that was failing to close files in certain situations!). A few TCP connections cannot be bad…