Launching with default settings and ignoring config file/settings on Windows

[LessThanBenji]

Hi, I'm using the Windows executable release of lazymc on Windows 11 (64bit) to run a Fabric server on 1.20.4.

Setting up and accessing lazymc.exe works fine, as does using .\lazymc config generate to create the config file lazymc.toml.

However, no matter what I do, lazymc does not respect the settings I choose in the config file. No matter how I do it, running .\lazymc start launches with the default shipped config settings and completely ignores my settings.

I have custom MOTDs (for the different sleeping/starting/stopping states) in there that aren't being used, I've changed the hold timer, I've changed some of the settings around starting the actual server at launch... none have any effect.

The config file isn't being affected/changed itself, it retains all my settings, they're just ignored. I'm wondering if I've set something up wrong, or if this is an issue with the Windows release that's flown under the radar?

The rest of lazymc's functionality works fine as far as I can tell.

[LessThanBenji]

I've gone back through a few versions and as far as I can tell, the options set in lazymc.toml aren't respected by lazymc in any situation with my particular setup. I've tried running lazymc's executable by itself and invoking it via the command line, both methods work the same and ignore the config for all default settings.