Playing offline, the games 'output log' has this message spammed :
-----
[ACTk] Time Cheating Detector: Could not resolve IP from the host pool.ntp.org =/

(Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/DebugBindings.gen.cpp Line: 51)

[ACTk] Time Cheating Detector: Could not resolve host pool.ntp.org =/
System.Net.Sockets.SocketException: No such host is known.

at System.Net.Dns.GetHostByName (System.String hostName) [0x00000] in <filename unknown>:0
at System.Net.Dns.GetHostEntry (System.String hostNameOrAddress) [0x00000] in <filename unknown>:0
at CodeStage.AntiCheat.Detectors.TimeCheatingDetector+<GetOnlineTimeInternal>c__Iterator2.MoveNext () [0x00000] in <filename unknown>:0
-----
Game will crash constantly unless a connection to "pool.ntp.org" is allowed.


Edit : correct the NTP url.

Best bet would be to open up a ticket direct with the developers.

What you;re looking at is an attempt to make sure your computer's clock is correct via a computer service called NTP:

https://en.wikipedia.org/wiki/Network_Time_Protocol

Rather surprised to see it spammed as overloading the NTP servers with requests is a quick way to get your computer banned from accessing them and an abuse report sent to your ISP. I run a webhosting company and we have a single web server make the request every few hours and our other servers make their requests from that one server.

With this being a third party seller, you're probably not going to be able to get support for the game from here.

Having said that, it;s an anti cheat within the game. Probably stuck with it.

Submitted a ticket at Revival.

That error starts at Line 136 in the log, and repeats constantly to the end ( Line 414 ) of the log.

My PC is deliberately set to "Local Time".
The catch ... make sure the old style CMOS Battery is still good.

Well, the game does work for me when playing offline. Yes, there NT_pbased the anti-cheat measures will not work, but that will not matter.

I did have some issues. My router died, and the game would run only for about a minute, and then freeze. But I found out that this only happened due to my system still trying to reach some name severs, and ran into timeouts. After I configured my network interfaces properly (not pointing it to an unreachable gateway, using no nameservers), the game did run flawlessly.

I also did already report those issues to the devs.