-
-
Notifications
You must be signed in to change notification settings - Fork 2
Compatibility
Optimum is client-only. It connects to any Vintage Story server running the matching game version (currently 1.22.3). The server does not need any modification. From the server's perspective, Optimum looks like a standard client.
Each Optimum release targets one Vintage Story version. Running Optimum built for 1.22.3 against a 1.22.2 or 1.23.x server will fail at the version handshake, same as vanilla. Check the release notes for the supported version.
Most client-side mods work with Optimum. Mods that add items, blocks, recipes, or UI elements through the standard modding API load without issues.
Mods that may conflict:
- Mods using Harmony to patch the same methods Optimum modifies at source level. The compiled DLL already contains the optimization, so a Harmony patch targeting the same code path may hit unexpected IL.
- Mods that hook into entity rendering internals (custom renderers, shader injection).
- Mods that replace the frame-limiting or game-loop logic.
If a mod causes problems, disable it and test. Most issues are detectable at startup (crash or log error on shader compile / method resolution).
Optimum does not modify save formats, world generation, or block/item data. You can open the same world folder with Optimum and vanilla interchangeably.
Other players do not see any difference when you connect with Optimum. The server sends the same packets, your client processes them the same way. The only change is on your GPU and CPU: less redundant work per frame.
If you encounter problems, switch back to your vanilla client. Your data path, worlds, and account remain intact. Optimum writes its settings under Optimum* keys in clientsettings.json; vanilla ignores keys it does not recognize.