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

Journal Enhancement for Active Effects #1707

Open
Vespilo opened this issue Dec 6, 2024 · 1 comment · May be fixed by #1667
Open

Journal Enhancement for Active Effects #1707

Vespilo opened this issue Dec 6, 2024 · 1 comment · May be fixed by #1667

Comments

@Vespilo
Copy link

Vespilo commented Dec 6, 2024

Is your feature request related to a problem? Please describe.
Active Effects currently need to be either created directly on an actor or item, there is no way of easily assigning non-permanent effects outside of dedicated macros.

Describe the solution you'd like
A journal enhancement similar to how skillchecks or tables are embedded to simply drag & drop an effect on an actor, saving it in a format such as @twodsix.effect[]

Describe alternatives you've considered
Using macros until now has been working, but a new way of storing effects as strings within journals or tables would reduce the amount of clutter in the macro collections.

Additional context
The Call of Cthulhu 7th edition is currently using an implementation, which was the inspiration for this request

marvin9257 added a commit to marvin9257/twodsix-foundryvtt that referenced this issue Jan 20, 2025
Addresses xdy#1707  - The original AE must still exist or the link is broken.
@marvin9257
Copy link
Collaborator

marvin9257 commented Jan 20, 2025

In the V13 release, I've added some preliminary support for drag-dropping an AE. You can copy by drag dropping between traveller sheets. Also, you can drag-drop to a Journal Entry. It stores the UUID and not an arbitrary formula. So the original AE must still exist to drag from Journal Entry to Traveller.

@marvin9257 marvin9257 linked a pull request Jan 20, 2025 that will close this issue
2 tasks
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 a pull request may close this issue.

2 participants