What is happening at Wizden?
This is intended to be a comprehensive overview of the recent Wizards den drama. If you would like to submit any corrections and clarifications you are welcome to contact me at dffdff2423@gmail.com. If desired, you can encrypt mail with my pgp key. Please specify if I can publish your communications if you contact me.
A pre-release version of this article was given to the following people for comment:
- Aexxie
- Princess_Cheaseballs
This article will be going in “rough” chronological order and will assume the reader is familiar with ss14 but not the ongoing drama. This article or a future one will be updated with future information as it is known. I will try to be as neutral as possible. For your reference, my involvement with the SS14 community is that I am a long-time maintainer on Cosmatic Drift and help run a few of the inter-community backchannels.
The Wizden Admin Walkout
On November 10th, 2024 the overwhelming majority of active Wizards Den game admins along with the three head game admins (Nairod, Skarlet, and Chief_Engineer) opted to leave citing concerns with toxicity among leadership, several blocked attempts to improve security, and a general feeling the admin team was being exploited. Since this is fairly old news I am going to just link CE’s article which gives an overview of their perspective.
After the walkout there was a lot of talk about change, however in reality none of the major issues were fixed at Wizards den.
Quite a bit of minor drama happened between here and the next point but I am going to skip over most of it.
The Dwarf Incident
On February 10th, the project lead of Wizards Den, PJB, created two pull requests on the Wizards Den content repository, one which removes dwarves and another that removes text replacement accents. This resulted in two lengthy forum threads being created where the community mostly politely expressed their disagreement with these PRs: thread one, thread two1. Despite disagreement with the maintainers and community, these PRs were merged anyway against maintainer policy2. After this happened, PJB updated the maintainer policy document giving herself post facto permission to make these changes. After this, PJB transferred ownership of the Discord to DrSmugLeaf and took a break2.
During this ordeal, long time admin CptJeanLuc was banned from the Wizden server for providing constructive feedback2. You can read their prospective on the incident here. Former headmin, Chief_Engineer was also banned at this time and told no appeal would be voted on you can find his prospective here.
The Mass Removal
Shortly before her break a letter directed to PJB from the Wizden staff was created requesting change3. During her break, PJB went on a massive rant in the Opendream discord4. On May 2nd, 2026 PJB returned from her break and removed a large portion of staff without prior consultation and created the linked thread. After the large community outcry, she decided to let the removed staff nominate somebody to take over project management.

Wizards den started to begin talks with her and lawyers about transferring ownership of assets along with forming an e.V.(eingetragener Verein) organization in Germany to manage the money.
The Formation of The SS14 Continuance Commission
Disclaimer: I am personally involved with the SS14 CC
The night and day after the mass removal a large number of forks met to discuss plans for forking the engine. This ended up becoming what is now called the SS14 Continuance Comission. The first meeting lasted for two hours and ultimately it was decided to refrain from forking the engine and allow Wizden some time to get back on their feet. The group has continued to meet every other week since then. The following public statement was made:
We as stakeholders in the wider Space Station 14 ecosystem hold that:
- We prefer for the needed authority and keys to be transferred to a new standing team, comprised of both current and returning members, and we will find ways to support that new team if it is formed.
- We recognize the difficulty in doing a hard engine and platform fork, but commit to collaborating to do this if needed for the survival and benefit of all our servers.
- We recognize that this has exposed a large risk to the project, and we commit to future collaboration to make it easier in the future to make sure that Wizden, or a future central service/hub, cannot be a single point of failure, and existential risk to the project, going forwards.
The Breakdown of Negotiations
A few days ago PJB posted set the following message Wizden staff.

This was followed up with a more diplomatic public post.
Last night (June 5th, 2026), PJB opted to remove all staff involved with the key transfer from all infrastructure she still had control over with the following message:
The “Hack” of Auth Servers and Legal Action From the Wizards Den Team
Shortly after this, the Auth servers and forums were taken down with PJB claiming that they were “hacked”. My current understanding is what she means by “hacked” is that the Current Wizards’s Den Project Leads had shell access and were using it to take backups of the server which is why I placed it in quotes2.

Shortly before PJB pulled the plug, the Wizards Den team has opted to send her a cease-and-desist: page 1, page 25. However, it was only made public after the fact. Note that the version linked is an old version since that is what is publicly available. The date of compliance on the final draft is the 12th.
The auth servers are back online and run by PJB.
The Hack of Rouny’s Marine Corps (RMC)
Shortly after the above notice, the RMC game servers were compromised. It is unknown at the moment if a exploit was used or if it was just somebody with shell access backdooring the server. There is currently no evidence PJB is involved.

Is it safe to play SS14 right now?
As a player it is safe if you trust PJB. Currently she is running both the Auth servers and the Engine CDN. When you connect to any server you download a bundle from the Wizden Engine CDN containing engine code. This bundle runs outside the sandbox. If you trust PJB not to tamper with the engine code it is safe to play the game. If you do not, I advise closing the launcher until more information is known. Note that if she does tamper with engine code there could be possible criminal charges on her part. The fact she uses her legal name online would make the case easier to prosecute. Thus, I don’t personally think she would go that far. Ultimately, that is your choice to make as a player.
The full details of the RMC hack are yet to come out pending full forensic review from their system administrator. If this was just somebody abusing shell access to the server then it should be entirely safe to host servers. If it is a exploit you should wait for a fix. Regardless, I advise keeping your server off until more information is known about the RMC hack.
Update: It is safe to host servers provided your server is secured. There is currently no evidence of some kind of RCE venerability. The information for players above still applies.
Wizden Update
Added Sat Jun 6 05:38:48 PM CDT 2026 for people to reference who are not in the wizden discord. The original message is here. Minor changes were made to formatting to make it work with the website. Blame me for it looking like shit, it is hard to adapt a discord message to a website
Hello everyone,
We are issuing this update to provide clarity on recent infrastructure downtime and to address ongoing misinformation regarding the Wizards’ Den project.
Recently, a former contributor stepped down from project leadership and agreed to transfer the operational keys to the newly unified leadership team. Unfortunately, attempts to formalize this transition were met with shifting demands, and the former contributor subsequently used legacy access to revoke permissions from the core team and restrict access to vital infrastructure.
Where We Currently Stand:
In response to these unauthorized lockouts, the Wizards’ Den leadership team, operating under our formal legal entity, has issued a Cease and Desist. We are currently working closely with legal counsel to resolve the retention of these legacy assets.
What This Means for Players:
Authentication & Legacy Domains: The authentication servers and the legacy domain (spacestation14.com) are currently under the sole control of this former contributor. We cannot guarantee the security or stability of infrastructure we do not control, so any usage of the legacy platform is at your own risk.
The Migration: To ensure the uninterrupted future of the project, we are actively migrating the official Wizards’ Den servers and community to secure, team-controlled infrastructure. We will advise when they are available, and provide the domains so that you can update your bookmarks.
We appreciate your patience as we navigate this transition. The project is larger than any single piece of hardware, and our priority remains the safety, stability, and continuation of the Wizards’ Den community. We will provide technical updates regarding the new server connections and auth protocols as soon as they are fully deployed.
A Note on Community Well-being:
We know that disruptions within communities you care deeply about can be highly stressful and overwhelming. The safety and well-being of our players always comes first. If you or someone you know is going through a difficult time or struggling with their mental health, please know that you are not alone. Help is always available. You can reach the Suicide & Crisis Lifeline by dialing or texting 988 (in the US), or reach out to international resources and crisis text lines available in your specific region.
A timeline of events so far:
Hello everyone. To provide our community with transparency and address any ongoing misinformation regarding the recent infrastructure downtime, we have outlined a factual timeline of the events that led to our current migration:
Early May: After an internal transition on May 3rd, a former contributor stepped down from project leadership and agreed to transfer the operational keys.
The Negotiation: We held internal votes to select the new keyholders. While the former contributor initially agreed to these new leaders, they immediately tried to change the terms regarding organizational requirements. We successfully negotiated a partial transfer of some community assets, with the understanding that the remaining infrastructure keys would be transferred later.
The Breakdown: Over the subsequent weeks, communications began to break down as the former contributor began blocking many of the new leads of the project.
The Lockout: Recently, the former contributor returned to change the terms once again. They issued new demands and made it clear that if these terms were not met, the entire project would be deleted. At the same time, they used their access to revoke the permissions of several staff members from the infrastructure and key areas of the project.
Our Response: We responded yesterday with a formal Cease and Desist, telling them to keep their promise and transfer all keys. They have not currently complied, and the situation is still developing.
We appreciate your patience as we navigate this transition. We will provide technical updates regarding the new server connections as soon as they are fully deployed.
Comments/Clarifications from PJB
PJB contacted me via email with the following clarifications. I have included them for completeness.
On Sun, Jun 7, 2026 at 5:22 AM Pieter-Jan Briers wrote:
these PRs were merged anyway against maintainer policy.
Incorrect. Maintainer policy explicitly allowed Wizards to override the regular review procedure.
After this, PJB transferred ownership of the Discord to DrSmugLeaf and took a break.
Entirely incorrect and I have no idea where you got this from. I did not go on break at all here.
During this ordeal, long time admin CptJeanLuc was banned from the Wizden server for providing constructive feedback.
They were banned for trolling the discussion and acting in blatant bad faith. If you want a public log, this is further reflected in their behavior in subsequent PRs they made. Furthermore, they were later re-banned by the rest of Wizden staff entirely without my involvement because they were a dick and I was right to ban them.
Shortly after this, the Auth servers and forums were taken down with PJB claiming that they were “hacked”. My current understanding is what she means by “hacked” is that the Current Wizards’s Den Project Leads had shell access and were using it to take backups of the server which is why I placed it in quotes.
WizDen staff has boasted about using a backdoor for this purpose. They did not have normal shell access and whatever method they used was entirely unauthorized.
My response to her corrections
After this, PJB transferred ownership of the Discord to DrSmugLeaf and took a break.
Entirely incorrect and I have no idea where you got this from. I did not go on break at all here.
I interpreted leaving the server and passing off control as taking a break from upstream. I don’t think it particular matters what you call it.
In regards to the other points I stand behind what I said based on my understanding of the situation.
Errata
You can view a diff on at git.notaslug.org/notaslug.org.git/.
- Corrections based on information from Princess and Aexxie have been included.
- Sat Jun 6 11:27:52 AM CDT 2026 - Removed text regarding the “beg” message that was outdated.
- Sat Jun 6 12:28:03 PM CDT 2026 - Changed some information about the admin walkout after talking to CE and added some minor corrections per CE.
- Sat Jun 6 12:43:49 PM CDT 2026 - all admins -> active admins in the admin walkout section per Skarlet.
- Sat Jun 6 01:34:00 PM CDT 2026 - Slightly changed the wording of the admin walkout section again on advice of Nik and Poop Sticks.
- Sat Jun 6 01:59:17 PM CDT 2026 - Removed Open Dream link and added links to CptJeanLuc and CE’s articles.
- Mon Jun 8 06:15:00 PM CDT 2026 - Updated with PJB’s comments. Along with fixing some grammar and formatting issues.
-
These are currently archive.org links since as of writing this the forum is down. ↩︎
-
A copy of this letter is included in PJB’s form post. ↩︎
-
Link removed since the opendream folks do not want the added attention. Please do not harass them. To clear up any misconceptions, no data mining was done. A colleague actually saw the conversation live as it happened. ↩︎
-
Non-public names and information has been redacted by me to prevent disturbances. ↩︎