Release Notes for 721

Hey all, release 721 is out the door.

I meant to post this yesterday, May 13, but I had some car trouble…

… not unlike Ben Carlin, who completed his circumnavigation of the world by amphibious vehicle on May 13, 1958 in a heavily modified Ford GPA “Sea Jeep.” Various accounts indicate that Carlin was an extremely unpleasant person who undertook the voyage at least partially out of spite and conducted himself poorly throughout. After taking 20 minutes to jump-start my car this morning, though, I suppose I can forgive some irritability from someone who spent most of the ten year journey making repairs.

58 Likes

Every time I think the fun facts have reached their peak, Roblox Staff continue to be funnier and funnier. Cheers, Sashimi!

19 Likes

This is an amazing update! I’m looking forward to see what’s next.

3 Likes

20260514_172844s_wRJ8C6FqPO

22 Likes

Yeah… I had to jumpstart my 2001 Oldsmobile Silhouette after the battery was completely dead.

NO WAY WE GOT UI SHADOWS! MY LEAF BLOWER ACTUALLY WORKED!

I probably blew away the servers with this :joy::joy::joy:

16 Likes

What a great way to get into the fun fact!

2 Likes

And the UI shadows streak returns to release notes!

5 Likes

Where is the device-ban feature, which was mentioned alongside UIShadow months ago?
image

3 Likes

never stop with the fun facts, love you all creator marketing team

My best guess is that they’re trying to create a proper system that’d allow for blocking whilst still allowing access to new users.

You need to consider scenarios when people pass down devices to others, especially in this time of RAMageddon where the prices of electronics are rising up and up.

If you say “ban this device permanently, no exceptions”, that is very, very selfish.

What if the person goes ahead and passes it down to a child, only to have the child unable to play your game (or appeal, in that matter), because of someone else?
You don’t expect the child (who could be 7, for example) to have a Discord account, now, would you?

Or, a device is banned but someone sells it, say, a year or two into the future? Again, that new player would inherit the ban unsuspectingly. Why should the customer have to go through all the hassle of unbanning themselves for something an entirely other person has done?

Yes, it cuts down on malicious users repeatedly using the same device, but in the end, there are more downsides than upsides.

In fact, when I upgrade my own devices, I don’t recycle them or trade them in. Instead, I pass down my devices to others so they can use it.
My younger siblings obviously don’t need Centre Stage or MagSafe, and as such, there is really no harm in passing a device down.

My main point here, is that we need to think of others that could be affected on the side. The Collateral.
(And no, not everyone is willing to, or can afford, to purchase a new device.)

…and that’s why we’re probably still waiting for the feature!

2 Likes

7 Likes

How long until the new class update hits Studio?

4 Likes

I’ve been trying to use the new class feature but it doesn’t seem to be there yet on my end? I heard some people already had it but I’m not sure of that fact

1 Like


Soon…

7 Likes

How dd you get it? I just updated studioa and I cannot use htis feature yet

1 Like

There is nothing else to add here.

1 Like

How do these guys not fail to make us happy and surprise us??

Since when did we have native class support??

1 Like

Is :Evaluate() what I think it is?

Besides that, I hope they add a way to get a list of "frameId"s (maybe thats what :GetThreads() does) so that someone could make a custom profiler plugin. Nevermind, misunderstood the service. Still very cool!

ca6fde54e0bb02dbbf2485971bc86deea94f1eba

720/Last weeks had this. It no longer shows on that or this one :frowning: Any updates?