Portals

Design

Implementation

The portal and bridge entities are all mapped to a specific button entity which, when pressed, either enables or disables collisions with the relevant obstacle. Portals begin the level closed, or shut, thus not allowing the player to move through them until their mapped button has been pressed. Bridges begin the level open, or un-extended, thus not allowing the player to move over them until their mapped button has been pressed. This functionality is handled in the onCollisionStart function in the PlayerMovementComponent class. All portals and bridges are created with a SubInteractableComponent which is a dummy component that acts as an indicator to the mapInteractables function in the LevelGameArea class and the onCollisonStart function that the entity is a sub-interactable entity. A sub-interactable entity is one that starts in an initial state and whose state is changed after the player collides with its mapped interactable entity (i.e. button). Bridge entities will be created without a collider component such that the player will fall through them until they have pressed the bridge's relevant button. Portal entities will be created with a collider component such that the player will not be able to move pas them until they have pressed the portal's relevant button.

if (interactableComponent != null && !mapInteractables.isEmpty()) {
          ObstacleEntity mapped = mapInteractables.get(target);
          ColliderComponent colliderComponent = mapped.getComponent(ColliderComponent.class);

          if (mapped != null && mapped.getDefinition() == ObstacleDefinition.DOOR) {
                  // Desired affect on mapped door - disappears
                  colliderComponent.dispose();
          } else if (mapped != null && mapped.getDefinition() == ObstacleDefinition.BRIDGE) {
                  // Desired affect on mapped bridge - appears
                  colliderComponent.create();
          }
   }