Building the Foundation: MMO Architecture Migration

Welcome back to the Gildwall development log!

Today we want to share something different from our usual feature updates. We've been working on a comprehensive technical roadmap to transform Gildwall's architecture into a production-ready MMO stack, similar to what powers games like Albion Online and Diablo 4. This is a significant undertaking that will lay the foundation for the massive multiplayer experience we envision.

### Why This Migration Matters
Our current architecture works well for development, but to support thousands of players, dedicated servers, and seamless world transfers, we need to evolve. This migration isn't just about scaling, it's about security, anti-cheat, and creating a foundation that can grow with our community.

### Phase 1: Boot Scene Implementation
The first phase focuses on architectural cleanliness. We're separating network initialization from the main menu UI by creating a dedicated "Boot" scene. This means:
* NetworkRoot will persist across all scenes
* Both client and server will start through the same boot sequence
* Cleaner separation between networking logic and UI
* More robust scene management

This might sound technical, but it means a more stable connection experience and fewer edge cases when loading between scenes.

### Phase 2: Transport Layer Migration
Currently, we use Fishy Steamworks for networking. While Steam P2P is great for development, production MMOs need IP-based transport for dedicated servers. We're migrating to Tugboat transport while keeping Steamworks for platform features like friends, invites, and achievements.

This gives us:
* IP-based connections for dedicated servers
* Linux server compatibility
* Config-based transport selection for development flexibility
* Steam integration preserved for social features

### Phase 3: Character Service with Server-Side Storage
This is where things get exciting for players. We're implementing a full character system with server-side persistence. Why does this matter?

**Security:** Character data (level, stats, position) lives on the server, not on your client. No more cheating by editing local files.

**Anti-Cheat:** The server validates all character data before accepting it.

**Persistence:** Your character survives across game restarts and server reboots.

This includes character creation, selection screens, and server-authoritative spawning, meaning the server decides where you spawn based on your saved data, not the client.

### Phase 3.5: Session/Authentication Service
To support multiple login and world servers securely, we're implementing a JWT-based session token system. This allows:
* Secure cross-server communication
* World servers can validate sessions without trusting all connections
* Foundation for future gateway API architecture
* Token-based authentication that scales

### Phase 4: World Transfer System
The final phase enables sharding, the ability to transfer players between different world servers seamlessly. This is how games like Albion Online support massive player counts by distributing them across multiple world instances while maintaining a unified experience.

### What This Means for Players
All of this technical work translates to a better experience:
* More stable connections
* Fair gameplay with server-side validation
* Character data that's always safe
* The ability to support larger communities
* Foundation for future features like guild wars across worlds

### Current Status
We're currently in the planning and early implementation phase of this migration. This is a multi-month effort that we'll be rolling out incrementally to ensure stability at each step.

We wanted to share this roadmap with you because transparency matters. You're building this world with us, and you deserve to know what's happening under the hood.

Stay tuned for more technical deep-dives as we implement each phase. And as always, thank you for supporting the development of Gildwall!