NetworkedAnimator may cause excessive allocations

[angusmf]

Apologies for pointing this out before I've tested it, but noticed that, just like in the vanilla HLAPI, the for loops when reading and writing parameters repeatedly call the m_Animator.parameters property. This causes huge allocation spikes there. I created PR 12 for this. https://github.com/TwoTenPvP/MLAPI/pull/12

[TwoTenPvP]

Haven't tested either. But this should be right. However, no need to allocate a new array each time we can WriteParameters or ReadParameters. The parameters are not changed during runtime (AFAIK) and thus we can keep the array. Fix this and I'll merge.

[angusmf]

Agreed. I felt this was less than optimal in the original PR also.

[angusmf]

Have update PR with this.

BTW, the original patch works in HLAPI, which I've verified through testing, so expecting this to work as well.

[TwoTenPvP]

It doesn't. See comments on PR.

[angusmf]

Ok. I'll make the equivalent change in HLAPI and test before updating again.