liveBook · Manning

System

As explained in High Performance Unity Game Development

In this section's ECS representation, a system is logic that operates on data arrays.

A system is logic that operates on data arrays. In enemy movement, the index identifies an entity, the EnemyPosition array holds component data, and the position update is the system. section 12.3

Listing 12.10 Original enemy movement before DOTS
static void moveEnemies(GameData gameData, Balance balance, float dt)
{
    for (int i = 0; i < balance.NumEnemies; i++)
    {
        Vector2 dir = -gameData.EnemyPosition[i].normalized;
        gameData.EnemyPosition[i] = gameData.EnemyPosition[i] + 
                                    dir * balance.EnemyVelocity * dt;
    }
}

The movement loop shows the calculation that modifies each enemy’s position array entry. section 12.3

ECS separates data and calculations into Components and Systems, which can add code and architectural overhead. Array-based data and static logic can support data-oriented design without adopting ECS. section 12.3 section 12.5

How High Performance Unity Game Development covers it

How deep it goes
Defines Systems as data-modifying logic and maps the term to an enemy-position calculation, without requiring full ECS adoption.
Examples
Uses an enemy-position array and movement loop to show a System updating each enemy.
What it assumes
Builds on an array-based enemy-movement example and defines Entity and Component alongside System.
What you can do after
Understand: map an array-based calculation to an ECS System and recognize when ECS overhead may be unnecessary.
How it connects
Links Systems to entities, components, data-oriented design, arrays, and static logic functions.

This explainer was generated by Manning's knowledge graph from the text of High Performance Unity Game Development. The section links point to the parts of the book it draws on.