devtrackers.gg
Whatever that excuse was, it's not a good one, lol.
There's literally 0 reason to not do it this way.
Whatever that excuse was, it's not a good one, lol.
There's literally 0 reason to not do it this way.
It was basically - "The systems aren't built to handle this" and "there's significant differences between prisms and other examples"
However, when the question was raised, I think they were answering in the context of Ascension Pass skins, which I can kinda see making more sense (even tho I still agree they should be together lmao)
Also I don't even think it's an excuse tbh, I just really don't see that as a priority right now, although it would be nice to get the confirmation it will be done at some point in the far future.
Yeah, but I don't really buy that though.
The skins are categorized by numbers and alphabets in the game files, with Skin00 being the default skin, Skin01 being their first skin, and so on. Then you have the letters, which symbolize the recolor/texturing of a skin, so if you have Skin01A and Skin01B, those are recolors of the same skin.
I have a hard time believeing that their system either already can't, or cannot be modified to be able to refer to a different model instead of skin texturing when utilizing the Prism system.
You're technically right - but you're describing something that's kinda like the opposite of scope creep.
I can 1000% buy that the system was designed with only texture swapping in mind as that's typically how game dev would go - the idea to expand it to cover other systems currently in the game probably never got thrown out there during the planning phase resulting in a system that is limited to textures only.
Now, the system can ofc be expanded to model swapping 1000%, but the issue now is that you have to refactor a system that works well and does its job JUST to do a feature that doesn't actually bring you any kind of direct benefit.
Essentially it's tech debt - to be fixed later.