I have heard that, and the mock-up showing a dynamic head switch is promising. however, I still am not entirely sure what this will mean for new users.
if the optimistic answer is the correct one here, though, this is shaping up to be a really great Roblox update
I wouldn’t say its amazing update exactly, I gauge it closer to how the layered clothing went (not many people like/use it), but it is a major improvement over what was originally shown and that makes it an, ehhhh, okay update.
Roblox could’ve stopped this by just telling us all the info rather than withholding as much info as possible
thanks roblox for letting me know that an American billionaire company will use my camera every time I play roblox + even more battery drain, I really appreciate the updates which are a laugh and nothing else.
I have no idea why so many people don’t realize that:
Your camera isn’t going to turn on by itself
You can change your head shape to how it was, so your accessories won’t be messed up
You can disable dynamic heads to turn your face back into a “static” expression
And judging that these features seem to be in beta testing, Roblox was planning to release these anyway. I think they may have jumped the gun in announcing this update, but it was planned at the start for players to select a head shape and move accessories. These features don’t just materialize in a few days.
I really do not understand why you guys are forcing this update to us…
I mean don’t get me wrong the Idea SOUNDS cool but the execution is terrible…
Instead of taking all faces off-sale, make a separate category, so that people that WANT to use these can use them.
There is no absolute reason to do this. Most of the community doesn’t even use these faces in the first place! ( Except people that wear them )
First we had to verify our Identification for voice chat or whatever, and now we need to trust a company with our real life camera movements for silly avatar animations? Although these are optional, I’d love if this was also optional, although it doesn’t seem like it when we are going to be forced to use these by next year.
Taking the faces that were uploaded since the dawn of time and were seen as legacy off-sale, you’re basically taking a part of history, which nobody likes to be honest. ( Not blinded by nostalgia, just really confused )
I love these small ideas but please focus on OTHER things instead of forcing an update that barely anyone uses.
We were told an update to the audio last year, oh well guess that didn’t happen.
We were told a few other cools things, guess these also magically didn’t happen…
TLDR: Cool idea but terrible execution like I said.
This is a very bad idea. The dynamic faces DO NOT support R6 and they look out of place. Please put the classic faces back on sale and please don’t repeat past mistakes (rthro).
I don’t think you understand what you’re saying here.
You own the intellectual property of the games you publish. Of course there’s fine print for engines such as Unity or Unreal, but those kinds of agreements aren’t something developers have to accept for game design as a whole for every modern game engine.
If you take your business elsewhere, and you aren’t publishing unsavory content, you retain rights to what you publish, depending on the distribution platform of choice.
Have you heard of peer-to-peer networking, or community-hosted servers? Older COD games like WaW are no longer possible to play legitimately without community mods, and it’s because of how the game was compiled. You don’t need centralized servers to have a multiplayer game up forever, and you don’t need servers for single-player games either.
Again, depending on the choice of distribution service, which is at the developers’ discretion, you may do this. My point was to illustrate that streaming content is not the only way that games work, and you don’t seem to have understood why I brought this up in the first place.
In which case the developer base will move on, and such a choice could impact Epic financially. There are alternative engines besides Unity or Unreal which show no signs of going away, and neither do these engines given their hold on the industry. No company worth their salt would even entertain the idea of closing off a stream of revenue.
What’s happening now is gross negligence on the part of Roblox higher-ups, ignoring community feedback, and failing to uphold their promises. The mistreatment of the developer base is telling enough that Roblox does not actually care.
Also, my point here was to illustrate the importance of preservation, something that Roblox does not care for, either. Decades of Roblox’s digital history will go by the wayside, with each weekly update deteriorating the games on its platform. This is a very bad thing for any living piece of software - you don’t see this anywhere serious programmers work.
And even if a codebase has to be refactored, you are typically not forced into accepting an update which breaks code.
This whole tirade of mine is trying to illustrate that Roblox forces change onto the community, and unless you’ve been conditioned to feel okay about that, any developer who wants to do serious work should choose a serious game engine. Until Roblox changes their methodology with regard to updates to their engine and platform, which I don’t see happening, I don’t see any reason why rational game developers would want to waste their time with apathetic management.
I mostly agree with your post, but there are a few points I’d like to comment on.
Nearly every update has some way to opt-out, and this update is no different. You can disable animated heads/faces in your own game. Animated heads are also optional in general (for now, and hopefully forever). Though I will say that it’s a bit much to require all devs to stay up-to-date with all changes at all times. This is why I would suggest that most new features, mainly those that would actually cause things to potentially break, should be opt-out by default. This does seem to be the case for a lot of things thankfully, but I would like to see it applied more often.
I don’t find this to be all that true. The only update to truly destroy that much history was the FilteringEnabled update, which was obviously a much needed update that had to happen. I would argue that it actually gives the original devs a chance to re-release their games as well, if they so choose. Or for new devs to try their own spin on classic games.
This part I won’t deny. Many of their choices have been less than ideal, and I hope to see continued improvement in this area. However, as long as new updates remain optional and have the ability to opt-out, I’ll still be satisfied. Though I won’t stop wishing that Roblox focus more on features that players, and especially devs, are asking for.
I don’t think this is entirely true, though not entirely false either. But the main thing is that it’s simply unrealistic. To preserve every game in a playable state, it would need to remember the version used. That alone is fine, but it’s the fact that this is an always-online platform that’s the issue. You can’t just have outdated versions existing when there are live services and policies to keep functional and up to standard. This is why having new feature updates opt-out by default is ideal. However, this excludes essential updates like the FilteringEnabled update.
You should also keep in mind the services that Roblox provide to you. That includes infinite data storage, infinite server hosting, currency/sale system, cross-platform, and plenty of other services. (Obviously I don’t mean truly infinite, but you get the idea.) I won’t deny that Roblox has some downsides, but these services are also very useful. That is why I, for one, choose to continue using Roblox.
My counterpoints were mainly from the perspective of the player, since I myself would consider myself more of a player than a developer (I really only develop for fun once in a while.) But thanks for the reply nonetheless!
Most features that get phased-out go through a sunset before either deprecation or a plain refactor.
You have to create BodyMovers via commands or scripts to place them in the explorer, which is irksome since there are no complete analogs between those and the new physics constraints.
The My Feed page is gone, making group shouts pointless.
The animation update is no longer opt-out, and the sound update was promised to be addressed further but there has been no indication of commitment towards that.
All of these are cases of Roblox just not caring enough to keep things consistent across versions, which is very disappointing coming from a billion dollar company.
That is true, though not every game from yesteryear gets its deserved justice. Some developers just don’t care enough to upkeep their games, and the third parties who have the capability to spin them may not even be aware of some older games.
I wouldn’t hold my breath on this. Unless direction changes at Roblox, I don’t see this happening any time soon.
Are we unable to have versions of the engine from certain time periods? Before Roblox did to Finobe what Nintendo did to Brick Bronze, Finobe had older versions of Roblox available to use. Why can’t Roblox do the same? With the functionally “infinite” resources you claim they may have, shouldn’t they also be able to host older versions of Roblox just the same, if not exceeding what Finobe had?
All of this to say that I distrust Roblox, given their repertoire. An update like this is sure to put more work on developers if they just want to keep things the way they were, probably beyond just a simple boolean property in the Players class.
This has not been confirmed or denied by Roblox and considering their track record on these types of updates it is wrong to give them any sort of benefit of the doubt.
People here can read infact, the vocal opposition is by and large to the removal of classic heads and faces from the Marketplace. Dynamic heads being in beta testing for some time does NOT mean that players should have expected this to happen, quite the opposite considering that layered clothing and classic clothing have been able to co-exist in the Marketplace for an extended period of time.
faces on R6 look completely dead inside.
I use this face on my human avatar and it became an essential part and i simply CANNOT use “Face of Disapproval” because of that reason. Also it lowers my shades and make it even weirder.
if roblox the next thing they do is REMOVE classic faces, they force me to hide the rest of the face with a scarf that covers mouth.
Actually, all you have to do is go to Studio settings and enable Deprecated Objects, and then restart Studio:
Group shouts appear under notifications now, I believe. You may also have to enable that. If they don’t, I know that the game update notifier thing (bit too tired to look up what it’s actually called right now) will send a notification to everyone who’s following the game. There’s also some new notification thing that I’ve just now seen called “Notification Strings” and I have no idea what that is as of this moment.
Not quite sure which animation update you’re referring to in this case.
The issue here is more that Roblox is really slow with their updates. I was hoping that their roadmap would be more transparent with all of their activities, especially those that were announced in previous RDCs even from several years ago and have yet to see any announcements on even if they’re still in progress or dropped.
Also not quite sure what you mean here. Keeping what things consistent across what versions of what?
The roadmap and their apology give me some amount of hope at least. Plus, keep in mind that Roblox actually used to be much worse with this sort of thing. People like to praise classic Roblox, but it was really bad when it came to many different things.
As I said in my post, that part isn’t the issue. The issue is that they need to keep certain aspects up-to-date. Whether that be to make sure that all services remain functional or just required by law in some areas. This specific topic can go much further in depth, something I don’t particularly feel like doing right now, but it’s something that is unrealistic in that particular way.
Now I don’t think it’s actually impossible. There are other ways to preserve games, such as opting out of all new updates automatically by default. A lot of deprecated things do still actually work perfectly fine. They’re only deprecated because they’re no longer maintained. That is one of the issues with having something live such as Roblox. Even Windows struggles with this, keeping all sorts of legacy stuff in for various reasons. However, they seem to be throwing that out now with Windows 11 onward. It does require an amount of resources to keep everything working as core framework constantly changes. Definitely not impossible, but you can see that there is a very real cost there. It’s also considered as bloat.
I have personally not seen anything that would actually make me want to move away from Roblox. The services it provides are more valuable than the downsides that Roblox has, in my opinion. As far as this update goes, the boolean is really all there is. If you don’t trust that, you can create a system to replace it with a classic head, which isn’t actually hard to do in this case. I saved the original R6 avatar when R15 was announced just in case, but it seems that wasn’t needed.
Now I don’t think you should have to make your own system, but at least it’s possible if needed. But if you actually look at these updates, so far everything reasonable has had a way to opt out and that has stuck. Don’t get me wrong, I understand your fear. I guess I should also clarify that I’m not really defending Roblox here either. They need to make sure that this always remains the case. But I will say that the services they provide are more than worth it currently for me.
Gee, that would have been really nice to know about. Maybe, oh, I don’t know, some more publicized post elaborating that this setting exists? A contextual tooltip when searching for deprecated classes to inform the user that there is a setting for deprecated classes to remain visible? Am I wrong for expecting better out of a billion dollar company?
(Scroll down, you’ll get it)
Methods to circumvent this update exist, however obscure and never publicized.
You’re free to opine that Roblox still has value, which it may for some, but my point is that there is no guarantee that things will remain the way they are, for better or for worse. Developers will always be in a rat-race to maintain their game, to fix things they never broke to begin with, and personally I’ve had my fill of that.
Yes, deprecated objects are still functional, though entire libraries or facets of the API are not permanent fixtures onto the engine.
That was a hypothetical. If they were to make it toggleable in game options, no harm no foul, but we’ve gotten no concrete word with whether the originals will remain accessible or not.
I think it’s worth mentioning that the people in charge of maintaining the Linux Kernel do no such thing. Isn’t that a novel concept?
Most of my points development-wise are done with direct comparisons to other engines. I understand that Roblox is a unique platform, though developers should honestly get a feel for how things are done elsewhere - it’s much nicer, trust me.
I’m well aware of the things Roblox provides free of charge, but engines such as Godot by the Godot Foundation are free just the same, provide an equal amount of documentation and community support, and doesn’t ask for a single penny from your profits. Again, I understand that Roblox takes a lot of the brunt off of the service-end of things, though it’s still worth pointing out that alternatives exist. Disgruntled developers here shouldn’t be left in the dark for healthy alternatives.
If people are fine developing games on Roblox, then that’s their choice, but I personally wouldn’t want to enable Roblox to continue making decisions like these, potentially forcing developers to revise their work. Am I getting through?
To be fair, only older devs would even know about these objects to begin with, unless they’re following an outdated guide. I think it makes sense from Roblox’s perspective to hide it in a setting. While it could always be shown, as they’re already grayed out, it’s worth noting that your average user might not even question why that is, even if there were some type of tooltip. Perhaps a message box could come up warning them. I don’t really think this is a big issue overall as you could look this up, as any developer should when they have a question. I personally found it because deprecated objects were actually previously shown, so I looked through the settings because I was confident that there would be a setting to enable it again. In this case, I think it’s a bit complicated, but the option is still there regardless.
I’ll just give you this because I’m not really familiar with this particular update and I’m not all that interested in animation related things anyway.
This is true, but I don’t believe this is as bad as you portray it to be. Though I’ll admit that I’m only judging this through my experience over the years, perhaps it’s different in other areas that I’m unfamiliar with.
As I said previous, Roblox updates are actually very slow. They also give you plenty of time to prepare, if you keep up-to-date with announcements. I’ve also never had anything break on me in my own experience. With that said, this is why I continue to suggest that new feature remain opt-out by default to avoid issues like this.
Roblox won’t remove anything unless it absolutely must for whatever reason. If it were an invalid reason, we would protest. We know that works because they have reverted several updates for that very reason, including the material update. Roblox has also actually published old utility modules that can be used as well. Though I have to admit that you’d have to actually look it up in order to know that it exists.
Seeing as this is still the case, I see no reason to to bring this up as an issue until it becomes one.
I think you’re missing my point again on why they can’t in this case, but I’ll leave it there.
I completely agree with this on the basis that competition is very important. Don’t think much more needs to be said on that topic.
Unless Godot provides free servers, data storage, and everything else I’ve mentioned, I’m not sure if that’s really a valid comparison in this case.
I’ll once again completely agree that competition is good.
We, the community (yes I’m assuming a bit here), will always fight against forced changes that will cause real issues. Sure it would be nice to just leave a game as is and have it remain operational, but the maintenance isn’t really all that demanding either. Plus, as I said before, I’ve actually never had an issue with Roblox breaking anything in any of my projects/games. I won’t say that doesn’t happen as I’ve definitely seen much older games run into some issues, but I do think it’s relatively avoidable and easy to maintain otherwise.
I’ll just go and say that there is a cost to develop on Roblox, and you do get things in return for that. It’s totally up to the individual developer on what they value. If you don’t want your game to be live service, perhaps Roblox isn’t for you after all. Or perhaps you want to use p2p or whatever else. I do think it’s important to realize that Roblox stands out in its own way due to what it offers. I agree that Roblox could do better at backwards compatibility, but it’s really not that big of an issue in my opinion. This isn’t really an excuse for Roblox, but by the time a game starts breaking from updates, it’s usually well beyond dead player wise.
I know this really sounds like I’m defending Roblox, and in some aspects I am, but I’m only trying to give the other side. I fully support your core idea of backwards compatibility. I do hope Roblox takes steps to better preserve the games on their platform. Though do understand that Roblox doesn’t purposefully want to break games, and they do already try to update carefully. Roblox can do a lot better, but they are at least trying already.
I’ll also leave a disclaimer that obviously everything about Roblox can change at any point. Even if Roblox is perfect, that can change. Roblox may even shutdown one day, though hopefully not for a long time. That is something any developer will just have to accept about any live service platform. This is just an objective fact that each person will have to judge based on their personal needs. Games/experiences on Roblox are best designed as live service games/experiences, as that’s essentially what they are.
(I really need to stop writing essays without meaning to…)