Optimizing major places for improvement

[aed3]

This is to keep track of changes I want to make to address speed bottlenecks found in #46. In order of importance:

• Replacing SelectForView method of selecting entities #49
• Creating current action entities at battle creation and reusing them throughout the turn #51
• Tracking how many Pokemon are still available instead of calculating it every time

[aed3]

I'm not sure if this will lead to a speed up, but I'll also try moving move slots from entities to just one struct containing the name, PP, and max PP. Those three pieces of data are the same size as one entity, so there might be no added benefit to keeping the separate.

[aed3]

I'm not sure if this will lead to a speed up, but I'll also try moving move slots from entities to just one struct containing the name, PP, and max PP. Those three pieces of data are the same size as one entity, so there might be no added benefit to keeping the separate.

Never mind, I'm almost certain this will be an important change. For a 6v6 battle where each Pokemon has 4 moves (aka the most common situation), moves take up 48 entities per battle. There are only 15 other entities each battle uses, so if the number of entities active makes a difference in how fast EnTT can run (it does), then removing move entities is very important.