Is it any good idea to put 600+ "if branches" (no casting just for some simple variables) on 1 custom event ?

Is this the enumerator method from above ? Sounds really good if it works like this. I’m pretty sure i can make it otherwise with a whole bunch of branches maybe even put all the connection pipes in a struct and give them an integer value pipe 1 value 1 and so and then compare the branches if skill2 is active but not 3 then light up 1 to 2 and so on. But this will be for sure not only a lot of work but very inefficient way to do it i guess performance wise. I intendet to put all this branches on the skill button so every time i purchase a skill it will cycle over 600+ branches… I guess this is bad idea on my side and if i understand this correct the enumarator one sounds way better.