The biggest update in Community Version History: Elemental Fracture 6.1.0 – Patch Notes

Hey there, everyone! Doobs here. On behalf of everyone here at Elemental Fracture, I’m very excited to announce the next iteration of the Spellbreak Community Version. 6.1.0 is the biggest wave of new features the Community Version has ever had. Almost nothing below has been in the game before this release: a native Friends, Party, and matchmaking stack that talks to a real Elemental Fracture backend, a full account system with a website behind it, a *real* one-click launcher that does the entire setup for you, Crouch and Equip Any Rarity built right into the game, and a permanent North American backend that stays on and fresh around the clock. If you play the Community Version, this is the release where it stops feeling like the start of something and starts feeling like the whole thing.

A word on what this is, because it matters. Elemental Fracture is not a new game. It is Spellbreak, kept alive. When Spellbreak’s official servers shut down, the game did not stop being one of a kind; it just stopped having anywhere to play it. The Community Version exists to give it that somewhere again: to preserve the real game, the real movement, the real spellcasting, and run it for anyone who still wants to play. 6.1.0 is the release where a huge amount of what a living game needs, the friends, the parties, the matchmaking, the account, the launcher, all arrives at once.

These notes are long, on purpose. I would rather tell you the story than hand you a bare list, because a line that says “party display works” tells you nothing about whether it matters. So I have tried to explain not just what is here but why it is built the way it is and what it means for you at the keyboard. Read the parts you care about, skip the ones you do not. If you only read one thing, read the first section of Part 1, because it is the heart of the whole project.

A quick map of what is below:

• Part 1 – The social, party, and matchmaking stack. Native, real, and permanent.
• Part 2 – Accounts and the website. Who you are, and where you sign up.
• Part 3 – The launcher. One program that does all the work.
• Part 4 – The in-game menus, the EF Controller, and the account screen.
• Part 5 – Gameplay: Crouch and Equip Any Rarity, baked in.
• Part 6 – Performance, and the plumbing underneath that you never see but always feel.

Part 1 of 6: Social, Party, and Matchmaking

This is the center of gravity of 6.1.0. Spellbreak’s Friends, Party, and matchmaking screens are alive, powered by an Elemental Fracture backend that speaks the game’s own protocol. Everything in this part is the real, built-in game UI. None of it is an overlay, a reskin, or a mod window drawn on top pretending to be the real thing. I keep repeating that because it is the single most important fact about this release, and it is the thing that took the most work to earn.

Why this was the hard part

Let me set the stage before the bullet points, because the bullet points do not do it justice. It is worth knowing how this got here, because the how is the whole reason it is real and not a clever fake.

When Spellbreak’s official servers shut down, the game did not lose its social features in the sense of deleting them. The Friends list is still in there. The Party system is still in there. The matchmaking flow, the class select, the queue, all of it, still in there, fully built and polished by the original team. What the game lost was the other end of the conversation. Every one of those screens works by sending a specific message, in a specific private format, to a service that used to answer. Press “add friend” and the game composes a request and sends it off, expecting a particular kind of reply. After the shutdown, it sends that request into the void and hears nothing back, so the screen just sits there, dead, waiting for an answer that never comes.

There were two ways to give those screens someone to talk to. The easy way is to fake it: draw my own menu over the top of the game, with my own buttons and my own list, and quietly run everything through a mod. That would have been faster and it would have been a lie. It never looks native, it never feels native, and every player would eventually notice the seams. The hard way, the way I chose, was to learn the exact language the original servers spoke, message by message and reply by reply, by reading Spellbreak’s own code, and then to build a backend that speaks that language fluently. Then I taught the client to open the connection it stopped opening after the shutdown, so those original screens have someone to answer them again.

The payoff is that the game genuinely cannot tell the difference between Elemental Fracture and the servers that went dark. When you add a friend, you are pressing Spellbreak’s real add-friend button, and a real Elemental Fracture service is answering in the game’s own tongue. That authenticity is the entire point, and it is why this feels like the game rather than a shell of it.

Your Spellbreak ID

• Every player has a unique Spellbreak ID: a single, one-of-a-kind name, for example Doobs.
• Names are unique across the whole community. When you register, if the name you want is taken, you are told immediately and asked to pick another, so there is never any ambiguity about who is who.
• Your ID is what shows in-game, and it is what your friends use to find and add you. It is surfaced in your account screen and in the EF Controller so you always know exactly what to tell people.
• There is no four-digit discriminator tag. Some games make you tack a #1234 onto your name so names can safely collide. Elemental Fracture does not. There is no tag to remember, no separator to type, and no “wait, was that a 7 or a 1” moment when a friend reads their number off to you. A name is a name. You add Doobs, and you are done.

Why identity comes first: a social system is only as good as its ability to name a person unambiguously. “Add Doobs” has to mean exactly one person, and it does. Making every name globally unique gives you that guarantee, and the thing you say out loud to a friend is just their name, nothing more. This tiny piece of identity is the foundation the entire friends and party system stands on.

Friends

• The native Friends list is live. You can add, accept, decline, and remove friends directly from the in-game Friends tab, the real one.
• Each friend shows a live presence state so you can read the room at a glance: online and in the menus, in a match right now, or offline.
• Friend requests, accepts, and removals are all driven over the Elemental Fracture backend, which means they persist. Close the game, come back tomorrow, and your list is still your list.
• Friend cards carry identity and non-default cosmetics, so your list actually looks like your friends instead of a row of anonymous placeholders.
• The “add a friend” box asks for a plain name, matching the tag-free ID, and the name validation behind it accepts a plain username, so a correct name is never rejected for missing a tag that does not exist.

The practical upgrade here is enormous. Without this, “playing with friends” means coordinating out of band, in a Discord call or a text, agreeing on a server, and pasting the same IP address to connect to the same place at the same time, hoping everyone did it right. Instead, your friends are a list inside the game, with a light next to each name telling you who is around. That is the difference between a community that has to schedule a match and a community that can just bump into each other.

Party

• Invite a friend straight from your friends list. The invite arrives in their invites tab, and when they accept, you are grouped up. No coordinates, no addresses, no timing.
• Leader controls live in the native per-member options menu: promote another member to leader, kick a member, or leave the party, all from the game’s own UI.
• The leader crown renders correctly on every client, including your own, so it is always obvious who is in charge. This sounds trivial and was not; getting the crown to show on the leader’s own screen, and not just on everyone else’s, was its own small fight.
• Party placards in the lobby show each member’s name, rank, and cosmetics, and they update live as the roster changes rather than freezing on a stale snapshot.
• Leaving a party cleanly resets you back to solo, whether you leave under your own power or the party naturally drops below two members and dissolves.
• Departed members are removed promptly for everyone in the group. No lingering ghost entries hanging around after someone has clearly left. Getting the last mile of this right, so a member who leaves actually vanishes from a teammate’s squad HUD instead of freezing there, came down to forcing a network update at the exact moment of removal so no client is left holding a stale roster.

Parties are where the “same team” promise starts to matter, and getting the display honest, the crown correct, and the cleanup clean is what makes a party feel like a party instead of a fragile arrangement that falls apart if someone alt-F4s.

Matchmaking and the queue

Press Play and you drop into a real matchmaker, one that finds you a game and the right people to play it with.

• Press Play, pick your class, and enter a real queue with a live timer you can watch tick up and cancel whenever you want.
• All four modes route correctly. Solo, Duos, Squads, and Capture each send you and your group to the right kind of server.
• Your whole party lands on the same team in the resulting match, using the game’s native premade-squad path rather than a hack bolted on the side.
• If no server is ready and waiting for your mode, a fresh one boots on demand and you are sent to it as soon as it is up. You do not have to know or care whether a server existed before you pressed Play.
• Matchmaking pools players headed to the same mode into the same match instead of scattering them across lonely instances. Two people who both queue Solo can land in the same lobby, which is the whole point of matchmaking existing.
• The queue is readiness-verified. The matchmaker will not hand you a server that is not actually up and accepting connections yet. It waits until a server has genuinely confirmed it is joinable before it sends you there, so pressing Play never drops you into a hole.
• Mode ownership lives in the EF Controller and travels with your queue request, which keeps routing clean and predictable rather than something patched onto the wire at the last second.

The thing I want to highlight is the rubber-banding, or rather its absence. A single static server looping matches over and over causes the kind of rubber-banding that makes a game feel unpolished at best and unplayable at worst. Matchmaking that spins up the right server on demand, for the right mode, and pools real players into shared matches, is not just a convenience feature. It is a direct fix for one of the worst feelings a revived game can have.

The connection behind it all

• The native social system connects to a public, permanent endpoint: wss://play.elefrac.com/appserver.
• That connection is secured end to end. TLS terminates at the edge, and the appserver process the game actually talks to is never exposed as a raw public port. Only the front door faces the world.
• Your authentication rides the same secure channel, so the friends, party, and queue you see are tied to your real account, not to a guess based on a name you typed.

This backend is deployed as part of the North American server architecture and stays on for everyone, all the time. It is a real, always-on service, and that permanence is a big part of what 6.1.0 is: the friends list is there when you open the game tonight, and it will be there tomorrow.

Part 2 of 6: Accounts and the Website

Behind every friend, every party, and every match is the question of who you actually are, and 6.1.0 gives that question a real answer. Elemental Fracture now has a proper account, a proper place to create and manage one, and a proper website wrapped around all of it. This is the piece a lot of you will feel first, because it is the thing you touch before you have even launched the game.

A real account, made the way you expect

• You create an Elemental Fracture account with an email and a password, the way you would sign up for anything else. No hunting for a bot command, no copying a long token string, no editing text files.
• If you would rather not manage another password, you can link your Discord account and sign in through it. One click through Discord’s own authorization screen and you are connected.
• Both paths land you at the same place: one account, one Spellbreak ID, one identity that the game, the launcher, and the website all agree on.
• Accounts are server-authoritative. Your name and your identity are owned by the backend and handed to the game at launch, so what you see in-game is always the real, current truth about your account rather than something cached locally that can drift out of sync.

Signing up is deliberately boring, in the best way: an email and a password, or a single Discord button. That is the difference between an account you have and an account you are still trying to create.

The website: elefrac.com

The site is the front door for the whole project. It is where you download the game, manage your account, read the documentation, and check whether the servers are up.

• A landing page that knows your platform. The download button detects whether you are on Windows or Linux and offers the right build automatically: the Windows installer, or the universal Linux AppImage. No guessing which file is for you, and no accidentally grabbing the wrong one. The button text is tuned for contrast so it is actually readable, and the platform labels are honest, so a Linux visitor is not told to go find a Windows version.
• Account management, in the browser. Sign in, see your Spellbreak ID, link or unlink Discord, and manage your profile from a clean account page. If you sign in with Discord, your Discord avatar is pulled in and shown as your profile picture, cropped cleanly to a circle so it always fits its frame regardless of the source image’s shape.
• Documentation that matches how the game actually works. A quickstart walks you through creating an account and using the launcher, and a full guide covers the in-game EF Controller menu, so a new player can go from “never heard of this” to “in a match” without getting lost.
• A focused FAQ. The questions people actually ask, with answers that match what you are playing.
• A live status page. A footer widget and a status view report whether the servers are up, so when something is wrong you can check the site instead of wondering whether it is you.
• Patch notes as a real feed. The site publishes patch notes and announcements as a blog, and that same feed is what the launcher’s “What’s New” panel reads from, so notes like these can reach you inside the launcher too.

The whole site sits behind a proper reverse proxy with TLS, so elefrac.com is a normal, secure website. The account API the site talks to stays entirely internal, on the private server network, and never rides the public path, so account traffic is not exposed just because the public pages are.

Discord, done right

• Linking Discord works through the correct authorization flow, so connecting your account is a single approve-and-return.
• Your Discord avatar renders correctly on the account page: fetched at a sensible size, cropped to a circle, and shown cleanly without stray rings, badges, or borders bleeding in from the page theme.

One identity, everywhere

The point of all this is consolidation. There is a single source of truth for who you are, and the website, the launcher, and the game all read from it. Sign in once, and you are the same person in all three places, with the same name and the same standing, no matter which one you opened.

Part 3 of 6: The Launcher

If the account system answers “who are you,” the launcher answers “how do you get in,” and the answer is now: you open one program and press a button. There is no manual install anymore, no base-game zip to extract, no folder surgery, no hand-placed patch files. This is the piece that makes everything else reachable, because a feature nobody can install is a feature nobody has.

One program that does everything

• A single one-click launcher handles downloading, installing, patching, launching, and self-updating. You open it like any other app.
• Windows and Linux are both first-class. Windows gets a proper installer; Linux gets a universal AppImage that runs on effectively any modern distribution without hunting for dependencies.
• On install, the launcher puts the mod loader into the game’s binary folder and the feature mods into the mods folder for you, and keeps that folder tidy so nothing stale lingers and causes strange behavior. Your setup stays clean and predictable.
• The launcher keeps itself up to date. When a new launcher build ships, it updates itself; when a new game version ships, it patches the game. You press Play; it handles the rest.

Sign in the way you made your account

• The launcher signs you in with your email and password, matching the account you created on the site.
• There is no auth-token chore. No token to generate, no token to paste, and no auth_token.txt to create in the right folder. The launcher keeps the game folder free of that kind of thing entirely.
• Once you are signed in, the launcher carries your identity into the game automatically on every launch through a secure, in-memory handoff, and refreshes it as needed. You simply stay authenticated without ever thinking about it. Authentication should feel like nothing at all, and it does.
• Sessions expire honestly. If your session lapses, the launcher notices and tells you, showing “Session expired” and prompting you to sign in again, instead of pretending you are still logged in and then failing silently the moment you try to play.

The details that make it feel finished

• The “What’s New” panel reads the live patch-notes feed from the website, so release notes reach you inside the launcher without me having to hand-edit the launcher for every update.
• The account area shows your Spellbreak ID and your avatar, so the launcher feels like it belongs to you.
• The install-location section is labeled “Launcher Location” so it is clear what it points at.

Getting into a preserved game usually has a failure point at every single step: extract the base game, find the prerequisites, drop the patch into the right Paks folder, generate a token, create the token file, paste it correctly, and hope. Each of those is a place a new player quietly disappears. Collapsing all of it into one program that just works is, honestly, one of the most important things in this whole release.

Part 4 of 6: Menus, the EF Controller, and Quality of Life

6.1.0 fills in the menus around all of this, so the game feels like it belongs to you and remembers you rather than treating you like a stranger on every launch. None of the items in this part are as headline-grabbing as native matchmaking or the account system, but taken together they are the difference between a menu you fight and a menu that gets out of your way.

Native Account management

• The native Account screen is fully functional.
• Region selection is here. Pick your region and the game routes you to servers near you instead of wherever it felt like sending you.
• Your Spellbreak ID is surfaced where your identity belongs. The game’s Player Name box, which would otherwise let you type a name the server just overwrites, is now a clean read-only display of your actual, server-owned Spellbreak ID, labeled “My Spellbreak ID,” with the obsolete name-entry row collapsed so there is nothing misleading to click.

Region selection deserves a moment, because it is quietly one of the most impactful settings in the whole game. Being sent to a server on the other side of the world is the difference between spells that land when you cast them and spells that land a frustrating fraction of a second late. Putting region control in your hands, in the native screen where it belongs, means you can actually take ownership of your own latency.

The EF Controller

The EF Controller is your in-game hub: it is where your identity, your mode, and your account state come together in one place, surfaced natively inside the game, and it is wired straight into the new account system.

• It carries your server-authoritative Spellbreak ID, handed over from the account system, so the identity you see in the controller is the real one, not a local guess.
• It owns your mode: the mode you choose travels with you into the queue, which is what makes all four modes route correctly.
• It is the surface where account-linked state, like your role and standing in the community, is reflected in-game, kept in step with the backend through the same live refresh the launcher uses.

The controller is deliberately native and quiet. The goal was never to bolt a loud overlay onto the game; it was to make the game’s own hub reflect the Elemental Fracture backend, so the whole thing feels like one coherent game rather than a base game with sticky notes on it.

First-boot and defaults

• Your first loadout defaults to your preferred class instead of some hardcoded class that has nothing to do with how you play.
• These defaults are deliberately polite about parties: a saved solo preference will not stomp on a live party’s mode when you reconnect. The party you are actually in always wins, because it should.
• The first-boot welcome screen is branded for Elemental Fracture and cleaned up, so a new player’s very first screen reads correctly.

This is the kind of thing you only notice by its absence. A menu that forgets you every time makes you do the same three clicks forever. Getting the restore logic right, especially the part where it defers to a live party instead of overriding it, took more care than it looks like it should, precisely because the wrong version of it would be subtly annoying in a way that is hard to name but easy to feel.

Mode selection

• The mode picker runs every mode through the same clean path, so they all behave consistently instead of some taking a different internal route.
• The Match Settings button only appears for the mode where it actually does something, rather than showing up everywhere including modes where clicking it accomplishes nothing.
• Mode changes reflect in the lobby instantly instead of lagging a beat behind and leaving you wondering whether your click registered.

A dead button is worse than no button. Every time a player clicks something and nothing happens, they trust the interface a little less. Keeping Match Settings only where it means something, and making mode changes feel immediate, is a small honesty upgrade for the whole menu.

Lobby and party display

• Party member placards, cosmetics, and ranks render live in the lobby podium, updating as the roster changes.
• The leader crown shows on your own client, not just on everyone else’s screens.
• When a teammate leaves mid-match, they drop cleanly off your squad HUD instead of lingering as a ghost entry.
• The friendly blue glow outline that marks your allies stays correct after a mid-match team change, so an ally always reads as an ally.
• Post-match summary placards read the correct, current display name instead of a stale cached one, so the scoreboard shows who was actually there.

That blue-glow one matters more than it sounds in the middle of a fight. If the game tells you someone is on your team when they are not, or fails to tell you someone is on your team when they are, you will make a bad call at the worst possible moment. Keeping the friendly outline honest after a team change is a safety feature disguised as a cosmetic one.

Part 5 of 6: Gameplay – Crouch and Equip Any Rarity, Baked In

6.1.0 brings two gameplay additions, Crouch and Equip Any Rarity, and they ship inside the launcher’s package, so there is nothing to download, drop in a folder, or activate by hand. They are simply part of the game.

Crouch

• Crouch works, and everyone sees it. Both the client half and the server half are in place, and the crouch state is replicated to everyone near you, so when you crouch, other players actually see you crouch. It is not a private, local-only animation; it is a real, shared game state that the server agrees with and broadcasts.
• Getting replication right is the whole game here. A crouch that only you can see is a toy. A crouch the server knows about and tells everyone around you about is a mechanic, and a mechanic is what you get.

Crouch is perpetual, and swap-proof

This is the part I am most careful about, because it is about durability.

• Crouch ships as a permanent game pak (EFCrouch_P.pak) that the launcher installs into the game’s content folder and leaves there for good. It is bundled inside the launcher’s package, so a normal install puts it in place with everything else.
• Crucially, the launcher’s ruleset swapper does not touch it. The launcher can swap the game between its Elemental Fracture balance and a Classic, closer-to-vanilla feel, and that swap only parks and activates the balance content. Crouch sits outside that mechanism entirely. Whichever ruleset you are on, Crouch stays installed and stays working. It is perpetual by design, not by accident.

Why this matters: a feature that silently disappears when you flip a setting is worse than a feature that was never there, because now you have to debug it. Making Crouch a standalone, permanent pak that no ruleset swap can disturb means it is genuinely part of the game, across every ruleset the launcher can put you on. Baking it in like this, rather than running it as yet another toggle, is the same philosophy as the native social work: if it does not feel built-in, it is not done.

Equip Any Rarity

• Equip Any Rarity lifts the pickup rarity gate so you can swap any piece of equipment into its slot regardless of rarity, with the server agreeing rather than quietly reverting your choice.
• Like Crouch, it is server-honest. It is not a client-side illusion that snaps back the moment the server has an opinion; the server is in on it, so what you equip stays equipped.

Bundled, not fetched

Both mechanics ship inside the launcher’s package. Fetching and installing individual gameplay mods correctly is a chore, and every one is a chance for something to go wrong. Folding them into the package the launcher installs means the features are just present and working the moment you are in the game, and the launcher curates that package to exactly the mods a player needs, keeping it clean over time.

Part 6 of 6: Performance and Under the Hood

The least visible part of 6.1.0 is the part I suspect you will feel the most. This is the plumbing: the performance work that makes the whole thing feel native, and the deployment work that makes it real for everyone rather than a demo on my desk.

Performance: made to feel native

A preserved game can feel jittery or clunky, like it is running on tape, when its hot paths are quietly doing far too much work. Some of you told me it felt that way, and I did not want to wave it away, so I went looking for the specific causes of that feeling and took them out.

• Logging is off-thread. When a mod writes a log line, that write no longer happens on the game’s own thread where it could stall a frame while it hits the disk. It is handed off to a background writer, so it never blocks the game thread. This is the single biggest cross-cutting win, because logging is everywhere.
• Menu scans are gated and throttled. Menu features that could otherwise walk the entire object table, thousands of objects, on every single party heartbeat now only run when the roster or the mode actually changed, and rapid-fire work like typing is capped so it cannot pile up and stutter.
• The overlay stops working when it is closed. The in-game overlay does no per-frame setup while it is hidden. If you are not looking at it, it is not costing you anything.
• A background actor scan runs on a sensible cadence. A crouch-related tally that could otherwise run dozens of times a second, walking the world every time, now runs on a slow cadence that produces the same result for a tiny fraction of the cost.
• The server caches the friend graph. Reading a party or a friends list no longer opens a fresh database query per member per refresh. The graph is held in memory and annotated with live presence, so the common case never touches the database at all.
• The server database uses write-ahead logging. Reads and writes do not serialize and block each other, so the server stays responsive even while it is busy.

The felt result is menus that settle smoothly instead of stuttering, typing that does not hitch, a post-match friends list that snaps in instead of crawling, and a game that is simply crisper overall. None of these are flashy on their own. Together they are the difference between something that feels like a mod and something that feels like a game.

Multiple devices, multiple sessions

• Your account allows several active sessions at once instead of kicking you off one device the moment you sign in on another. Signing into the launcher on your desktop does not invalidate the session on your laptop, and the server keeps a sensible number of your most recent sessions alive. If you move between machines, you are not fighting your own account.

Roles and standing, in step

• Community roles, like staff, developer, and tester standing, are reflected live in the game and the launcher, kept in step with the backend through the same refresh path that keeps your identity current. Your standing follows you without a restart, because the client asks the source of truth rather than trusting a value it cached at login.

The backend, built to stay on

• The native social system is deployed as part of the North American server architecture, not as a one-off local demo, and it stays on for everyone.
• The appserver connection is on by default in the shipped client, so the social features work out of the box after a normal launcher install, with no extra steps or hidden switches to flip.
• The backend is a coherent set of services: the router that owns authentication and accounts and speaks the game’s native protocol, the manager that spins up game servers on demand, the players and metrics services behind the social and stats data, the Marla Discord bot, the status monitor, the website, and the content delivery that feeds the launcher its downloads. They run as a tidy, clearly-named stack, which is a large part of why the service can actually stay up.

This part is invisible by design. If I have done my job, you will never think about any of it. You will open the launcher, press Play, and be in a match with your friends, and the entire apparatus that makes that possible will stay quietly out of your way.

Getting started

If you already play, the launcher will pull 6.1.0 for you: open it, and it patches the game and updates itself. The one new step is the account. Head to elefrac.com, sign up with an email and password (or by linking Discord), and sign in with those in the launcher.

If you are new, there is nothing to hunt down. Grab the launcher from elefrac.com, which hands you the right build for your platform automatically, create an account on the site, sign in, and press Play. The launcher takes care of downloading, patching, installing the mods, and keeping itself current. Crouch, Equip Any Rarity, and the native social features are all in the box.

Thanks for reading all the way down here. Genuinely. Elemental Fracture exists to keep this game alive, and it only works if people are in it. If something in these notes does not match what you are seeing in-game, that mismatch is exactly the kind of report that makes the next version better, so please tell me. Every bug you find and every match you play moves this forward faster than I ever could alone.

See you in the arena. ⚡