Aki-Configurator mod by ereshkigal, that's all you need to know.
But be advised, if you change port via config, launcher will refuse to connect.
Probably caused by https protocol variable itself.
Since launcher doesn't take port for a connection, aka just 127.0.0.1
Even more updates,
first of all, BackendUrl that being generated by Eresh mod goes nowhere since there is no variable for that in ConfigHttp, it's just exist iirc.
changing values via that mod shows on the server terminal that is changed, but by netstat in cmd it clearly doesn't, it still listening for classic 443.
Aki-Configurator mod by ereshkigal, that's all you need to know.
But be advised, if you change port via config, launcher will refuse to connect.
Probably caused by https protocol itself.
Since launcher doesn't take port for a connection, aka just 127.0.0.1
Servers changes doesn't work on Aki Config as these changes are made after the server is launched.
That explain why then, here's more info and possible solution.
By compiling server.exe myself with a change of port, it does listen to it, same with hex-editing value in existing server.
Servers changes doesn't work on Aki Config as these changes are made after the server is launched.
Question is, why are they are there? 
Because i havn"t removed them
Don’t have an account yet? Register yourself now and be a part of our community!
Just a few of the 290 users online
