300 Concurrent Sessions — A New Milestone

April has been the busiest month in Project Rubi-Ka's history. We've hit a new concurrent sessions record, crossing 300 active characters online at the same time.

This wouldn't happen without the players who keep showing up, the bug hunters who dig through every oddity, and the developers who volunteer their time to make it all work — even when the servers are slow enough to be considered a feature in their own right. Thank you, all of you.

Missions Are Live

The headline feature of April's update is one that's been through years of development: Missions (aka. ACG — Automated Content Generation) are now available on PRK.

Rolling missions on Rubi-Ka is a core part of the AO experience, and getting this right mattered to us. Along with the initial launch we've shipped a steady stream of fixes throughout the month; mission doors leading where they should, the Mission Window behaving itself, ghost players staying out of your instance, and a lot more. The new .mishroll command also lets you preview your reward before committing to a roll, at a credit cost reduced by your Breaking & Entering skill.

Mission rolling tools such as ClickSaver and MishBuddy are permitted. For a walkthrough of how missions work on PRK, see this video.

Scaling for Growth — Multiple Play Engines

Reaching 300 concurrent players is not just a feel-good number. It puts real strain on the infrastructure behind the scenes. To keep up with demand, we've added support for running multiple play engines simultaneously.

This is a significant architectural change, and we'll be honest: it comes with growing pains. Keeping multiple engines in sync and reporting consistent state across them is complex work, and there will be bugs while we stabilise it. We appreciate your patience, and as always; use .bug to report anything unusual you run into so we can kill those pesky bugs.

Security Incident

Early in April a vulnerability was found in one of our APIs. We closed it, and wiped all game accounts as part of the planned April 10th reset. Passwords were stored using bcrypt, so the practical risk was low, however a full audit of all systems were done and we're in a better state. We're grateful to the community member who brought this to our attention.

Other Fixes & Improvements

April also brought a range of smaller but meaningful fixes:

• Fixed a credit-theft exploit in player trades
• Fixed an exploit allowing attacks to be redirected at friendly players
• Outdoor zone performance improvements
• Various background stability and optimisation work

The full list is available on the changelog.

Thank You

April was a reset in the literal sense — new characters, fresh start — and the server filled up faster than ever before. That says everything about what this community means to the project.

More exciting things to come! See you on Rubi-Ka!

— The Project Rubika Team

PS. If you'd like to learn more about the project or just look around, drop in to our Discord and say hi!