āWhen we say computerā¦ we mean the electronic computer!ā - Knife Party ā404ā
Client Difference Log
API Changes
Added Property string StudioService.InstalledPluginData {RobloxScriptSecurity} [ReadOnly] [NotReplicated]
Added Function string StudioService:GetStartupPluginId() {RobloxScriptSecurity}
Added Event StudioService.OnPluginInstalledFromWeb(string pluginId) {RobloxScriptSecurity}
Added Tag [Deprecated] to Function GlobalDataStore:OnUpdate
Removed Function DebuggerWatch:CheckSyntax
Removed Function StudioService:GetInstalledPluginData
(Click here for a syntax highlighted version!)
I had very low expectations for this bug being fixed and itās ended up in literally the next release after I posted the reportā¦ I guess very cool, haha?
What? Why were these removed without any prior notice? I donāt personally use these controls but I know there are lots of games that do.
As listed in the Release Notes, the Quick Access Menu config dialog now supports multiselect! This has just been enabled.
Before:
After:
Also just enabled is disabled icon support for any instance. Previously only a small, hardcoded list of items (scripts and physics constraints) would have greyed out icons in the explorer when they were disabled, but now this is automatically applied to anything with an Enabled/Disabled property.
This is something Iām worried about too. We have our control scripts forked and like to keep offering these movement modes to players (Why would we remove them if thereās no reason to re-fork the scripts, especially if they offer less options?), it would be worrying if these options are removed from the settings menu and movement mode enums.
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.