It seems that the consensus is that having a remote for each “action” is better. However, in my case, I eventually plan to have around, say, 100 different skills in my game. Would it be better then to have a single remote and call the skills by their ID? Or would it be better to just have a remote for each skill?
I’m only really concerned with the performance, as I can manage both methods. Currently, I have a single remote that takes a skill ID and then looks up the skill’s function in a table, where the key is the same as the skill ID. It’s early enough that I can change it, but I don’t want to rewrite it later on when I have many skills.
Whenever I do stuff like this I find it better to just do the method you suggested; use one remote for all and just refer to them with an ID, this also cuts the time taken to add new skills in your case.
You could store the skills in a module as a dictionary and have the player pass in the skill they’re attempting to use, then look that skill up in the dictionary and run the function for that specific skill.
I have worked with the “one remote for everything” method and at some point if you have a lot of stuff it becomes really messy and confusing. It might be because I probably didnt organize it properly. But using 1 remote for 1 thing for lets say 100 skills is also really messy.
