-
Notifications
You must be signed in to change notification settings - Fork 1
Entities
First see Entity Component System.
An entity without components doesn't do much, but has some important functionality:
- Entities have a position in the world, which is measured in metres. This is used for rendering and physics.
- Entities have a scale which determines its size. This is used for rendering and physics.
- Entities have an event system to communicate between components and entities. See Event System.
The entity lifecycle can be seen in the figure below.
Note that create() is not called when the entity is instantiated through new Entity()
, but when the entity is added into the world. This means we know that an entity doesn't do anything while we are still adding components to it, or before we've placed it in the game.
Entities can also be disabled or enabled during gameplay. While an entity is disabled, it won't draw on the screen or run any updates. This is very useful when an entity isn't needed right now but will be later, since it won't have to be created twice. You can also create entities ahead of time but leave them disabled until they're necessary.
To make an entity, just instantiate one and use addComponent()
to add components to it. You can also use getComponent()
to access the components on an entity. The entity then has to be registered with the Entity Service to be created.
public static void spawnPlayer()
// Create entity
Entity player = new Entity()
.addComponent(new TextureRenderComponent("images/player.png"))
.addComponent(new PlayerMovementComponent())
.addComponent(new InventoryComponent())
.addComponent(new CombatComponent());
// Access components
player.getComponent(PlayerMovementComponent.class).setSpeed(3f);
// Create in the world
ServiceLocator.getEntityService().register(player);
}
- Uniform Pixel Grid Resolution
- Storyline
- Instruction
- NPC info
- NPC Communication Script
- Inventory-System-and-Consumables
- Storyline User Test
- Traitor Clues
- Game Characters
- Player Profile User Test
- Player Eviction Menu Sprint1: User survey (Team 7)
- Player Eviction Menu Sprint2: User survey (Team 7)
- Sprint3 - Win/lose Condition: User survey (Team 7)
- Sprint4 - Polishing-tasks: User survey (Team 7)
- Transition Animation/Special Effects/Sound Effects: Feature Overviews
- Transition Animation and Effects: Design Process & Guideline
- Sprint 4 User Testing
- Transition Animation & Effect: Code Guideline-Sprint4
- Sound effect when players complete npc tasks and hover over npc cards
- Fixing the clue bug
- Music Test
- Player Eviction Menu: Design Process & Guideline
- Player Eviction Menu (Feature Overviews)
- Player Eviction Menu: Code Guideline - Sprint1
- Sprint 1 User Testing
- Detailed Eviction Card: Design Process & Guideline
- Detailed Eviction Card: Feature Overviews
- Sprint 2 User Testing
- Player Eviction Menu: Code Guideline - Sprint2
- Sprint 2 Inventory System and Consumables Items User Testing
- Sprint 2 Inventory System and Consumables Items Functionality
- NPC interaction testing plan sprint3
- NPC interaction testing results sprint3
- NPC Dialogue Scripts
- Code Guideline
- Win/lose Condition: Design Process & Guideline
- Win/lose Condition: Feature Overviews
- Sprint 3 User Testing
- Win/lose condition: Code Guideline - Sprint3
- Enemy List
- User Testing 1: Enemy Image Filter
- User Testing 2: Enemy Animation and AI
- User Testing 3: Basic Attack