Hi there, I think it would be great if you could find a way to actually delete things instead of making them obsolete. I know, it will cause problems with some 15years old games with 40 CCU that won’t receive any update but whatever it’s their problem they can just log back in and do the update
There’s not only scripts or methods that would need to be cleaned up but also all the old Roblox UI, useless files etc we can find ourself when digging up into Roblox Studio folder.
This and also update some of the old Roblox code you can find, come on what is this :
I 100% agree with this gentleman. You guys should realize no one plays old games anymore, it’s time clean up Roblox from those deprecated troubles makers. That was all for me have a great day.
Games that never received an update are unplayable because you now need to submit the Maturity & Compliance questionnaire. If the devs had time to submit it, they have time to just update 2 lines in their scripts. So no, it’s not an issue for old games that never received an update.
You don’t know the impact full-on feature removal has until it affects you.
I agree that the engine carries a lot of clutter from legacy features, but removing them would impact and damage way too many games. When you use a game engine to build a game, you expect that game to work tomorrow & 10 years from now.
That said, yes, Roblox should modernize and improve their CoreScripts. That has my full support.
I still don’t quite understand the “why” here. If you find certain documentation or tools cluttered with deprecated APIs, maybe the feature request would be to improve those surfaces and hide the APIs.
Hey there, feature requests should ideally be about problems. It’s hard to understand what the problem is here. I recommend updating your title/post to explain a specific problem you’re having as a result of “old, unused, deprecated code”. This isn’t very actionable as-is.
This is a horrible idea, whether or not you like it, deprecated code is required to keep many many systems in many different areas working correctly. They can’t just “delete old code” it doesn’t work that way. They could potentially upgrade some inefficient code but, deprecated things are marked as deprecated for a reason. It is most likely that deprecated code isn’t running unless it’s being used. I’m sure some of it has some overhead but again, it’s not something that can just be removed without major issues.
Not to mention this…
that is just flat our wrong, there are games that are owned by developers no longer alive, games owned by users who haven’t been on the platform in many years, games so large that fixing everything deprecated isn’t possible. The issues go on and on and on, not to mention the backlash from the community. It’s the same situation we saw with R6 when it was being planned for removal, so many games still rely on it, new/old, it doesn’t matter, R6 is widely used and isn’t going anywhere. The same could be said for some of these deprecated features. I know I have used some of roblox’s most obscure and/or deprecated features in projects, things like, FloorWires, Mouse.KeyDown/KeyUp, SkateboardPlatforms, Humanoid.LoadAnimation, Holes, Hats, Old raycasting functions, you name it.
Not fan of this, but agree. This change is needed. With keeping all of old code, Roblox will end in future in a lot of junk items left, which no one uses anymore, but kept for the sake of the history.
While some items, like BodyMovers should be kept (cuz they used very frequently even now), things like flags should be removed (for capture a flag game).
something called “memory usage” exists. Maybe one useless instance won’t do much, but if you combine every useless instance/function etc you can see the impact.
(They also make making new things harder due to code organization for the people working at roblox)
things from 2010 which probably don’t even work anymore are “every other update”?
no new game uses flags and hats bro
and the old games are literally broken anyway
If these things actually had the meaningful impact you claim they do, Roblox would have almost definitely removed them entirely from the engine already.
This is a really odd and downright ridiculous point to try making. Roblox should (and I believe, does) have very good code organization to the point where this is a non-issue and it’s pretty dead simple for them to locate pieces of the code they need to work on.
15+ year old code which is not removed or modified almost at all wouldn’t cause issues?
For example, the core gui has tons of pointless unused UI instances (100+), each of them has properties. They aren’t needed yet they take a little bit of memory which is something completly avoidable
I honestly don’t think we should limit ourselves because we have something that must work even though no one uses it anymore or only a really small minority of people do. You guys want backwards compatibility, sure, but then you agree with having an engine being more and more dirty in the time because we have to think about the small percentage of people that would like to continue doing something that’s not even a thing anymore.
This right here is proof you have no idea what you are even talking about, you say “there are so many non needed stuff. It’s just slowing down our games” while using a screen shot of CoreGui full of things required for roblox to function
the Flag instance isn’t going to cause your game to lag, it isn’t slowing it down, and the memory it would use is very small.
Like @TheGrimDeathZombie said
Most of these instances/functions don’t limit roblox, they just add backwards compatibility. The limit to roblox is artificial, it’s set by the target devices roblox supports, which is a very long list of really old phones. That is what limits roblox, but mobile is their biggest market so it makes sense.
:
