Ship log — March 2026.
Six releases, two new scripts, and the first public look at rb-housing. Plus the bug we held back from v1.4.2 and why.
Six releases, two new scripts, and the first public look at rb-housing. Here's what shipped, what we held back, and what's queued up for April.
Released this month
rb-mechanic 1.4.2
The headline change is per-player idle profiling — open the in-game /rb_diag panel and you can now see exactly how much frame budget each player's session is costing you. We've already used this to find one regression in the wild (a debug print left on, predictably).
Also: a fix for a long-standing bug where vehicles repaired during a job-complete event could double-count toward the daily limit. If you've had players complaining about hitting the cap early, this was probably why.
rb-vehicleshop 1.2.0
Showroom layouts now support named anchor points instead of magic-numbered indexes. If you've been editing the showroom config by hand, the migration is mechanical — the changelog has the find/replace.
Test-drive routes are now first-class objects with their own waypoints and time limits. The default routes for Los Santos, Sandy Shores, and Paleto Bay ship in the new format. Your custom routes still work; the bridge translates them at boot.
rb-radio 1.1.4
Latency on cross-channel handoffs is down to 8ms from 14ms, which sounds small until you realize it's the difference between feeling like a radio and feeling like a delayed phone call. The change was a single buffer-size tweak in the voice mixer — we'd been conservative on the buffer for a year for no good reason.
rb-hud 2.0.0 (free)
A full rewrite. The widget marketplace is live, the layout editor is finally drag-and-drop, and the entire bundle is 34kb smaller than the 1.x line. If you're running 1.x, the upgrade path is clean — your saved layouts come with you.
rb-inventory 3.2.1
Two bug-fix releases this month, both for the same crash: a race condition between the crafting tick and the durability degradation tick when a player was wearing an item that crafted into itself (yes, really). Fixed for real this time, with a regression test we should have written the first time.
New: rb-housing (alpha)
The big one. After six months of "soon," we're opening private alpha for rb-housing next week. It's the script we've been most quiet about because it took three completely different architectures to get right.
The version that's shipping uses MLO-free instanced interiors — no map files to install, no IPL conflicts, no compatibility surprises with whatever map pack your server is running. Interior layouts are defined as data, the renderer is generic, and players can swap furniture sets at runtime without a resource restart.
It's not feature-complete yet. The MVP shipping next week covers:
- Single-tier instanced apartments
- Furniture placement with snapping
- Per-house storage
- Visitor permissions
What's not in the MVP, but will be by 1.0:
- Multi-room houses with separate door permissions
- Decoration sharing between characters
- Garage integration with
rb-mechanic
If you're an existing customer with a server we trust, the alpha invite is in your Discord DMs.
What we held back
There was a v1.4.2 patch ready to ship two weeks ago that we sat on. The patch fixed a small visual bug in the mechanic UI — a one-pixel border misalignment that nobody had reported. While testing, our QA pulled on the thread and found that the same change subtly altered the click-target for the "complete job" button on touch devices.
It wasn't a regression in the change itself — the touch-target had been wrong for months — but rolling a fix for the cosmetic bug without also fixing the touch issue felt wrong. We held the patch, fixed both, and shipped them together.
The lesson, which we keep re-learning: small patches are rarely as small as they look. If you're not sure, hold.
April preview
rb-housingalpha → public betarb-mechanic1.5 — long-promised dealership API- A new script we haven't announced yet (it'll surface in the changelog when it does)
- A complete rewrite of our docs site, which is what you're reading
If you've got requests, the Discord is the right place — we read every channel and feature requests with three or more 👍 emoji go into our triage queue automatically.
See you in April.