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

Feature Request: option to disable the damage/healing notifications in main chatlog entirely #2196

Closed
cswendrowski opened this issue Apr 3, 2022 · 8 comments
Labels
feature request wontfix This will not be worked on

Comments

@cswendrowski
Copy link

In GitLab by @esheyw on Apr 3, 2022, 14:34

https://i.imgur.com/LEe0Suq.png these guys. I see them as just clutter, especially with the use of a module like Damage Log which puts equivalent information on a separate tab.

@cswendrowski
Copy link
Author

In GitLab by @lostsanityreturned on Apr 3, 2022, 14:41

Seconded for exactly the same reason.
The undo button from damagelog is too good not to have.

@esheyw
Copy link
Contributor

esheyw commented Jul 16, 2022

re: cs96and/FoundryVTT-damage-log#19, if we can't get an option to toggle, could we at least get the messages tagged in such a way that modules could mute them?

@MorfeuRS
Copy link

I would like to endorse this request.

@DariusWolfe
Copy link

Count me in for the suppress damage messages support crew.

@apoapostolov
Copy link

My groups would definitely benefit from less bloat. The only case where the post is useful, however, is when there's a shield applied and the string will properly inform the players that their shield is now broken or destroyed.

@roguedevjake
Copy link

roguedevjake commented Oct 29, 2022

Putting my vote behind this as well. A pretty big pain and the chat log is cluttered enough as is.

Even giving it a unique CSS class so group ID so a module could just hide them would be nice.

@roguedevjake
Copy link

roguedevjake commented Oct 29, 2022

For anyone interested, if you do a simple search and replace for the following in main bundle.js it will remove the messages

You would need to do it when there are updates... But... it is an option and works for now

await chat_message_1.ChatMessagePF2e.create({speaker:{alias:token.name,token:null!==(_e=token.id)&&void 0!==_e?_e:null},content:`<p>${statements}</p>`,type:CONST.CHAT_MESSAGE_TYPES.EMOTE,whisper:game.settings.get("pf2e","metagame.secretDamage")&&!(null===(_f=token.actor)||void 0===_f?void 0:_f.hasPlayerOwner)?chat_message_1.ChatMessagePF2e.getWhisperRecipients("GM").map((u=>u.id)):[]}),

@esheyw
Copy link
Contributor

esheyw commented Jun 2, 2023

Well, these are useful twice over now (record of IWR, and the undo button) so I'd close this issue if I was still owner of it. Damage log is mostly redudant for me now.

@stwlam stwlam added wontfix This will not be worked on feature request labels Jun 2, 2023
@stwlam stwlam closed this as not planned Won't fix, can't repro, duplicate, stale Jun 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

7 participants