Automatically set journal entries permissions based on the permissions of the kanka entity #49
Labels
Milestone
Comments
|
I'll have to look into this, I like the idea, though I'd probably hide the feature behind an optional setting (as I'd rather err on the side that hides info from a player than show them anything they shouldn't see by accident). |
eXaminator
added a commit
that referenced
this issue
Jun 14, 2021
…ayers on public entities Fixes #49
github-actions bot
pushed a commit
that referenced
this issue
Jun 15, 2021
# [2.1.0](2.0.1...2.1.0) (2021-06-15) ### Bug Fixes * improve rendering in readonly context ([43d2496](43d2496)) ### Features * add button to link all entities at once ([491827f](491827f)), closes [#46](#46) * add option to automatically set observer permissions for all players on public entities ([4d725f4](4d725f4)), closes [#49](#49) * add progress bar for bulk operations ([505a3da](505a3da)) * add support for Foundry 0.8.7 ([b733d3c](b733d3c)) * add tab that displays all files of an entity ([8cdde61](8cdde61)), closes [#2](#2) * remove Foundry 0.7.x support ([d2c2879](d2c2879)) * show specific list of journal entries and folders that will be migrated on module update ([2b4700e](2b4700e)) * switch to image mode when clicking the image in the entry ([e5ab565](e5ab565))
|
🎉 This issue has been resolved in version 2.1.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If the kanka entity is set to public or player read, then set the permission of the journal entries to "observer" for all players.
The text was updated successfully, but these errors were encountered: