Cross-play servers and .ini: how is Nitrado doing it?

[Nyrin]

Cross-play servers and .ini: how is Nitrado doing it?

This is a long shot, but worth a try.

With your own Win10 server (Xbox can connect, where you have .ini file access), how can you enable events, RCON, and other capabilities that Nitrado provides on the same sort of server?

 

Putting the appropriate and wiki-documented items into the .ini doesn't seem to take any effect. Yet if a provider can do it, there's some way -- unless they're actually getting a *different build* altogether, which is possible but just seems bizarre.

 

Has anyone had success with this? Alternatively, if there's a sideload .appx that someone is giving Nitrado under the table, it'd be awesome to make that more broadly available somehow, even if as part of a developer program (Microsoft does have provisions for this).

[Juggernaut]

Nitrado uses a different version than xbox/windows 10 hosting. Nitrados build is more similar to steam's version in that it runs headless (no gpu required) and has access to the command  startup arguments which the windows 10 version only has access to game.ini and gameusersettings.ini only. Without command startup arguments, controlling events, clustering, RCON, is impossible with xbox/windows 10 hosting. Also their build allows them to run multiple servers on a single machine easily since they don't require a xbox hosted account per server. It is a clear advantage Nitrado has for xbox hosting and most likely results in more revenue for them. Xbox/windows 10 hosting is severely gimped.