Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Guilds/Communities] Handle Residence(s) on Disband or Leave #391

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

kirmmin
Copy link
Member

@kirmmin kirmmin commented Dec 2, 2021

Updates the Community Visit list appropriately on Disband
Fix Players not having a Residence assigned to ResidenceManager when Residence is created
Update Communitiy Visit List on Map Enter in case Community was just disbanded

Updates the Community Visit list appropriately on Disband
Fix Players not having a Residence assigned to ResidenceManager when Residence is created
Update Communitiy Visit List on Map Enter in case Community was just disbanded
@@ -89,6 +89,7 @@ protected override void AddEntity(GridEntity entity, Vector3 vector)
if (entity is not Player player)
return;

GlobalResidenceManager.Instance.SendRandomVisitableCommunities(player.Session);
Copy link
Member

Choose a reason for hiding this comment

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

Any reason this is being sent here?
The client has a packet it sends to request this when the random property window is open.

Copy link
Member Author

Choose a reason for hiding this comment

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

Sorry, I hadn't seen this comment.

I wrote this in here because if a Community is Disbanded, anybody in the current Community Map is removed and then sent to their own plot. When they reload, if they click on the "View Visitable Communities" thing, the old Community shows up because it's using the values from the first time the window was loaded. I discovered that re-sending the visitable communities was all that was needed to remove the, now disbanded, community.

@Rawaho Rawaho added this to the Pull Request Cleanup milestone Jan 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants