"ALWAYS create local variables = parameters of the same name, do not use parameters in coding. Why? So you can copy and paste code obviously." and then "Copying and pasting code is bad."
Consistency is also good practice for any coder...
Besides, I've always thought that copy/pasting code from other places and modifying it is a good way to learn. Sure it won't be optimal, but if it's a matter of doing something poorly or not doing it at all, I know what I'd choose. And once you've learnt enough you can edit the bad code. Opening the campaign maps can be a good idea when you want to do "that thing in that mission". It was very helpful for me to figure out how to make abilities with charges and pickups.
As for Records, I don't find them worth the effort. Player[15].deaths instead of player_deaths[15]? Big deal. Sort your variables into folders if you have a lot of them and use a naming scheme and allows you to skip to a certain letter to find your variables.
0.952660550458716
"ALWAYS create local variables = parameters of the same name, do not use parameters in coding. Why? So you can copy and paste code obviously." and then "Copying and pasting code is bad."
Consistency is also good practice for any coder...
Besides, I've always thought that copy/pasting code from other places and modifying it is a good way to learn. Sure it won't be optimal, but if it's a matter of doing something poorly or not doing it at all, I know what I'd choose. And once you've learnt enough you can edit the bad code. Opening the campaign maps can be a good idea when you want to do "that thing in that mission". It was very helpful for me to figure out how to make abilities with charges and pickups.
As for Records, I don't find them worth the effort. Player[15].deaths instead of player_deaths[15]? Big deal. Sort your variables into folders if you have a lot of them and use a naming scheme and allows you to skip to a certain letter to find your variables.