THE SHORT ANSWER
Roblox 744 introduces CollectionService:GetCollections() for scripting, moves collision fidelity changes to async with a progress indicator, fixes a Studio memory leak where destroyed parts weren't freed after rendering, corrects a HipHeight=0 spawn bug that affected SLIM avatars, defaults hand-authored places to Future lighting, and patches Luau --!native crashes on Intel Macs. Avatar generation from text prompts enters beta.
- CollectionService:GetCollections(Instance) now live — returns every tag collection an instance belongs to.
- Collision fidelity and precision changes run asynchronously with a Studio indicator.
- Studio memory leak fixed: parts destroyed after rendering are now freed, ending RAM growth across Play/Stop loops.
- HipHeight=0 spawn bug resolved; avatars no longer sink and slide, especially with SLIM enabled.
- Places without explicit Lighting.Technology (e.g., .rbxlx, Rojo) now default to Future instead of showing migration dialog.
- Luau --!native crashes on Intel MacBooks patched; subtyping bug in new type solver fixed.
- Beta: generate avatars from text prompts; detailed avatar creation progress reporting added.
New Scripting API and Luau Fixes
The only live improvement in 744 is CollectionService:GetCollections(Instance), a method that returns every tag collection an instance currently belongs to. This gives developers a single call to inspect all tags on an object instead of iterating known tag names.
On the Luau side, the new type solver had a subtyping bug that could inject a spurious nil into the lower bound of a generic type. That is fixed in the pending branch. A separate engine bug where a rejected yield could later resume the same thread at an unrelated suspension point is also resolved.
Studio Workflow and Memory
A long-standing Studio memory leak is finally addressed. Parts that had been rendered — including every part in the playtest client's Workspace at each Stop — were never freed after destruction. Repeated Play/Stop cycles caused Studio's memory use to grow without bound. The fix ensures destroyed parts are properly released.
Other Studio changes:
- Avatar-based icons in the Explorer have been modernized.
- An extra X button in the derives panel of the Style Editor has been removed.
- Hand-written
.rbxlxfiles and Rojo builds that don't specifyLighting.Technologyno longer trigger the Lighting Technology Migration dialog; they now default toEnum.Technology.Future.
Avatar and Character Fixes
A regression where Humanoid.HipHeight could spawn at 0 caused avatars to sink into the floor and slide uncontrollably, often unable to move. The issue appeared more frequently in experiences with avatar SLIM enabled. The fix restores correct HipHeight initialization.
When a character dies, the camera's viewable scene should no longer stream out completely because the Humanoid.RootPart falls away. This keeps the death camera stable.
Physics, Rendering, and Networking
Collision fidelity and collision precision changes now compute asynchronously instead of blocking the main thread. An async indicator appears in Studio while collision geometry is being generated.
Outgoing input replication bandwidth for Server Authority has been improved, which should reduce network overhead for server-authoritative movement.
A Clouds visual bug in Studio — visible when coverage is high and Editor Quality Level is set to Automatic — is fixed.
Luau Native and Animation Graph
--!native compiled code crashing on error on Intel-based MacBooks is resolved.
Enum.AnimationValueNodeType.Expression is now available in Team Create places enrolled in the Animation Graph State Machines beta; previously it was missing in collaborative sessions.
Avatar Generation Beta
A new Studio beta feature allows generating an avatar from a text prompt. When detailed-progress flags are enabled, avatar creation can report generation status, thoughts, and narration inputs, giving creators more visibility into the pipeline.