Convert numbers to assetids automatically

[THENOMNOMMONSTER55 (egg)]

if a number is passed into an instance that needs some kind of id (think Sound.SoundId or MeshPart.MeshId) and not the full “rbxasset//:id” convert it automatically instead of throwing a “Failed to load sound [id]: Temp read failed.” error

[CraX_573]

I can’t find a reason against this. If studio can autocomplete when you paste a number in, why can’t the client/server do the same?

Although I will admit this kinda leads to bad practices I do agree it seems odd it’s not coded in as that level of failsafe

[TheGrimDeathZombie (Reapimus)]

@CraX_573

I can’t find a reason against this. If studio can autocomplete when you paste a number in, why can’t the client/server do the same?

They’ve shutdown similar feature requests before because it introduces unexpected behaviour and bugs that are hard to track down.

NumberRange, NumberSequence, and ColorSequence properties should accept numbers & Color3s

Many of the type coercions exist only for backwards compatibility reasons and we are strongly discouraging using them. In fact all of your examples give script analysis warnings. We are also introducing more runtime warnings so that developers stop relying on many forms of type coercions and make their code better. Relying on type coercions absolutely does incentive bad code and cause developers to unknowingly introduce bugs to their code that are hard to track down later. For these reason…

[THENOMNOMMONSTER55 (egg)]

okay fair enough i do get how it could encourage bad practices, how about making the error message if you do input an invalid type more verbose though? just throwing a temp read failed error isn’t the most helpful, maybe something like “expected rbxassetid:// got [type]”?