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

'User lacks permission to update ChatMessage' error message #1514

Open
cornyB23 opened this issue Mar 16, 2024 · 3 comments
Open

'User lacks permission to update ChatMessage' error message #1514

cornyB23 opened this issue Mar 16, 2024 · 3 comments
Labels
bug Something isn't working combat Related to a future combat refactor

Comments

@cornyB23
Copy link

Prerequisites.

Description.

GM targets a player token then clicks the Sanity loss button on a creature/monster character sheet. This opens a chat message for the targeted player with a button to make a Sanity check roll.

Expected Behavior.

The player clicks the Sanity Check button, the roll is made and subseuent adjustments (sanity loss, bouts of madness, etc. ) arte made.

Actual Behavior.

The player gets a '"User [player name] lacks permission to updaye ChatMessage (message-id]" error and no roll is made. This happens when player is promoted to Trusted Player, but is solved by promoting player to GM Assistant or higher.
Tested in Firefox and Chrome, and with no modules running.

@cornyB23 cornyB23 added the bug Something isn't working label Mar 16, 2024
@snap01 snap01 added the combat Related to a future combat refactor label Mar 24, 2024
@snap01
Copy link
Collaborator

snap01 commented Mar 24, 2024

The Actor the token is related to needs to both be set to Owner for the User and the Users default character.
This can be set in player list, right click the users name, select User Configuration, make sure the correct actor is selected.

@snap01 snap01 changed the title GM instigated SAN roll triggers 'User lacks permission to update ChatMessage' error 'User lacks permission to update ChatMessage' error message Mar 24, 2024
@snap01
Copy link
Collaborator

snap01 commented Mar 24, 2024

Leaving this issue open as a future refactor of the code will prevent this issue

@cornyB23
Copy link
Author

You star. Many thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working combat Related to a future combat refactor
Projects
None yet
Development

No branches or pull requests

2 participants