[BUG] Guild permissions, do not work.
Closed this issue · 5 comments
I confirm that:
- I understand that if I do not agree to the following points by marking the checkboxes my issue will be ignored.
- I have searched existing issues to see if the issue has already been opened, and I have checked the commit log to see if the issue has been resolved since my server was last updated.
- I am currently on the latest commit of the branch when reporting this bug
Code branch that is affected by this issue
develop
Bug description
When guild permission is given to a house, land, trunk, etc., guild members do not have access to it.
Steps to reproduce
- Create a guild
- give guild authorization to a house, land, trunk, etc.
- ask another guild member to access it
Expected behavior
Screenshots
Any additional context for this bug
I'm looking into this, and I did find one error related to the house packet data, but it's not related to a fix for this.
What is happening is that the server correctly knows the permissions to use when it's set to guild. But for whatever reason, the house itself is not considered to be part of a Guild by the client, and that is what is causing other guild members not to be able to interact with the normal house doodads.
It's not just the house, the land around it, which is also in the guild, is also in the same situation
I mentioned the house, as the house itself defines what the client will allow when something is placed on it. Permission settings for items that cannot have it's own permission set are irrelevant to the client, and will always default to the parent house's permission regardless of what the server tells it to be.
A farm is independent from the house, right?
When I talk about the land around the house, these are farms that I have placed around it, and which are also not accessible to members of the guild.
That would be the same reason, anyway, I tracked down the issue, and working on a fix.