EndlesNights
commented
2 years ago -
Wooops my bad, missed called a function.
-
Wooops my bad, missed filtered that.
-
Might have been caused by another bug that I squashed, where tokens with linked actors where causing some strange edges case issues
-
See 3
-
/ 6. I really like these ideas. Would probably take a bit more work. Though it doesn't help that Active Effects have some strange nuances in the core code compared to other imbedded object types that make this a little harder. Might have to keep this on the side for now. I know PF2 has done some of these, but they've built up their own custom systems for apart from the core Foundry Active Effects system (they also have waaay more devs), so their solutions are not at all compatible with what we have here. If you happen to ever find a time machine, you should tell past me to use PF2 as a base foundation instead of 5e. Cause then we would probably have had way cooler stuff way sooner.
Anyway thanks again for all your feedback, and pointing out my goofups! And hope you have fun!
NuptupTDOW
So, After the Active Effects update, I started playing around with it and here's some things I noticed right away.
1: My characters can no longer use the Long Rest button on the character sheet. When they press it, the prompt appears, but when you click to confirm it, there is no resolution and the window stays active and no changes are posted.
2: When setting an effect in the new effects tab to "Affects Self Targets" it is sorted in the "Affects All Targets" group.
3: When setting an effect to apply to "Affects Hit Targets" and applying 4 effects (-2 to all defenses) such as the Astral Seal power, I can't figure out how to apply those effects when the power is a "probable hit" after rolling.
4: When setting an effect to "Affects Self Targets" and setting the effects (Razorclaw Shifting) to give +2 speed, +1 AC/Ref until duration End of Encounter, upon using the power, nothing happens, regardless of whether the "Transfer Effects to Actor" box is applied EXCEPT that it will put a condition on the actor's token but only appear in the "Unavailable Effect" group on that character's sheet. I can toggle the effect to being an Inactive Effect, but I can't ever get the power to turn it into an active effect.
5: Is there a way to make it so that the power output into the text channel can display "The Effect" as a click and draggable "box/handle" that can be pulled over a token, and when released it applies the effect to that token? This would be ideal for powers that have multiple different effects that apply to different actors, such as our Healer's Astral Seal which A: applies target -2 to defenses B: Heals ally who next hits target and C: applies temp HP to one ally in range. Currently we can only have one "Healing" roll associated with the power which we're using for the temp hp, and then applying the healing through a secondary power when it's relevant, but it could be nice to have the healing be in the healing line, and then just have a click and draggable effect that our healer can drag directly onto the ally of their choice to give the THP to. And, in the case someone forgets to target an enemy, it would still output an "Astral Seal" "draggable" that they (or the DM) can drag onto a hit target to apply the -2 to defenses.
6: I truly am excited for a fully automated 4e experience when it comes to effects and conditions, but that sounds like a LOT of work, and I feel like a very good tide-over and also a good redundancy system would be a great idea to add for those occasions when something is missed. Or, for example when a power does "X to all targets hit" but "Y to all allies in burst" (Such as moment of glory), where you wouldn't want to target the allies during the attack portion since they aren't targets. So far I can't think of a way to generate multiple effects that target different creatures in the same power, so the "Draggables" idea would serve a purpose here.
Anyway, I'm sure you'll put out a fancy explanation for how it all works, similar to the "Effects" compendium entry, but in my quick testing, those were the things I found. I'll hold off on doing anymore extensive futzing about until I can get some feedback to see if I'm maybe just completely missing something.