Release Notes for 702

[EndlessSashimi]

Hey everyone, we have a bit of a shifted release schedule this week, so 702 is out the door! This should be the last release of 2025 – wishing each and every one of you a safe, happy, and warm holiday season.

https://create.roblox.com/docs/release-notes/release-notes-702

[VegetationBush (FartedWayTooHard)]

Will be be seeing constrained generics in the new Luau type solver soon? Generics are amazing, but sometimes (especially for mathematical functions), just generics aren’t enough:

-->> doesn't work; warns
local function add<addable>(a: addable, b: addable): addable
    return a + b
end

But if we can constrain the values, perhaps something like that could work:

-->> works!
local function add<addable: Vector3 | number>(a: addable, b: addable): addable
    return a + b
end

[Crazyblox]

It would be beneficial for the team to begin providing Luau type solver updates in their own category separate from engine API updates as they are interleaved sporadically across improvements and fixes, because the way it stands it makes it hard to flick through all the release notes when looking specifically for type solver updates.

If you want an even more elegant solution, post a link to the Luau github repo’s release notes for anything Luau-related as that would more clearly define what is engine specific and what is Luau specific - That could be a step forward for allowing the Luau team to make use of github’s issue tracking rather than letting them be lost to time, like this one here: Incorrect warning requiring an optional key to be provided by table returned by function · Issue #521 · luau-lang/luau · GitHub

[TenebrisNoctua (Noctua)]

The team is considering the implementation of generic type constraints. However, I doubt it will happen soon.

[enzogamer123vv (8800GTX)]

They added alpha mode to materialvariants wwww

[galmeowing (quaywin)]

wheres ExampleService, my game relies on its behavior and has been broken since its removal

[avodey (avocado)]

Love all of the optimizations this update! Much appreciated.

This is confusing though:

Why not just do array<number>? What’s the difference between that and array<<number>>? They seem to do the same thing.

[TenebrisNoctua (Noctua)]

[TenebrisNoctua (Noctua)]

https://rfcs.luau.org/explicit-type-parameter-instantiation.html

First, what we absolutely cannot pick:

• f<T>() is the choice of C++, but is ambiguous with f<a, b>(c) in the same way we mentioned with bitwise operators above. C++ only disambiguates this with an extra pass using type information that would dramatically inflate the complexity of all Luau parsers.
• f::<T>(), named the “turbofish”, is the choice of Rust. This is not strictly ambiguous, but it would require infinite lookahead as it conflicts with casting generic functions. In local x = f::<T>(() -> T) -> (), which is valid code today, we cannot know this is a type assignment until we get to the first ), as until that point we might have code that looks like local x = f::<T>((x)). This is not a cost we would like to add to the parser.

[nopesbucket]

I can’t believe IAS finally has Touch inputs! Time to say goodbye to UIS.

Are there also any plans adding TintMask for MaterialVariants to have similar materials like Material.Brick?

Also is this alluding to RunService:BindToSimulation() method?

But good release

[enzogamer123vv (8800GTX)]

I believe the opaque mode will add a opacity map image id type thing uhhhh

[TheGrimDeathZombie (Reapimus)]

Have you considered that the staff members responsible for posting release notes have nothing to do with that update and additionally would have no influence or control over it? You’re just polluting random announcement/release notes posts at this point with spam that achieves nothing.

[nopesbucket]

Ooooh, I assumed that was related to having similar property like in SurfaceAppearance.AlphaMode.
mb, still hope they’ll add something similar in the future.

[enzogamer123vv (8800GTX)]

also roblox where is 4k textures

[HealthyKarl]

What’s the before and after for this?

[Dogekidd2012]

local function f()
    return a<b, c>(d)
end

…is valid Luau code today–it is two comparisons.

[CoffeeAPI_JSON (EspressoAPI)]

There hasn’t been any official docs, but it looks like in the API reference, load character is deprecated and is replaced with two different versions: one traling with Async, the other with Blocking.

For example LoadCharacterAsync() and LoadCharacterBlocking().

This was silently rolled, what were the reasons for this change? Are we planning on migration? What’s the deal with this?

Cheers.

[TheGrimDeathZombie (Reapimus)]

LoadCharacterBlocking has existed since 2017 and is probably used for something internal seeing as it’s not accessible by normal code.

[Dogekidd2012]

Nearly all yielding methods have been renamed to add Async() at the end. :LoadCharacterAsync() is equivalent to :LoadCharacter(). An announcement is coming soon, but that is the TL;DR. Old methods are not being removed or broken, just aliased.

LoadCharacterBlocking() exists for internal reasons and is unrelated.

[Evercyan (Cyan)]

NO WAY! Does this fix the long-standing bug reported here, where particles not in front of an opaque pixel would appear washed out, lacking any color??

This has affected so many accessories & gears for the longest time now (Periastrons, Crescendo/Telamonster, Fiery Horns, Seasonal Fairys, 8-Bit Series, Sparkling angel wings, the dozens of off-sale particle items).

So happy to see this finally being resolved if I’m understanding correctly

---

I’m curious if particle items will also have their thumbnails force updated in this fix, as Crescendo still appears white, but the fire is actually red.