# Unity Version
Minimum supported and recommended Unity version is 2019.4.x; this won't change until the stream is out of maintenance, 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.
Unity 2019.4.30 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 and are officially supported by us:
- Standalone: Windows, Mac, Linux
- Mobiles: iOS, Android
- Web: WebGL
- Consoles: Nintendo Switch
While Unity allows building for numerous other platforms (PlayStation, Xbox, Stadia, etc), some features (eg, save system) may not work out of the box, as access to the platform-specific SDKs is restricted for registered developers only. We don't have the access to such SDKs and are not able to provide support for platforms outside of the list above. Find more information about developing for game consoles in the article.
# Enter Play Mode
Naninovel supports disabling both
Reload Domain and
Reload Scene options under "Enter Play Mode Settings" category of the project settings. Disabling the options will make entering play mode take less time, especially in large projects.
# 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 (selected by default).
At least "Explicitly Thrown Exceptions Only" level is required for
Enable Exceptions option in "Publishing Settings" (selected by default). The setting is only applicable for WebGl builds. "None" level is not supported.