In prior versions of Roblox, there has been a folder named DeveloperFramework inside /content/textures. This folder contains many miscellaneous icons such as checkboxes, arrows, etc. Even the developer console uses it.
For an example of impact, this affects the open-source projects Iris and Live-Game Explorer.
Repro
Open the Developer Console in any game you have Team Create access on and open the console. Notice there’s no arrow on the Log & Client/Server buttons.
Alternatively, open the Iris demo place.
Info
OS: Windows 10
I have confirmed that I am not running Bloxstrap or any other Roblox bootstrappers.
I have reinstalled Player just to make sure.
A friend has confirmed he experiences this issue ingame as well, on Windows 11.
Expected behavior
I expect these icons to be present so UI that relied on it doesn’t have missing images. If Roblox is no longer interested in shipping these icons, I expect either a network fallback or a developer notice
AFAIK relying on rbxasset images has never been supported behaviour, especially considering some spritesheets like FoundationImages change almost every release.
If the developer console didn’t (try to) use them and Studio didn’t still have them I’d be inclined to agree, in this case it feels like a mistake hence me reporting it as a bug
Thanks for flagging this. Especially for Iris, since I expected we are allowed to use an assets in the content\textures\ folder. Ideally Roblox can fix this, otherwise I’ll upload the assets normally and change Iris to use them.
Please do so, at least as a fallback for redundancy. This is making it fairly difficult to use Iris, and it looks like Roblox isn’t fixing it anytime soon. Thanks a lot
You might have to contact a roblox ui developer directly as ive been noticing bug reports being ignored. I got 2 bug reports that got ignored and had to directly contact a roblox staff to get them to work on it.
“DeveloperFramework” assets were recently deleted. We weren’t aware they were being used in the developer console. Are the missing assets breaking any functionality in the developer console or is it just a cosmetic/useability issue?
Could folks clarify if and how they are accessing these assets outside of the built in Developer Console? It seems folks are using these assets in their games? I’m unfamiliar with how this is done and if its common practice.
Since the “DeveloperFramework” assets were for internal use only. It was not intended for us to be using those assets in the developer console which is why they got mistakingly removed. We will try and put them back in a non-internal use only location.
In general, I’m unsure if assets built into studio are officially supported. It would definitely be safer just to upload the assets yourself. Perhaps someone else from my team can chime in with an official answer!
It’s not terribly uncommon. I don’t operate any of the third party tooling I highlighted in my topic, but as a developer, I feel it is more forward-thinking and simpler to use already existing local assets, especially with recent asset privacy changes and the fact that they are accessible offline. This is often done with the default Roblox sounds, as an example.
You can use these local assets via setting the asset uri of an instance to rbxasset://PATH_TO_ASSET instead of rbxassetid://ID. Assets | Documentation - Roblox Creator Hub explains a bit more. Here’s an example of how they are used in Iris (shown here is the commit that removed the DeveloperFramework textures):
Thanks for responding. It’s just a cosmetic issue, since any buttons or other UI elements will still interact correctly.
Regarding the content folder, there are multiple reasons for using assets provided by Roblox:
They already exist and I don’t need to upload them. Generally speaking, it’s quicker to assume Roblox has a particular asset and search through the content folder, then it is to find one online and then upload it.
Other Roblox instances use them by default: the SpawnLocation decal, ScrollingFrame scrollbar images, Sky skybox, sun and moon textures. These are the default, and considering you can read the full path, an assumption would be made that you can use any assets under the content folder.
Lots of the assets in the content folders are very old and outdated. I would assume that they are left there for compatability reasons, which would give the impression that any assets put within that folder will be kept, unless Roblox has a really good reason. Considering that the Tix and old Robux icons still exist within them, years after becoming obsolete, along with other legacy assets implies that there is a strong amount of backwards compatability and it is safe to trust they will continue exist.
For Iris, all of the assets are generic UI elements (triangles, crosses, checks, etc…), which are common enough in any UI that the ones Roblox provides would do the job. In an actual game, I would upload them, but for a debug tool which isn’t generally designed for players I wasn’t picky.
Realistically, it’s not that big of a deal, and I can just upload them myself, but there’s a strong amount of safety knowing that the assets you are using will always load: say, if your internet goes down temporarily during Studio; and any rogue moderation won’t break them, preserving the code long into the future.
Again, it seems like Roblox’s strong commitment to legacy code compatability, would ensure that any assets which have been released would remain available. I don’t know if any other games or tools use these assets and whether it’s a problem for them.
Thanks for reporting this. After thorough consideration, we’ve made the decision not to address this particular issue. We understand this might be disappointing, and we appreciate your understanding. If you have other concerns or questions, feel free to let us know.
