OCTOBER DEVELOPMENT UPDATE
Client version 0.1.15-staging.25 is now deployed to our staging environment. Hands-on gameplay testing is underway. Nytharis remains in Alpha.
In our previous development update, we talked about what comes after building the foundations of an MMORPG.
The answer was not simply more systems. It was making better use of the ones we already have.
That means a client that feels better to use. Controls that fit the way you play. Character progression that belongs inside the game, not just in a development preview. And more time spent turning Firstlight into a place worth exploring.
Since that article, the Passive Atlas has moved forward, Client Options 2.0 has taken shape, and our latest client update has reached staging.
This is not a new continent or a batch of new bosses. It is an update to the experience through which you encounter everything else in Nytharis.
Here is what has changed, what we are testing, and where we go next.
CLIENT OPTIONS 2.0
The Options menu has received a substantial redesign.
Instead of spreading information across the previous collection of pages, Options 2.0 brings settings together into five dedicated sections: Display, World, Interface, Key Bindings and Advanced.
The aim is straightforward. Finding a setting should not feel like searching through a developer tool, and changing it should have an understandable result.
Display settings, world presentation, interface preferences and controls now have clearer places of their own. Apply and Cancel provide an explicit way to manage changes rather than leaving players guessing about what has already taken effect.
These improvements are not just about making a menu look better. They are about making the client more comfortable to live with during an actual play session.
CONTROLS THAT FIT THE WAY YOU PLAY
Key bindings are now a much more practical part of the client.
Supported gameplay actions can use primary and secondary bindings, including modifier combinations. Individual action-bar slots can be configured, and relevant shortcut labels reflect the selected bindings.
When a new binding conflicts with another action, the interface offers a choice: reassign it, swap the bindings, or cancel the change.
There is also an important distinction between playing and typing. Gameplay shortcuts are suppressed while entering text in supported chat and text fields, helping prevent a conversation from unexpectedly becoming an action.
This gives players more room to arrange the client around their habits rather than adapting everything around a fixed set of defaults.
Key binding support is still developing. Mouse-button bindings and some keyboard-layout-specific keys are not yet supported. We would rather make that limitation clear than describe the system as unrestricted.
DISPLAY AND FRAME-RATE CONTROL
Options 2.0 also gives players more direct control over how the client runs.
The frame-rate limiter supports values from 30 to 360 FPS, alongside an Unlimited option. Common presets make it easier to choose a familiar target without entering a custom value.
VSync is available, and the client supports Windowed, Borderless Fullscreen and Fullscreen display modes.
Display-mode changes use a temporary confirmation step. You can keep the new mode or revert, and an unconfirmed change returns to the previous mode automatically.
Preferred key bindings and the frame-rate limit are saved between sessions. These behaviours were checked during local acceptance, with the latest staging build now receiving its own hands-on checks.
World and interface settings also provide access to presentation choices such as smoothing, multi-floor rendering, HUD preferences and UI scale.
The purpose is not to prescribe one perfect configuration. It is to give players useful choices for their own display, hardware and preferences.
PASSIVE ATLAS: FROM PREVIEW TO IN-GAME PROGRESS
Our previous article described a newer Passive Atlas revision that had not yet reached the game environment.
That part of the story has moved forward.
Passive Atlas V7 has since been deployed across the game and Portal, with hands-on in-game validation completed for that milestone.
The latest client update builds on that progress by improving how the Atlas behaves alongside the rest of the interface.
This distinction matters. The current patch is not announcing another collection of new passive nodes or a new balance pass. It is making the existing progression experience easier to use.
Planning a character is an important part of Nytharis. Opening the interface used to make those decisions should feel deliberate and predictable.
ONE FOCUSED WINDOW, NOT COMPETING PANELS
Opening the Passive Atlas now dismisses conflicting interface panels before the Atlas takes focus.
That includes overlapping inventory, equipment and container panels, along with the spellbook. Context menus and active drag interactions are cleared as part of that transition.
The result is a clearer boundary between ordinary gameplay windows and the full-screen progression interface.
You should not open the Atlas only to find another panel sitting above it. You should not accidentally reopen a conflicting dock underneath it. And closing an interface with Escape should produce an understandable result.
The latest work specifically targets those interactions.
These may sound like small changes compared with an entire passive tree. In practice, they are the details you encounter repeatedly while playing, checking equipment and considering your next point.
A good interface earns its place by helping you make a decision, then getting out of your way.
FIRSTLIGHT REMAINS FIRSTLIGHT
This release preserves the existing world.
It does not introduce a replacement map, a new set of regions or a separate world-content update.
The complete existing visual library has also been carried forward, including terrain, creatures, cosmetics and the supporting content needed to render Firstlight.
More than 34,000 visual assets were checked as part of preparing the client. Those are preserved resources, not a claim that this patch adds thousands of new graphics.
The focus is the client through which you experience the world.
New areas, encounters and rewards deserve their own development work and their own announcements. We are not presenting interface improvements as a content expansion.
A RELEASE MILESTONE, WITH PLAYTESTING STILL TO DO
The latest update has passed its automated release checks and is now deployed to staging.
The client and server builds have also passed the current Windows and Linux test runs.
That is an important milestone, but it does not replace playing the game.
A test can confirm that an action is handled correctly. It cannot fully tell us whether the interface feels comfortable after an evening of switching between combat, equipment, chat and character planning.
That is the work happening now.
We are checking the updated client in ordinary play, including display changes, saved preferences, window interactions, movement and returning to the game after logging out.
The distinction is simple:
The staging update is deployed. Final hands-on acceptance is still in progress.
This is an Alpha development milestone, not an announcement that every part of Nytharis is finished.
THE ROADMAP: PUTTING THE GAME FIRST
The client work does not replace the wider roadmap. It supports it.
Once the current staging release has completed its gameplay checks, our priority is to bring development attention back toward the things players can feel, discover and make decisions about.
FIRST: FINISH THE CURRENT PLAY EXPERIENCE
The immediate task is to test the complete client rather than its features in isolation.
That means checking whether the new settings work comfortably together, whether the Atlas behaves correctly during normal play, and whether any remaining interface friction needs attention.
We want to close this update with a clear understanding of what works and what still needs improvement.
NEXT: COMBAT, BUILDS AND REWARDS
Our near-term gameplay direction remains focused on stronger class identity, more satisfying ability interactions and meaningful character-building decisions.
The Passive Atlas is part of that picture, but it should not carry the entire weight of character progression.
Abilities, equipment and rewards also need to give players reasons to experiment.
The goal is for a different build to change how a character approaches an encounter, not simply how large a number appears on the screen.
THEN: MORE REASONS TO EXPLORE FIRSTLIGHT
The broader roadmap continues to include world content, quests, achievements, gathering, crafting and deeper dungeon experiences.
Nytharis already has a dungeon system and Portal integration. Future dungeon work should expand what is there through more interesting encounters, bosses, rewards and reasons to return.
The same principle applies elsewhere in Firstlight: build depth around the systems that already exist.
These are development priorities, not a list of features promised for the next patch. We are not attaching a release date to work that has not yet been completed and tested.
PLAYER STREAMS AND OTHER DEVELOPMENT TRACKS
The administrative tools, Player Streams, audience chat, clips and viewing features discussed in earlier updates remain separate parts of the wider development picture.
This client release should not be read as an announcement that all of those systems are complete or generally available.
Streaming performance, viewing quality and playback were identified as ongoing work in our earlier previews. Their progress needs to be reported and validated on its own terms.
For this update, the focus is Client Options 2.0, Passive Atlas interface behaviour and the delivery of the latest staging client.
Keeping those boundaries clear helps us show actual progress without turning every roadmap idea into an implied release promise.
FOR PLAYERS TESTING STAGING
Players with staging access can open the Nytharis Launcher, select the Staging profile and use Repair/PREPARE GAME to update.
The expected client distribution is 0.1.15-staging.25.
During testing, spend some time with the new Options pages. Change a supported key binding, try a frame-rate limit and check how the display confirmation behaves.
Open the Passive Atlas while other panels are already open. Move between the Atlas, spellbook, backpack and equipment. Log out, return and check the settings you expected to keep.
Useful feedback does not need to be technical. Tell us what you were doing, what you expected to happen and what happened instead. A screenshot and the steps needed to reproduce an issue are especially helpful.
The aim is not just to make the client pass a checklist. It is to make it feel right in use.
BACK TO THE ADVENTURE
This development cycle has asked for patience.
Some of its most important work will never become a feature that players open from a menu. What matters now is what that work allows us to deliver.
A client with more useful choices.
A Passive Atlas that fits better into the rest of the game.
And a clearer path back to developing the encounters, equipment, progression and world content that give those systems a purpose.
There is still plenty to build. We are looking forward to spending more of that time inside Firstlight, testing the game and shaping what comes next.
Thank you for following Nytharis, testing its updates and staying with the project as it grows.
See you in Firstlight.
The Nytharis Team
A SMALL NOTE FROM THE CREATOR
Outside Firstlight, I’m also building AutoDay.se, a separate project focused on reminders and everyday planning.
For anyone curious about what I’m creating beyond Nytharis, you are very welcome to take a look. Thank you for supporting the things I build, both in-game and outside it.