How jrbashl/flappy-bord works
Project type and purpose
• This is a Unity-based 2D “Flappy Bird” clone.
• Purpose: run inside the Unity engine, load a scene, spawn pipes and a player “bird” (Bord), handle input and collisions, manage scores and speed boosts, render visuals.
File structure
• Top-level files: README.md, GapColliderManager.cs (misc script), Unity version + ProjectSettings.
• Assets folder (all game assets):
• ColliderVisualizer: editor tooling for debug.
• Events: ScriptableObject assets defining game events.
• Prefabs: Pipe, Bird, environment prefabs.
• Scriptable Objects: pipeline speed configs.
• Scripts: game logic (BoostColliderManager, Bord*, PipeLogic, GameEvent, listeners, etc.).
• Scenes: SampleScene contains the game objects.
• Settings, TextMesh Pro, Thirdparty, TutorialInfo: supporting assets and demos.
README
• Single line “Making a copy of flappy bird” confirms it’s a clone, no extra microservices or external back ends.
Components
a. Main components:
• Unity Engine Core
• Scene Manager
• Input System (Player_Actions_for_Bord)
• Game Loop & Update Cycle
• Physics & Collision System
• Game Logic Scripts:
– BordController (jump, collision, scoring state machine)
– PipeSpawner & PipeLogic (spawn, move, recycle pipes)
– BoostColliderManager (trigger speed boosts)
– GameEvent / GameEventListener (decoupled event bus)
• Scriptable Objects (PipeSpeedScriptableObject, event assets)
• Prefabs & Assets (Bird, Pipes, Materials, Shaders)
• UI (Score display via TextMesh Pro)
b. Relationships and interactions:
• Input System → BordController.Jump
• Physics Engine → collision callbacks → BordCollision / GapCollider → GameEvent.Trigger
• GameEvent → listeners (e.g. BordScore, BoostColliderManager)
• BordStateMachine → state transitions (Alive, Dead)
• PipeSpawner uses PipeSpeedScriptableObject to set velocity
• Update loop drives PipeLogic.Move and BoostColliderManager.Check
• Scene Manager loads SampleScene and instantiates Prefabs
• Renderer subsystem draws Meshes, Shaders, Materials
c. Architectural patterns:
• Component-based (Unity’s ECS/MonoBehaviour)
• Event bus via ScriptableObject assets (GameEvent pattern)
• State machine pattern for player state
d. Key technologies:
• Unity 2021+ engine (Universal Render Pipeline)
• C# MonoBehaviours
• ScriptableObjects for data/config
• Input System package
• TextMesh Pro for UI