> For the complete documentation index, see [llms.txt](https://documentation.rcore.cz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.rcore.cz/server/onesync.md).

# 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

![](https://1037498771-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MZErcztD5BvrKnwRGJq%2Fuploads%2Fgit-blob-50891901ed0bc987293b60f5e8f754170c2794cf%2Fimage%20\(2\)%20\(1\).png?alt=media)

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