I just have a quick question. Why do we put things other than skies, atmospheres and blurs into Lighting? Like scripts. I am not good at scripting at all and would like to know the reasoning behind that. Some free models that I mess around with (like ones that have instructions) say to put like a script for example into lighting, but I wasn’t sure why. Any explanation is appreciated 
It is bad practice to put non-effect like objects like scripts or parts in lighting. Parenting something in lighting will have no different effect than parenting in a different service that the client can get to such as workspace or replicated storage though.
1 Like
you put your scripts wherever u want to keep them neat or wherever they are relevant to (as long as they still fire), if you have a script that changes something in the lightening and u dont know where to find it, look in lighting if u store it with that kind of logic.
1 Like
That’s not entirely true, as if this were the case we wouldn’t have all 3 types of storage and it wouldn’t be a bad practice if both were the same…
In reality, most scripts that use lighting for storage will probably be pretty old, or at least use old/ dated practices. ReplicatedStorage was made as a replacement for lighting and ReplicatedFirst is used I believe mainly for holding UI.
1 Like