[BDS-4899] Console Logs Disconnection Message Too Many Times for a Player on the Same Device with Server Created: 01/May/20 Updated: 29/Jan/21 Resolved: 29/Jan/21 |
|
| Status: | Resolved |
| Project: | Bedrock Dedicated Server |
| Affects Version/s: | 1.14.60 |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Mike Evet | Assignee: | Unassigned |
| Resolution: | Incomplete | Votes: | 1 |
| Labels: | None | ||
| Environment: |
Operating System: Windows 10 Pro 2004 (Insiders Build) |
||
| Attachments: |
|
| Confirmation Status: | Unconfirmed |
| Description |
|
When a player from the same device where the server is hosted disconnects, the console spews the disconnection message far too many times. |
| Comments |
| Comment by [Mojang] Mega_Spud (Jay Wells) [ 29/Jan/21 ] |
|
Cleaning up old tickets: This ticket had been set to 'Awaiting Response', but has not received a response from the reporter (~3 months+) so is being closed as Incomplete. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines which includes steps to reproduce the problem. Quick Links: |
| Comment by IonicEcko [ 22/Jul/20 ] |
|
Are you still able to reproduce this issue in the latest BDS release? Much like Ben I've been unable to reproduce this issue, for us to confirm it and pass it on to the developers we need to work out how to trigger the problem. As Ben mentioned, a copy of your server.properties file could help. Other information like any changes you make from a completely vanilla copy of the BDS files would assist. An example would be if you turn off online mode and connect using a client not connected to Xbox Live. The report will be temporarily closed as Awaiting Response. It will re-open automagically as soon as you comment back. |
| Comment by Toba da'Great [ 15/May/20 ] |
|
I wonder if this is related to symptoms you see with other bug: Would you mind sharing your server.properties file. Have you run the checkisolation fix provided in the bedrock_server_how_to.html |
| Comment by Mike Evet [ 14/May/20 ] |
|
"As a bug tracker this site doesn't work in the same way a support site would. Once a bug is logged you don't receive feedback on that report through to a resolution." My appologies, I come from an area of experience using Discourse, so I'm still getting used to Jira as a place to report bugs. As for the main concern, I'm not sure what other details I need to provide in order to identify the underlying issue. |
| Comment by IonicEcko [ 06/May/20 ] |
|
I've just tried to reproduce this myself and have been unable. We'll need to narrow down how to reproduce the problem as it doesn't appear to be present by just starting a server on the local PC and connecting to it. |
| Comment by IonicEcko [ 06/May/20 ] |
|
Hi Mike, As a bug tracker this site doesn't work in the same way a support site would. Once a bug is logged you don't receive feedback on that report through to a resolution. You will be notified by email of any changes to the report when they happen if you've chosen to "watch" the report (top right corner). Ionic |
| Comment by Mike Evet [ 03/May/20 ] |
|
It's been about 3 days with no response or update. I'd like a follow up. |