Howdy howdy! Release notes for 668 are here!
Since a “.” in the require string stands for a parent why not make it so we are able to do:
local MyModule = require("/MyModule") -- Works the same as require(script.MyModule)
I think it would be better than having to do this:
wasn’t mentioned in the release notes but YES
Does the deprecation of special treatment of Init-named ModuleScripts mean that they’re walking back the decision they made to allow requiring containers if an Init ModuleScript exists in it?
I’ve been waiting for this for so long, glad it’s a real thing now. Always had plans in the back of my head to make some multi-controller party games on the big screen.
FINALLY
Love you guys. We’re so back.
Looks like we’re getting close to the release of VideoPlayers.
what do you means it already exists…
It’s different. We currently have VideoFrames, which play 1 video in their frame (duh), but there is an upcoming VideoPlayer and VideoDisplay instances. They kind of act like the new audio APIs, where you can have 1 VideoPlayer connected to multiple VideoDisplays, and (probably) being able to hook them up to audio effects as well
now to suggest a feature: allow streamlined control of surfaceguis like this B)
you have no idea how cool it would be to have a surfacegui that is connected to multiple adornees
Still no gpu support or more actors ? Anyways woah so many kinda oop updates
That would be neat. I was thinking more about how ViewportFrames should somewhat act like this too (or maybe Content.fromViewport? so you can use a static texture from the viewport in an ImageLabel?) but SurfaceGuis would make a lot of sense.
I think itd be neat of them to add LightEmission or influence for videos and images onna surface so we cab have TVs and ptextyre Sugns or even Windows that have advanced glow, emission and light effects like in UE5. This would allow to have a Video or TV reflect realistically or have multi-colored lifht effects on a wall its facing kr near depending on the colors shown.
Would be cool if require-by-string worked if you used :GetFullName()
on a script.
A large part of the goal of require-by-string is to allow code to be used between Roblox and non-Roblox Luau environments.
In non-Roblox Luau environments, your code reads as requiring directly from the root of the system (I don’t know if that’s the actual behavior, but it certainly reads like it does).
Split screen coming to the Blox…
HOORAHHHHHHH
What why? What’s the point of doing that in the first place.
Better yet, we should just be able to do require(“child”) for consistency and convenience.
If the @self alias does not exist in non-roblox environments (unless I’m an idiot and just couldn’t find it, which I probably am lol), wouldn’t the better route be to make it more consistent and convenient for the developer?
can you tell me what does this mean ?