most efficient utilization of module?

[grave charm]

I made a status effect module/system so scripts don't need repeated logic but the issue is that im not sure how environmental stuff should trigger it.

for example, if I had puddles around the map that inflict soaked on players, I could just put a script under each puddle to handle it but that would lead to too many scripts. another solution is applying attributes to each puddle but that isn't very customizable.

there's other solutions to this like effect levels (like: burning I, burning III, etc) or something but, what should I do?

[obtuse wagon]

collectionservice

[haughty torrent]

Use collectionservice to get all parts tagged ‘EffectPart’ and add that same tag to all parts that needs to apply an effect. Now you can add attributes like the effect name and level and make some modular system to load each effect onto any player touching this part.

[grave charm]

im a bit bad at attributes and tags, but i wonder, why is this better then attributes? is it because looking for attributes is somehow less efficient then looking for tags?

[haughty torrent]

You cannot ‘look for attributes’ without it being really inefficient. Thats where tags and collectionservice come in. You can get all instances with a specific tag with a single line if code easily by using collectionservice.

[grave charm]

thanks, but lastly, how should i be applying tags to the "puddles" and whatnot?

[haughty torrent]

Well its easy, select a puddle, go to properties and scroll all the way down. Clikc + in the tags-section. Name your tag and its applied.