# Unity Version
Minimum supported Unity version is 2019.4.x; this won't change until the stream is out of maintenance (expected in summer 2022), at which point we'll upgrade to the next LTS stream.
In case breaking changes or critical fixes are introduced throughout the release cycle, minimum supported patch version (the ".x" part) could change. You can always find minimum supported Unity version for specific Naninovel release in the change log.
Support for new releases from the TECH stream is added once they're out of beta.
Unity 2019.4.22 is the most tested and stable version to use with Naninovel at the moment. It's not uncommon for Unity to introduce regressions even in LTS patches (let alone minor and major releases), so we highly recommend using this version to minimize production risks.
# UPM Packages
Only verified package versions are supported. When installing or updating a package via UPM (unity package manager), make sure it has a "verified" label for the Unity version you're currently using.
All the engine features are implemented using cross-platform APIs and are expected to be compatible with all the platforms Unity can target.
The following platforms were tested for compatibility:
- Standalone: PC, Mac, Linux
- UWP (IL2CPP scripting backend only)
While Unity allows building for game consoles (Switch, PlayStation, Xbox, etc), some features (eg, IO-related) are not implemented out of the box, as access to the platform-specific SDKs is restricted for registered developers only. In Naninovel case, this affects the save system, which will require implementing custom serialization handlers in order to work correctly on the consoles. Find more information about developing for game consoles in the article.
# Render Pipelines
While it's possible to use Nanionvel with Unity's scriptable render pipelines (both URP and HDRP), some built-in features may not work out of the box and we won't be able to provide any support in such cases; see render pipelines guide for more information.
# Managed Stripping
"Medium" and "High" managed bytecode stripping profiles are not supported. Either disable the stripping or use the "Low" profile (set by default).