Ticket #1020 (closed bug: fixed)
Only the host sees who quit
| Reported by: | truckspin | Owned by: | |
|---|---|---|---|
| Priority: | blocker | Milestone: | unspecified |
| Component: | Engine: Networking | Version: | 2.2.4 (Unsupported!) |
| Keywords: | quit quitting | Cc: | |
| Blocked By: | Blocking: | ||
| Operating System: | Microsoft Windows |
Description
Since a few versions, maybe since 2.2.2 or 2.2.3, it happens very often that somebody quits (only for certain types of crashes or also for regular quitting?) and only the host gets notified about it. The other players still see that player with ping ??? in the game, and all his units and buildings remain in the game. That is a major annoyance, because even teammates can't take his oil, so the game is over when that happens.
Sometimes this happens, and sometimes they do see who quit. I can't say more about the reproduction than to play a few online games; it happens often.
Attachments
Change History
comment:2 in reply to: ↑ 1 Changed 2 years ago by Buginator
- Status changed from new to pending
Replying to -Kosh-:
There is a icon that appears when it detects someone dropped. The ??? means it can not calculate the ping time most likely.
You should see the icon, as he said. Everyone should...
If this is not the case, then please post back.
comment:3 Changed 2 years ago by truckspin
- Status changed from pending to new
This is not entirely wrong, but not relevant either.
I don't care about icons. I don't care if they "know" who quit; that could be simply worked around by the host telling everyone who quit.
The real problem is:
all his units and buildings remain in the game. That is a major annoyance, because even teammates can't take his oil, so the game is over when that happens.
This has nothing to do with any icons. His teammates just can't take the oil, and the buildings and units remain in the game, even when the user turns off his computer and burns it.
It happened a few releases ago and still is that way.
(And they don't get the icon either in that case, but that's not the problem. Also we all know what a ??? ping means.)
comment:4 Changed 2 years ago by anonymous
Also note that when this happens, the host can get a victory screen while his OWN TEAMMATES don't.
Please don't forget this easily reproducible bug; it is a major annoyance!
comment:5 Changed 2 years ago by Zarel
It's hardly "easily reproducible" - I've never seen it happen, unfortunately.
comment:6 Changed 2 years ago by truckspin
Can't be! It happens for about 50 % of all clients who quit/crash! When it started to happen last year in some 2.2.x I didn't even bother to report it, because it was so obvious that I was sure it would be fixed immediately.
comment:7 Changed 2 years ago by Zarel
Sync bugs are near impossible to fix immediately. Only the host seeing when someone quits is just that - a sync bug.
comment:8 Changed 2 years ago by Zarel
- Priority changed from critical to blocker
I agree with Per. Blocker priority.
comment:9 Changed 2 years ago by Buginator
- Status changed from new to closed
- Resolution set to fixed
(In [9644]) Change / add a few log WARNINGS to INFO instead, to track down why the game thinks that people have left when they haven't, and also fix the bug of not destroying the player who dropped / left feature(s).
fixes ticket:1020
comment:10 Changed 2 years ago by Buginator
"Change / add a few log WARNINGS to INFO instead, to track down why the game thinks that people have left when they haven't, and also fix the bug of not destroying the player who dropped / left feature(s).
fixes ticket:1020"
comment:11 follow-up: ↓ 12 Changed 21 months ago by kai
- Status changed from closed to reopened
- Resolution fixed deleted
It's back :-( ver 2.3.0
This time the host's units CAN get hurt by ghost defences.
comment:12 in reply to: ↑ 11 Changed 21 months ago by Crymson
Replying to kai:
It's back :-( ver 2.3.0
This time the host's units CAN get hurt by ghost defences.
What does that mean? The player never drops?
I haven't run into this issue with 2.3.0
comment:13 Changed 21 months ago by kai
Right, even after more than an hour, the clients still see the frozen client, and the host doesn't see it but still gets hurt by defences when he comes close.
comment:14 Changed 19 months ago by hao
I've seen this several times too, in 2.3.1 also. I usually see ping 1000 instead of ??? in that case. I still see the defenses and units of the player who has left, and it can hurt me, and even if the host comes near these units, his units can die because my computer reports them dead.
comment:15 Changed 19 months ago by Zarel
comment:16 Changed 19 months ago by Buginator
- Status changed from reopened to closed
- Resolution set to fixed
(In [11109]) When player disconnects / drops, handle the message, instead of the clients ignoring it.
Fixes ticket:1020
comment:17 Changed 19 months ago by Buginator
When player disconnects / drops, handle the message, instead of the clients ignoring it.
Fixes ticket:1020
comment:20 Changed 19 months ago by Git SVN Gateway <gateway@…>
(In [8e02c3d3eacc5437fb1218d4741e4ca258833da7]) When player disconnects / drops, handle the message, instead of the clients ignoring it.
Fixes ticket:1020
git-svn-id: https://warzone2100.svn.sourceforge.net/svnroot/warzone2100/trunk@11109 4a71c877-e1ca-e34f-864e-861f7616d084
comment:18 Changed 19 months ago by Buginator
When player disconnects / drops, handle the message, instead of the clients ignoring it.
Fixes ticket:1020
There is a icon that appears when it detects someone dropped. The ??? means it can not calculate the ping time most likely.