Skip to content

Go back to calling MapTool.setCampaign() - #4774

Merged
cwisniew merged 1 commit into
RPTools:developfrom
kwvanderlinde:fixup/pr-4771-bad-state-when-connected-now-for-some-reason
May 8, 2024
Merged

Go back to calling MapTool.setCampaign()#4774
cwisniew merged 1 commit into
RPTools:developfrom
kwvanderlinde:fixup/pr-4771-bad-state-when-connected-now-for-some-reason

Conversation

@kwvanderlinde

@kwvanderlinde kwvanderlinde commented May 7, 2024

Copy link
Copy Markdown
Collaborator

Identify the Bug or Feature request

Fixes PR #4771

Description of the Change

As part of my cleanup in the previous PR, I switched ClientMessageHandler from calling MapTool.setCampaign() to directly calling MapToolClient.setCampaign(). This is a mistake since - for now anyways - MapTool.setCampaign() still does a few important things that are separate from MapToolClient. This new PR addresses that.

Possible Drawbacks

Only upsides 🙂

Documentation Notes

N/A

Release Notes

N/A


This change is Reviewable

For now, the global `MapTool.setCampaign()` still does a fair bit of work outside of `MapToolClient`, so it was not
correct to have removed it the call to it in `ClientMessaageHandlder`. On the other hand, the call to
`MapTool.getPlayerList()` is not necessary.
@kwvanderlinde kwvanderlinde self-assigned this May 7, 2024
@cwisniew
cwisniew added this pull request to the merge queue May 8, 2024
Merged via the queue into RPTools:develop with commit cb46722 May 8, 2024
@kwvanderlinde
kwvanderlinde deleted the fixup/pr-4771-bad-state-when-connected-now-for-some-reason branch May 13, 2024 23:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

No open projects
Status: Merged

Development

Successfully merging this pull request may close these issues.

2 participants