Mitigate nil addition in EGP.umsg.End

[Denneisk]

Was sitting on this but thought it was just a fluke.
I don't know the cause, EGP's net messages seem to be properly contained as best as I can tell.

[thegrb93]

Shouldn't the net.Broadcast() be with the EGP.IntervalCheck[CurSender].bytes = EGP.IntervalCheck[CurSender].bytes + bytes? Also I don't see the point of changing CurSender to use NULL. Whatever is setting CurSender should do a IsValid check.

[Denneisk]

Shouldn't the net.Broadcast() be with the EGP.IntervalCheck[CurSender].bytes = EGP.IntervalCheck[CurSender].bytes + bytes?

It's needed to close the message if the sender becomes invalid somehow in between. It does nothing if a message isn't started. But I could change it to possibly be a bit less wasteful.

Whatever is setting CurSender should do a IsValid check.

It's to avoid nil checking and instead expect it always as an entity. IsValid is already done on sender before the message gets started.

[thegrb93]

Will the IsValid check cause the EGP to stop working if the owner isn't connected?
Or do things already break if that happens?

[Denneisk]

Will the IsValid check cause the EGP to stop working if the owner isn't connected? Or do things already break if that happens?

Yes, but it already would do that before.