Onesync can't be enabled via server.cfg

After using set onesync on inside server.cfg I see it as off inside server console. Onesync natives doesn’t work as well.

Client: production
FXServer: 3524 and lower
Category of bug: Server
OS: Windows 10 v1909

What you expected to happen
I expect enabled onesync while setting it via server.cfg instead setting it via execution parameters.

What actually happens
Onesync is disabled - it was verified via server console by typing onesync and by using onesync natives.

Reproducible steps, preferably with example script(s)

  1. Set up server by following Tradinional Installations Steps in Setting up a server guide from official docs
  2. Type onesync in server console

Related isssue:

Ah, I see - onesync on works fine but set onesync on leads to this as it seems.

Likely as set is not calling the custom interception handler or so.

1 Like