This is seriously getting out of hand - the amount of lag incurred from dropped hats is insane. I know that it’s easy to write a script to remove the dropped hats after x seconds if they don’t get picked up (Adding it to the place when ChadTheCreator wakes up), but I would really prefer if it were a default behavior that was built into the engine, and could be toggled if needed. Some game developers don’t know how to implement this, and have to incur the performance penalty from idiotic users dropping hats like this.
It’s quit easy just to search up “hat remover” on models though but it would be a good option.
Why are hats even dropable? Allowing users to drop their hats doesn’t seem to make much sense, their hats are part of their outfit, if the game doesn’t look good with hats on it’s the creator’s fault, and they should have a script to remove hats. If players have a real issue with having hats on in game, we have an outfit system, change outfits when you’re playing games if it’s really an issue for you.
I assume it’s to allow users to try on other peoples hats, with friends for example.
I assume it’s to allow users to try on other peoples hats, with friends for example.[/quote]
If that is the case, the users should be able to pick up three hats.
Well, I also think that should be the case but I’m guessing users can still only pick up one as they did not compensate for this since the update to allow users to wear three hats compared to the original one back before 2009.
I disagree.
This is just one more restriction on what’s possible to do with roblox, in my opinion. What if I need to have a hat that doesn’t remove? It will literally be impossible.
Dropped hats should be removed after X number of seconds of not being worn.
Why not create a read/write boolean property in Players service or Player object that indicates whether the user(s) can drop their hats?
I agree this is a feature we should keep, but we should have some control over it.
[quote] Why not create a read/write boolean property in Players service or Player object that indicates whether the user(s) can drop their hats?
I agree this is a feature we should keep, but we should have some control over it. [/quote]
We have control over it.
The problem here is that OP thinks writing our own code for it is a burden. I say it’s a liberty and it shouldn’t be removed just to save a couple people a couple minutes…
[quote] Why not create a read/write boolean property in Players service or Player object that indicates whether the user(s) can drop their hats?
I agree this is a feature we should keep, but we should have some control over it. [/quote]
We have control over it.
The problem here is that OP thinks writing our own code for it is a burden. I say it’s a liberty and it shouldn’t be removed just to save a couple people a couple minutes…[/quote]
I mean control over whether or not pressing the “=” button drops hats or not. I’d like an option to make it so when I press “=”, no hats drop at all, versus when I do: they get destroyed instantly.
That’s not what he’s saying at all. Dropped hats are a problem in every single game, so he’s suggesting that some sort of hat cleanup should be built into the engine by default.
That’s not what he’s saying at all. Dropped hats are a problem in every single game, so he’s suggesting that some sort of hat cleanup should be built into the engine by default.[/quote]
That really wouldn’t be appropriate though, when we can just stick the hats to the player and not allow them to drop their hats at all.
An optional property would be nice for devs, but it wouldn’t solve the hundreds of thousands of existing places that aren’t going to turn on that property.
An optional property would be nice for devs, but it wouldn’t solve the hundreds of thousands of existing places that aren’t going to turn on that property.[/quote]
But the only places we should be worrying about this happening are the places created by users who are more than able to control those situations, aka active users with popular games with at least some knowledge of coding?
Right? I don’t see many games that get flooded with players who haven’t had the game creator log on for more than a few weeks or so anyways, much less see users drop mass amounts of hats in them.
In 3 of my games, I made a script where dropped hats slowly go more invisible, then disappear for good after 20 seconds if nobody picks them up.
It also allows characters to pick up 5 hats max.
I haven’t seen any other game in the history of roblox do that, lol. I like the idea of creative control over what happens with hats though. But yeah… peeps should just go to free models to fix this (hilarious but fps-dropping) hat spam. And I probably released my simple code somewhere too.
An optional property would be nice for devs, but it wouldn’t solve the hundreds of thousands of existing places that aren’t going to turn on that property.[/quote]
Turn it on by default?
[quote] Why not create a read/write boolean property in Players service or Player object that indicates whether the user(s) can drop their hats?
I agree this is a feature we should keep, but we should have some control over it. [/quote]
We have control over it.
The problem here is that OP thinks writing our own code for it is a burden. I say it’s a liberty and it shouldn’t be removed just to save a couple people a couple minutes…[/quote]
I didn’t say it was a burden - I’m saying that I forget to put the code in a lot of places, and stuff like this happens.
Dropped hats being removed should be a default, and should also be a setting. This solves the problem in all games, and it can be explicitly disabled when it disrupts a user’s scripts or poses a gameplay issue. What’s not to like?
Made a simple module for removing hats - just run it in any script once, and it’ll remove them.
require(176226550)(t)
t is the delay before checking to see if the hat was parented to a character again before destroying it - it’s a float.