Studio update
The First Player Path Takes Shape
Since the first Developer Diary, the Evernight rebuild has moved closer to a real player-facing alpha experience, with invited access, a game lobby, player join flow, and the first gameplay client shell now taking shape.
Last month, we opened Evernight's Developer Diaries as a new public place to follow the renewed development work around the game. This month, there is more concrete progress to share.
The main theme of this update is simple: the rebuild is beginning to move from internal tools toward the first real player-facing path.
Invited alpha access is in place
One of the important rebuild milestones this month was establishing a controlled alpha access path for invited players.
This does not mean public registration is open yet, and it does not mean the full player account system is finished. The current goal is narrower and more deliberate: selected players can be invited into the new Evernight site, complete onboarding, sign in, and reach the protected alpha area.
That gives the project a safer way to begin gathering early feedback while the rebuild continues to mature.
The player lobby and join flow are taking shape
The rebuild now has the first version of a real player-facing game lobby. Players can see their games, games they can join, and active games through the new player site rather than relying only on admin-side testing tools.
The game join flow has also moved closer to the path players will actually use. Behind the scenes, the rebuild still has to bridge modern systems with parts of the existing Evernight game data, but the player-facing shape is now much clearer: sign in, find a game, join, and move toward play.
The first gameplay client shell is now visible
The most visible milestone this month is the first gameplay client foundation.
This is not the final Evernight gameplay interface, and it does not yet include the full set of orders, overlays, chat, or in-game actions. It is a foundation: a dedicated play screen where a player can enter a game and load a real map viewport.
That matters because Evernight is a map-centered strategy game. Seeing the rebuilt client begin to render the game map inside the player experience is an important step toward making the new version feel tangible.
The layout also leaves room for future work: map interaction, player context, actions, communication, and richer game information. Those pieces will come in focused stages rather than being rushed into the first shell.
Strengthening the map path
As soon as the map became part of the player-facing gameplay path, the map-rendering work became more important too.
The team has started improving the runtime path used to produce gameplay map images for the browser. This is partly technical infrastructure, but it directly supports the player experience: the rebuild needs map rendering to become steadier and easier to support before deeper gameplay interaction is built on top of it.
For players, the important takeaway is that the visible gameplay shell and the underlying map work are now moving together.
What comes next
The next focus is likely to stay close to the gameplay experience: making map rendering sturdier, expanding the safe game data the client can load, and preparing the first richer player interactions.
There is still plenty of work ahead. Full order entry, deeper map interaction, chat, real-time events, and the final gameplay interface are not finished yet. The rebuild is intentionally handling those pieces carefully, especially where hidden game information and player-specific visibility are involved.
But this month marks a meaningful step forward. Evernight now has the beginning of an alpha player path, a player lobby, a join flow, and the first version of a gameplay screen with a real map viewport.
The pieces are starting to connect.