Skip to content
This repository has been archived by the owner on Aug 29, 2024. It is now read-only.

Fix initial player control in a multi-worker (zoned) deployment. #1359

Merged
merged 2 commits into from
Sep 20, 2019

Conversation

yumnuska
Copy link
Contributor

@yumnuska yumnuska commented Sep 19, 2019

Description

When running a deployment with multiple server workers, it's possible for a worker to gain authority over a player controlled pawn, its player state, and its player controller in an arbitrary order. This change adds handling for the case when the worker gains authority over the pawn before receiving the player state.

Release note

Added to changelog

Tests

Found, debugged, and tested in Edmonton project.

Primary reviewers

@m-samiec @cmsmithio

@improbable-prow-robot improbable-prow-robot added jira/no-ticket Indicates a PR has no corresponding JIRA ticket size/S Denotes a PR that changes 15-39 lines, ignoring generated files. labels Sep 19, 2019
Copy link
Collaborator

@m-samiec m-samiec left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice catch!

@cmsmithio cmsmithio merged commit afff0ed into master Sep 20, 2019
@m-samiec m-samiec deleted the bugfix/zoning-movement-at-start branch September 20, 2019 23:32
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
jira/no-ticket Indicates a PR has no corresponding JIRA ticket size/S Denotes a PR that changes 15-39 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants