Brainless Technologies Ltd.

While i realise its only pre-alpha, it would be great to be able to add monitoring to check for crashes etc.

Our server is 125.63.48.150:7777, query port 7787

I'm also attaching a query script someone wrote in case it helps.

Does downloaded twice mean masher has accepted this challenge and is hard at work?

or just on holidays somewheres?

Yeah, been digging in to it, forgot to reply.

Awesome, love your work.

Forgot to add that I'm happy to be the guinea pig and test anything you come up with.

Any news? I could possibly ask the devs for more info.

Still working on it, haven't had much time to work on it as of late.

No worries, I spoke to the devs anyhow, and the code is internal only at the moment, I presume because it will change alot being pre-alpha.

I also assume their new HUB System will pretty much destroy any chance of server monitoring, as no servers actually run until someone starts one.

Actually we are running a HUB now, vs old school servers. I wonder if there is a way to at least query the hub, so it can be restarted if it crashes?

Port Range Description
7777
This is the port that the game will communicate with clients on. It can be overridden using the "-port=xxxx" command line switch.
7787
This is the sever query port. When clients are looking to connect to your server, they will use this port to communicate with it. You can change this port in the Engine.ini file.
14000
Hubs Only -- This is the instance communication port. Instances will talk back to their hub using this port.
8000-8xxx
Hubs Only -- Each instance will utilize one of these ports starting with 8000 to communicate on. You can strictly control which of these ports needs to be opened via configuration options. See "Setting up a Hub" further down on this page.

I'm kinda reluctant to support this in its current state. Epic needs to add a proper protocol for querying servers.

Sure, I don't blame you, in fact I really don't see anyway that querying Hubs is going to work.