Networked zay-es optimization

Thanks for the thorough response. Yes, I’ve noticed previously that using getComponent on the client, in realtime, really slows things down. It was indeed that again that caused the spiraling memory usage on the server. It took quite a bit of debugging, but now the server seems rock solid. No creeping at all. I replaced almost all getComponent with separate EntitySets, which had the positive side-effect of making it possible to break out some logic from the ‘main’ update loop. There are still a few getComponent that are not in the main branch, and thus called sparingly.