unity-csharp-fundamentals

Use TryGetComponent to safely attempt component access and check the result before using it. This pattern replaces unsafe GetComponent calls and prevents null-reference exceptions by explicitly validating component existence in Awake or Start.

Cache components in Awake using TryGetComponent or RequireComponent, then validate them before Start runs. This lifecycle order ensures dependencies are resolved early and guards against missing references during gameplay.

Use SerializeField to expose fields in the Inspector for manual assignment; use RequireComponent to enforce that a script requires specific components on the same GameObject. RequireComponent validates at design time; SerializeField gives runtime flexibility.

Combine RequireComponent attributes with inline code comments explaining null-safety patterns and initialization order. This documentation-driven approach makes explicit which dependencies are enforced and which are optional.

Yes. TryGetComponent safely checks for optional components at any lifecycle stage, including OnEnable. Guard the result with a null check before using the component to maintain null-safety across all lifecycle phases.