Gamestate Loop

[heinezen]

Implement the core components of the gamestate loop

• Game entity
  • Create game entity from nyan GameEntity
  • Create components from nyan Ability
  • Initialize internal components in spawner
    • Position
    • Ownership
    • Command Queue
  • Pass animations to render entity
    • Pass std::string instead of util::Path
    • Differentiate between absolute and relative paths (see file referencing)
    • Move current animation path outside of GameEntity
• Basic nyan API interface
  • Ability
    • Fetch properties
      • Animations
      • Sounds
      • Diplo Stances
  • Player Setup (civs)
• Components
  • Idle
  • Live
  • Move
  • Turn
• Activity system (New Gamestate: Drafts #1377 (comment))
  • Node graph
  • Systems
    • Idle
    • Move
  • Activity Component
  • Event Canceling

[JonasBorchelt]

What do you think about this code?

if (entity->has_component(component::component_t::MOVE)) {
    std::vector<coord::phys3_delta> positions = {
        {0, 1, 0},
        {1, 2, 0},
        {2, 2, 0},
        {3, 1, 0},
        {3, 0, 0},
        {2, -1, 0},
        {1, -1, 0},
        {0, 0, 0} // Assuming this is equivalent to pos
    };

    std::vector<int> angles = {
        279,
        225,
        180,
        135,
        90,
        45,
        0,
        315
    };

    for (int i = 0; i < positions.size(); i++) {
        entity_pos->set_position(time + i + 1, pos + positions[i]);
        entity_pos->set_angle(time + i + 1, coord::phys_angle_t::from_int(angles[i]));
    }
}

[heinezen]

Oh hey, thanks for checking out the code :D

Given that the current code is just test code and soon to be removed, it probably doesn't really matter how it looks. Your solution looks more maintainable though, so if this were an engine demo, it would be the better solution.