You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
marvin9257
added a commit
to marvin9257/twodsix-foundryvtt
that referenced
this issue
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.
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
The text was updated successfully, but these errors were encountered: