#Upcoming API change: Tools become Models
1 messages · Page 1 of 1 (latest)
makes sense
e

yeah
though how will tool properties work now
finally
idek if this is good or bad
like always
interesting
oh shit this is fucking great actually
it just changed superclass
multiple layers of classes are op
the tree would look like Instance -> Model -> Tool i think
rather than Instance -> Tool
so we have access to shit like tool:GetPivot() i think?
yeah
i don't know how to feel about the pivot being the weld point
i liked it a bit better before but ig it's no big deal
odd change but ok
wdym
The change is only for back pack right? Not tools because sometimes I have to detect the class inside the backpack
i think you misunderstand the change
this changes what you receive from the Roblox assets api
Ohhhh
previously when you used the Roblox assets api to receive some gear it would come as a tool, now it will come as a model
np
I think all the admin give command must be updated
It's a good change but I will have to update all tools in my games 😔
what why
FindFirstAncestorWhichIsA(“Model”)
💀 rip
Pain
Roblox should srs fix this
Like why can't they make the updates optional?
Why is there only 1 version of studio 💀
updates dont excuse your poor coding
its kinda mean I know its a standard but they said they are looking to automatically update that code
theres many times that roblox shouldve done that tbh
idk why they didnt do that before when they have access to our code lol
there has to be so many edge cases though
if they made this optional they'd have to offer two different endpoints
this is better in the long run. mostly everything you receive from the asset api is stored in a model and it makes sense to add more kinds of assets to that norm
lets developers rely more on this line of code and not have to make an exception for certain kinds of assets
But old games break
When you develop a game you pick 1 engine version and stick to it permamently
No issues
well it's up to the developers to keep up with changes. roblox moves forward and innovates, developers have to keep up and do the same, that's the life of software engineering
No its not
yea, it is
the world of programming is always ever changing, you can't rely on your code to work forever unless it's extremely low level and decentralized
And its a bad thing
Yes I can
i think roblox would be a horrible platform to develop for if things were still done like they were in 2006
If my game made in cryengine 3 still works I dont see why a game I released !!! last week already needs to be rewritten
If roblox wants to make those changes they have to announce them ahead of time
This isnt enough time
they always give devs time to make changes
Cap
idk dude it takes like a minute tops to adjust to this change unless your code is written extremely poorly
that's usually the case
and yeah admittedly roblox makes controversial changes developers don't agree with, but the purpose is always to innovate. if you want software engineering to be your thing you need to know how to adapt
ask any full time dev and they'll say it's true
That's not innovating
The tool property is trash in general
This does nothing relevant
If someone makes a game
In ue3
They're not going to want to switch to ue5
Its common sense
Some games benefit from legacy tools aswell
what about rocket league
Rocket league is owned by epic games
Look at fortnite
The switch to ue5 was terrible
And its an AAA studio
Imagine how many resources it required
On roblox u dont notice it cuz the changes are spread out thru the year
But in reality its just as terrible as that
See
Even ue5
Actually has legacy tools
And yet most of us would say theyre innovating aswell
Even tho they keep all the og stuff