The blueprint handles spawning new tiles and destroying old ones to maintain seamless gameplay and efficient memory usage. The `OnComponentBeginOverlap` event for the EndTrigger component triggers when the player collides with it, checking if the colliding actor is of the type BP_NT3000_C. If the cast is successful, the game mode is retrieved and cast to GameMode_EndlessRunner_C, which then calls the `Add Floor Tile` function to spawn a new floor tile at the end of the current sequence, ensuring the endless nature of the game.

To manage memory and prevent clutter, the `OnComponentBeginOverlap` event for the Box component detects collisions with obstacles, verifying the actor type and invoking the `On Collision With Obstacle` function. This leads to a 2-second delay before the Destroy Actor function is called, programmatically removing the specified tile or obstacle from the game. This process ensures a continuous and smooth gameplay experience by dynamically spawning new tiles and cleaning up old ones, showcasing efficient event-driven programming and memory management.

In here, the `OnComponentHit` event for the StaticMesh component is triggered when an obstacle collides with another object. This event captures details such as the hit component, other actor involved, other component, normal impulse, and hit result. When a collision occurs, the Other Actor is checked to determine if it is of the type BP_NT3000_C. If the cast to BP_NT3000_C is successful, indicating that the colliding object is a valid tile or player character, the `On Collision With Obstacle` function is called, passing the BP_NT3000 instance as the target.

The `On Collision With Obstacle` function handles the logic for what happens when an obstacle collides with a tile or player character. This function can include various responses such as damaging the player, triggering animations, or other game-specific behaviors. By defining these collider rules, the blueprint ensures that obstacles interact appropriately with other game elements, enhancing the game's challenge and dynamic interactions. This efficient handling of collisions showcases a solid understanding of event-driven programming and collision detection in game development.

Player Movement:

Input for Corners:

Collision with Obstacle Trigger and Action:

Pause Toggle Controller:

The `Donut spawner for pickup` is a BP function randomly places donut pickups in a defined area within a floor tile. It starts with the `Spawn Donuts` event, which activates the process. The `Golden Donut Spawn Point` marks the base location. A `Random Point in Bounding Box` function determines a random position within the spawn area. Finally, the `Add Component Child Actor` function spawns the donut at this random position, attaching it to the spawn point. This creates varied and unpredictable donut locations for players to find.

The `Obstacle and Donut Alternately Spawn Logic` blueprint function handles the random spawning of either an obstacle or a donut. It starts with the `User Construction Script`, which kicks off the process. The `Set Spawn Point` function sets the location for spawning. A `Random Integer in Range` function then generates a random number, either 0 or 1. This number is used in the `Switch on Int` node to decide what to spawn: a 0 triggers the `Spawn Obstacles` function, while a 1 triggers the `Spawn Donuts` function. This setup ensures that each spawn event alternates between obstacles and donuts, keeping the gameplay varied and unpredictable.

After setting up the initial endless runner gameplay complete with floor spawning, obstalce and pickup spawning and a player that can be controlled, I enhanced the gameplay by inheriting from the `Floor Tile` blueprint, creating child BPs and adding left and right corner tiles, and upward and downward ramps and a simple logic to spawn it and ensure that the tiles spawned never collides with each other.