Is storing connections in a table bad?

I want to create a health pickup system that is able to be used on multiple different maps, right now i’m thinking about connecting all of the parts to a touched event and then storing the connections in a table and disconnecting them when the map changes, will this affect memory in a bad way or is there a better way of doing this?

1 Like

Are these parts inside of the map model as well? Or are they separate? To answer your initial question though. No, storing connections in a table is not bad. It’s actually a very efficient way to disconnect connections all at once.

2 Likes

What you’re describing is basically what very popular libraries like Maid, Janitor or Trove do, I recommend looking into them.

3 Likes

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