Roblox update 735: what changed
Contents
Roblox update 735 shipped on 20 August 2026, and almost all of it is aimed at people who build games rather than people who play them. The notes are split into two sections — improvements and fixes. Below we retell them in our own words and flag honestly where Roblox itself says a change is still rolling out.
What this update actually is
Roblox does not ship “big patches” in the usual sense. The platform updates in small portions, and each portion gets a number and its own notes page. If this format is new to you, start with how platform release notes work — it explains why most entries read like function names rather than feature descriptions.
Many entries in 735 carry a Pending label. That is not a translation slip or our guess: it marks changes that are documented but still rolling out. For you it means one thing — you may not see them on your account immediately.
Animations: managing input pins
The most visible part of the update concerns animation nodes. A set of new methods arrived for working with input pins: add a pin, remove a pin, get the ordered list of their names, set that order, plus a separate event that fires when the set of pins changes.
In practice this means the structure of an animation node can now be rebuilt from a script rather than only by hand in the editor. If you build animations procedurally, a whole class of workarounds disappears.
Collections and tags
The collection service gained a new entry point — a dedicated method for creating a collection. Previously work with tagged objects started from other methods; now there is an explicit call for creation. The entry is labelled Pending.
Audio: occlusion and reverb separately
Classes and services with acoustic simulation enabled now have subcategories. Occlusion (sound muffled by an obstacle) and reverb (room echo) can therefore be enabled and disabled independently of each other.
This is a small thing until you build a large location with acoustically different zones. Then separate control saves a great deal of time on tuning.
UI: shadows, gradients and text boxes
Several changes cluster around the shadow element:
- a shadow can now be affected by a child gradient — so it can be coloured with a transition rather than a flat fill;
- an inset shadow property was added, drawing the shadow inside the parent element;
- a separate toggle was added for showing or hiding the part of the shadow that sits behind the parent element.
Separately, about text boxes. A box that cannot be edited now lets you copy its text on mobile without bringing up the native keyboard. Previously, trying to select text in such a box pulled in a keyboard nobody wanted in that scenario.
Script editor and image work
Autocomplete in the script editor learned to swap a dot for a colon where method-call syntax requires it. If you are only just picking up the Luau language, that is the mistake beginners trip over most often.
Editable images gained two things. First, a projected sampling function, the opposite of the existing projected draw: the projection defines how texels are sampled from the source texture onto the decal texture. Second, a new blending mode, subtract, which subtracts the source image colour and alpha from the destination image.
Networking and script isolation
A new object type arrived for replicating scripted input under server authority. In plain terms, so that input generated by code reaches the server correctly in a model where the server decides what happened.
The second change is subtler and concerns sandboxes. Scripts inside a nested sandboxed container that declares outside-write access can now reach instances up to their parent container’s isolation boundary. Previously they lost outside access entirely as soon as any ancestor withheld that access.
One more entry: a performance improvement to the call that creates data model content from a mesh.
If all of this sounds too engineering-heavy, start somewhere simpler: first steps in Roblox Studio covers the basic concepts, without which release notes really do read like cipher.
What was fixed
The fixes section is short this time: a case where text box focus sometimes got stuck on consoles has been resolved.
What we are not claiming
- We do not know when exactly the Pending entries will reach every user. Roblox gave no dates.
- The notes say nothing about changes to the player-facing app — not the store, not subscriptions, not moderation.
- We did not add entries that are absent from the official notes. If you see a longer list somewhere, it is no longer the notes for this release.
You can compare this with what changed in the previous release in a separate article.
In short
Roblox 735 is a developer-facing update: new methods for managing animation input pins, separate occlusion and reverb, several shadow properties, friendlier autocomplete and one fix for text box focus on consoles.
Sources: official release notes, developer forum mirror.
Frequently asked questions
When did Roblox update 735 come out?
It appeared on 20 August 2026 through the official developer channel.
Is this an update for players or for developers?
Almost everything in the notes concerns developer tooling: animations, audio, UI and the script editor. Players will not see a new button in the app.
What does the Pending label mean?
That is how Roblox marks entries that are already documented but still rolling out. The change may not reach everyone straight away.
What was fixed in 735?
The notes list one fix — text box focus should no longer get stuck on consoles.
Where can I read the source?
The official notes live in the Roblox creator documentation, with a mirror on the developer forum. Both links are at the end of this article.