Summarize what's being changed (include any screenshots, code, or other media if available):
The issue was the fact that entities in view were checked to see if they were updated.Arena has a special case for being added to the view, and that case is before the "is updated?" check. This caused a possible scenario where arena was both created and updated in the same packet
Updates are sent before creations, so this caused an issue. Instead of swapping updates and creation, ended up putting the special case for arena compilation after the "is updated?" check is complete.
Confirm the following:
I have NOT tested these changes (by compiling, running, and playing) and have seen no unintended differences in gameplay
Why:
No issue posted - though it could relate to #96
Summarize what's being changed (include any screenshots, code, or other media if available):
The issue was the fact that entities in view were checked to see if they were updated.Arena has a special case for being added to the view, and that case is before the "is updated?" check. This caused a possible scenario where arena was both created and updated in the same packet
Updates are sent before creations, so this caused an issue. Instead of swapping updates and creation, ended up putting the special case for arena compilation after the "is updated?" check is complete.
Confirm the following:
I have NOT tested these changes (by compiling, running, and playing) and have seen no unintended differences in gameplay