Showing content from https://docs.unity3d.com/Manual/sprite/../object-oriented-development.html below:
Unity - Manual: Object-oriented development
Managing update and execution order
Object-oriented development
Traditional Unity projects are object-oriented in two related ways:
- They embrace the object-oriented programming philosophy, which is grounded in the concept of objects, their properties and functions, and the relations between these objects.
- The original architecture of Unity projects uses an object-based model with types derived from
UnityEngine.Object. In this model, scenesA Scene contains the environments and menus of your game. Think of each unique Scene file as a unique level. In each Scene, you place your environments, obstacles, and decorations, essentially designing and building your game in pieces. More info
See in Glossary are composed of GameObjects which in turn interact with and are controlled by objects of other types.
An alternative to object-oriented development is data-oriented development, which is both a programming philosophy and a set of technologies that help you implement those principles. The data-oriented approach offers strong performance advantages at scale but can be more challenging for inexperienced developers to learn.
Object-oriented and data-oriented development are not mutually exclusive and you can combine elements from both. For information on data-oriented development, refer to Unityâs Data-Oriented Technology Stack.
Topic Description Managing update and execution order Understand the order in which Unity executes your script components and the lifecycle callbacks within those scriptsA piece of code that allows you to create your own Components, trigger game events, modify Component properties over time and respond to user input in any way you like. More info
See in Glossary during the runtime application loop. Managing time and frame rate Understand how Unity measures time so you can manage the rate at which time passes in your application and ensure values update according to the appropriate time scale. Handling events Make your application responsive to events such as user input, object collisionsA collision occurs when the physics engine detects that the colliders of two GameObjects make contact or overlap, when at least one has a Rigidbody component and is in motion. More info
See in Glossary, and physics and rendering updates. Splitting tasks across frames Split the execution of a task synchronously across multiple scenes with coroutines. This can be useful for tasks that should progress gradually over several frames, such as a fade out effect. Interacting with web servers Use the UnityWebRequest system to allow your application to interact with a web server via HTTP. Adding functionality to objects at runtime Use the Unity Properties API to implement a visitor design pattern and add new operations to .NET objects at runtime. Moving objects with vectors Use vectors to move objects in a specific direction and magnitude in 2, 3, and 4 dimensions. Using common math functions Use common math functions, including trigonometric, logarithmic, and other functions in your application. Using randomness Generate commonly required types of random values. Null references Understand and diagnose null reference exceptions in Unity projects. Unity attributes Use Unity-specific C# attributes to define special behavior for your code. Additional resources
Managing update and execution order
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4