I am pretty confident this was fixed by https://git.eq2emu.com/devn00b/EQ2EMu/commit/77616c791e1bb35be89452109df52afc963e8290
"- Zoning spruced up, we track incoming clients to a zone and also can emergency bootup a zone should it not be ready for incoming clients."
09:13:49 I Zone : Completed zone shutdown of 'QeynosHarbor'
Read packet: opcode 7 newlength 40, newbuffer2len: 237, newbuffer3len: 105
Read packet: opcode 21 newlength 4, newbuffer2len: 0, newbuffer3len: 0
we can see qeynos harbor shutting down before the client gets past the initial EQStream stage and gets stuck.
we now expect this message instead
```
+ LogWrite(ZONE__INFO, 0, "Zone", "Incoming clients (%u) expected for %s, delaying shutdown timer...", incoming_clients, GetZoneName());
```
this happened during an actual active stream and I had the client zoning
caused the client to crash with a last packet error
I am pretty confident this was fixed by
77616c791e
"- Zoning spruced up, we track incoming clients to a zone and also can emergency bootup a zone should it not be ready for incoming clients."
09:13:49 I Zone : Completed zone shutdown of 'QeynosHarbor' Read packet: opcode 7 newlength 40, newbuffer2len: 237, newbuffer3len: 105 Read packet: opcode 21 newlength 4, newbuffer2len: 0, newbuffer3len: 0
we can see qeynos harbor shutting down before the client gets past the initial EQStream stage and gets stuck.
we now expect this message instead