Week 2 built the infrastructure to make that doorway work: data models, interaction systems, and the architecture for moving between worlds. Week 3 is where the expedition stops being an idea and becomes a living thing moving through space.
This is where Fallen Compass transforms from a room into a world.
The Story behind the Story - Designing the Game
The Overworld: Where Plans Meet Reality
The office is safe. Methodical. You can take your time, weigh options, change your mind. But the moment you step through that door, everything changes.
The overworld is vast, indifferent, and unforgiving. It doesn't care about your plans. Every decision to move forward consumes time and resources. Every detour is a gamble. Every point of interest on the horizon could be salvation or disaster.
Week 3 was about building that transition - from the safety of planning to the risk of execution.
The Convoy as Physical Presence
One of the earliest design commitments for Fallen Compass was this: your expedition would never be an abstract marker on a map. You would see your people, your animals, your supplies. The convoy would be there, physically present in the world.
This matters because the game is about tangible stakes. When your caravan stretches across rough terrain, you see its vulnerability. When supplies run low, you notice the lighter loads. When danger approaches, you recognize how slow and exposed your expedition truly is.
Week 3 brought that vision to life for the first time. A group of characters and pawns moving together across terrain in response to your commands. It's not polished yet, but it's real. You click a destination, and the expedition goes there. You see individual figures navigate obstacles, spread out, reform. Simple. Essential. Alive.
Points of Interest: Promises on the Horizon
Scattered across the overworld are markers - ruins, clearings, camps, landmarks. Right now, they're just stubs: right-click one and you get a debug message when the convoy arrives there. But their presence changes everything.
Do you investigate that ruin? It might hold supplies. It might hold danger. It will certainly cost time. Do you push toward your goal, or do you detour? The world doesn't tell you. You have to decide, and live with the consequences.
These points of interest aren't content yet, but they're potential. They make the world feel like more than a straight path from A to B. They promise discovery, risk, and the weight of choice.
The Camera: Your Window Into the Unknown
The overworld camera was a particular challenge. It needed to feel stable and intuitive while giving you (limited) control over how you see the world.
The camera tracks your convoy without locking onto it, giving you the freedom to scout ahead, survey the terrain, and plan your next move - all while the caravan steadily moves forward. You can pan and zoom to explore, but here's the catch: the range depends on your convoy's skills and abilities.
This balance matters. Too much camera freedom and you lose spatial awareness. Too little and you feel constrained, unable to see threats or opportunities. Week 3 found the middle ground: enough control to feel empowered, enough constraint to stay grounded in the world.
Behind the Curtain - The Technical View
Week 3 was about making the overworld exist - not just as concept art or a prototype, but as a playable space with real systems underneath.
Building the Overworld Level
The overworld is a 3D landscape viewed from a top-down perspective. Creating it meant:
- Setting up terrain with proper collision and NavMesh for pathfinding.
- Placing the camera at the right height and angle to balance overview with detail.
- Adding basic environmental features (hills, valleys, paths) to test movement and navigation.
The terrain is still greyboxed - simple geometry with placeholder textures - but the foundation is in place. Hills will influence movement, valleys will offer cover at the cost of mobility, and open plains will leave you exposed. These aren't just visual details; they shape gameplay, driving decisions about routes, risk, and resource management.
For now, it's a single 2km x 2km test level. In the future, there will be dozens - eventually - each with unique geography, challenges, and secrets.
Top-Down Camera System
The camera system required balancing several competing needs:
- Follow the convoy smoothly without feeling sluggish.
- Allow dependent panning and zooming so you can scout ahead.
- Respect boundaries so you don't accidentally pan into empty space.
I implemented this using a Spring Arm component attached to a custom camera actor. The Spring Arm provides natural lag and smoothing, while the actor handles input for panning and zoom, all based on a constant scouting value for now.
Convoy Movement: Click-to-Move
The convoy is represented as a custom Actor with NavMesh-based movement. When you left-click on terrain, the game:
- Performs a raycast from the camera to determine the clicked world location.
- Validates the location is reachable via NavMesh pathfinding.
- Calculates a path using Unreal's navigation system.
- Moves the convoy along that path at a defined speed.
This is conceptually simple, but the details matter:
- Pathfinding Reliability: NavMesh must be correctly generated and cover all walkable terrain. Early bugs included the convoy getting stuck on slight elevation changes or refusing to path across certain terrain types. Fixed by adjusting NavMesh settings and testing edge cases.
- Movement Feel: The convoy needed to feel weighty - not instant, not sluggish. This required tuning acceleration, deceleration, and turning rates. A caravan of people, animals, and supplies shouldn't pivot on a dime.
- Visual Feedback: When you click a destination, a temporary marker appears showing where the convoy will move. This prevents confusion about whether the click registered and gives you time to cancel if you misclicked.
The convoy is already represented as multiple characters and pawns - currently using mannequin meshes as placeholders. There's a leader whom others follow, with each member moving independently. This creates realistic convoy behavior where the group naturally spreads out and reforms as they navigate around obstacles. Future work will replace the mannequins with proper character models, animals, and cart assets, but the core movement system is already functioning as intended.
Point of Interest Interaction
POIs are actors placed in the overworld with collision volumes. Right-clicking a POI triggers an interaction - currently either a debug message ("Entered POI: [Name]") or a selection widget offering choices like ambush or trade.
This is a stub for future systems:
- Camps: Rest, manage resources, assign crew tasks.
- Combat Encounters: Transition to grid-based tactical combat.
- Resource Nodes: Hunt, forage, gather materials.
- Narrative Events: Discover ruins, meet travelers, make choices.
The interaction system uses Unreal's
Interface pattern (IInteractable).
Each POI type can define custom behavior without bloating a
single monolithic class. This modularity will be critical as the
game grows and POI types multiply.
Conditional Engine Pause (Backlog Note)
An important technical decision made in Week 3: how to handle pausing in different gameplay contexts.
In the office, the pause menu doesn't need to freeze the engine - there's no real-time simulation running. But in the overworld, pausing must stop convoy movement, NPC behavior, and environmental effects.
The current implementation uses the
GameStateManager to detect which context you're
in. When pausing from the Overworld state, the system will call
SetPause(true) to freeze the engine. When pausing
from the Office state, it skips the engine pause.
This is currently noted in the backlog because the basic functionality works, but edge cases (exiting the Pause Menu via 'ESC') need more testing before it's production-ready.
The Invisible Work
Week 3 wasn't just about adding visible features. It was also about refinement and bug fixing.
Bug Fixes
- NavMesh Gaps: Fixed issues where the convoy would refuse to path to certain locations due to NavMesh generation errors. Required adjusting terrain collision settings and NavMesh agent properties.
- Camera Snap During Transitions: The overworld camera would sometimes snap violently when loading the level. Fixed by ensuring the camera spawns at the correct position before the fade-in completes.
- Input Context Stacking: Early builds had issues where office and overworld input contexts would both be active simultaneously, causing WASD to move both the first-person character and the camera. Fixed by properly clearing input contexts during state transitions.
Polish & Iteration
- Convoy Speed Tuning: Tested multiple movement speeds to find the balance between "painfully slow" and "unrealistically fast." Settled on a pace that feels deliberate without being tedious (subject to further iteration - based on load and terrain).
- Camera Boundaries: Added soft boundaries that prevent the camera from panning too far from the convoy. You can scout ahead, but not so far that you lose spatial context entirely.
Why This Matters
Week 3 was the moment Fallen Compass became an expedition game.
You can now:
- Stand in the office and interact with the desk.
- Trigger a transition to the overworld.
- See a 3D landscape spread out before you.
- Click a destination and watch your convoy move toward it.
- Pan the camera to survey the terrain.
- Interact with points of interest (even if they're just stubs).
This loop - plan, transition, move, explore - is the skeleton of the entire game. Everything that follows (crew management, resource depletion, combat, events, permadeath) will layer onto this foundation.
If the transition between office and overworld felt broken, the game would never work. If the convoy movement felt sluggish or unresponsive, players would abandon it. If the camera was frustrating, the entire overworld would be unplayable.
None of those things are true. The foundation is solid. That's the milestone.
What's Next – Making the World Feel Alive
The overworld exists. The convoy moves. But right now, it's empty.
Week 4 will focus on closing the expedition loop and adding the first layer of consequence:
- Expedition Flow – Part 1: Complete the cycle from office → overworld → return to office with a basic expedition summary.
- World Map Widget – Part 1: A simple 2D overlay displaying the unrevealed world under fog-of-war, ready to be uncovered.
- Critical Bug Fixes: Addressing issues with state management, pause menu behavior, and visual polish.
This is where the game starts to feel like a system instead of a concept. Where decisions in the office lead to outcomes in the field, and outcomes in the field shape what happens next.
If you'd like to follow the journey, keep an eye on the upcoming Steam page and website. Smaller updates and screenshots will appear on social channels, and there will be opportunities to join testing as builds become playable.
For now, Devlog #2 marks the moment when the map stopped being paper and became a world you can move through.
See you in Devlog #3.