this is actually awesome, and i love how many changes here actually really improve things all around. thanks for these changes!
Weirdly enough, this is for FFlagEnableControlsEmulator
I would assume so, considering that it “clones” the instance, but doesn’t include the children.
As of this update, replication (StreamingEnabled) has apparently just broken, at times completely stopping from streaming-in an area.
Yes, as with :Clone
, UniqueId
and some other internal properties are not copied where appropriate. It also cannot copy protected Instances like Players and Instances which have to be created in a specific way like DataStorePages.
It’s appropriate to simply think of it as “clone but without the children”.
Note: This has to ship on all platforms before becoming available so it’ll be a few weeks.
Cannot wait for ‘This will not be released to users at this stage.’
never seen in my life a meme in a official devforum post.
If you keep an eye out for the more subtle ones there’s actually quite a few of them out there.
update log 2 of asking for mouse side button input support
BANNING APIS POG, hopefully we can ban alt accounts too
what does this even mean
Would there be a brand new service or new methods for the Banning players system?
I mean the astronaut guy is still alive so I guess they might not be
Good question, if it was a service, that would probably be included in the notes but I don’t know, hopefully it’s something as simple as player:Ban() and you’re done with it ngl. The first person to make a ban manager plugin with this is also gonna be mega rich
Right now they are methods for the Players service:
This of course might change though
EDIT: Fixed typo
Oh it’s a method of Players (and not Player?). It wouldn’t make any sense for it to be a method of Player because, how do you unban a player if the player can’t join the game…?
Expected it to be a service though
This looks good, but It doesn’t seem specific within the config
parameter, as I assumed it would contain Reason: string
and Player: player
, I don’t think the Duration: number
is necessary since you can just do UnbanAsync
when a certain duration ends, however, I thought UnbanAsync
would just have Player: player
I remember just a few years ago, Roblox was completely opposed to developers banning. I’m glad that they finally came to their senses!
Engineers get to enter public release notes for the changes they make. Sometimes they enter something like that and the person compiling the release notes misses removing it as not relevant.
This fix was specified earlier in Release Notes 617, word for word.
Does this imply that it’s being delayed?
Yes, it is indeed tied to the Players
service.
As for the banning API, how exactly does it work and what results can we expect?
Right now, to “ban” a player we use :Kick() and datastores.
With this API, what’s exactly is going to be different? Can the player still enter the game through the app/website page? Are they informed of the ban only until they join the game?