Model.Permanent desperately needed!

Feature Requests Engine Features
#1

I got a folder in workspace that I call NoRay.
It’s there for all the items that should not be collided with a ray of any sort. Wether it be a bullet or camera calculation, it always ignore the folder workspace.NoRay

Issue is this:
If I put a part inside the NoRay model and let that part fall all the way down to the FallenPartDestroyHeight then it will delete the folder. This is incredibly frustrating and I can’t go around it. The microsecond the model is deleted 10923092 camera scripts and bullets all stop working. Having a single model used for basic ignore ray list is incredibly useful and saves ALOT of CPU but this constant removal of models is causing my game to break.

Please add a boolean value called Permanent to models so it can’t be deleted by fallpartdestroyheight or any other function (debris, remove, destroy etc).

1 Like
#2

My only suggestion to you is to add a BoolValue named Permanent within the model. If it helps, you can check the value to true.

#3

It doesn’t help at all. Everything inside the model is deleted once the last part reaches FallPartDestroyHeight.

#4

Yeah, Im running into that too. I think what I used to do was anchor a tiny part at the origin

#5

What I do is out one anchored part in the model.

#6

Hmm true, but it’s still a workaround. And a simple malfunction of a script that deletes the wrong model would still delete the folder causing the game to break and the developer to loose days of debugging to findout who caused it.

#7

Not sure if adding another property to a model will pass the cost-benefit analysis test.

#8

It’s a simple boolean value that would be incredibly powerful to developers.
I think this addition is already overdue.

#9

Its another property to replicate. Sure models may not be as popular as Parts, but that could be a lot of extra data overhead we may not need.

However I am not a Roblox Developer. Who knows what footprint this really would have.

#10

I think that not deleting the parent would be a better solution. A folder shouldn’t act like a model object in that regard… It’s a completely different object. There’s no need for another property that we all need to learn about.

#11

My folly, I wrote folder but I meant model.

#12

Ah, okay. Do folders behave in the same way? If not, then that’s good and you should probably use folders instead of models for that exact purpose.

#13

They do behave same way :confused:

#14

Could you not put a model inside of a model? Ignore the parent model and if the child model is deleted just recreate it.

#15

No they do not. When the last item in a folder is removed by the cutoff of the world, the folder is not destroyed. You should use a folder for NoRay.

5 Likes
#16

That is incredibly weird. I switched to folder for a while but still had this issue…
I’ll look into it, thanks for the gif!

#18

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.