The (Type, bool includeInactive) overload guarded its modern-API
branch with #elif UNITY_2023_1_OR_NEWER while the legacy reflection
helper LegacyFindObjectsOfType is gated by #if !UNITY_2022_3_OR_NEWER.
That left the entire Unity 2022.3.x band falling through to a
legacy helper that the preprocessor had already excluded, producing
CS0103: 'LegacyFindObjectsOfType' does not exist in the current
context (e.g. on 2022.3.62f2, see #1105).
The 3-arg FindObjectsByType(Type, FindObjectsInactive, FindObjectsSortMode)
overload has been available since Unity 2022.2, so 2022.3 can use the
modern API directly. Aligning the threshold with the rest of the file
(2022_3_OR_NEWER) closes the gap with no API loss.
Closes#1105
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
1.Add Compat based scripts revolving around UnityCompatShims.cs, that will document our current API Compatibility changes in several files.
2.Add custom screenshot folder selection
dsarno