Thanks for taking action on my comment, defaulting to the config on empty seems to make sense, otherwise the user is in control and can do whatever they are trying without interference 👍

I took me a while to understand that this behaviour only applies to the mantis-launcher and not mantis itself. It should be possible to inject a whole script file into the mantis script so ./bin/mantis etc would work the same way, but that's a different issue.

Thank you for the quick response 👍

Regarding the launcher: I made that decision mostly because mantis launcher itself works perfectly fine and a user can configure anything by passing the correct parameters. I see the launcher and other bin scripts more as utilities, saving the users from typing -Dconfig.file=conf/$network.conf and letting them just use mantis-launcher $network.

That said, I also found a technical issue trying to extend the mantis script. The issue is that on Windows, the generated mantis.bat uses the arguments array %* directly, so shifting doesn't work, and I couldn't find any other solution to "bypass" a parameter like the shift in bash. So I also preferred consistency across platforms instead of a feature that only works on Unix.