# onesync

There are more ways to enable onesync so let's take a look at how to do it in two ways.

* By putting the command in server.cfg

```
# enable OneSync (required for server-side state awareness)
set onesync true
```

* By putting startup command

```
+set onesync true
```

If we done everything correctly we can check the final result by command **onesync** in server console

![](/files/qW4S3263nWiLMNbAZdVO)

The onesync has to be always on "on" if there is "legacy" or "off" that's bad and the resources will not work.

Know issues:

* TXAdmin can rewrite the onesync which can be a reason why the status of onesync has not changed.
* You may have more commands in server.cfg / anywhere else where you execute "set onesync" where the value could be different than "true" like above


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://documentation.rcore.cz/server/onesync.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.