#SWIM support
1 messages · Page 1 of 1 (latest)
Creating a thread because I won't be able to keep up with this channel otherwise.
@limpid yoke
No changes lately, I currently have too much other stuff to do so I can't really work on any of my RPG projects. I even had to cancel sessions. :-S
It is entirely possible that there is something in warpgate that causes this behaviour, I know warpgate was updated recently but I haven't had the time to check that out either.
If that is the case, it'll be an easy fix though. Currently the function relies on warpgate flags to identify summoned creatures while the Active Effect unsummon solely relies on SWIM flags. So it seems reasonable that warpgate changed something here. I wanted to change the flag condition for the dialogue anyway so...
But please check the console (F12) for errors that mention swim or mighty-summoner.js anyway, just to see if there are any. if so please send me a screenshot here.
If there is nothing please make a bug report on the swim repo and mention that I speculated about warpgate flags as the cause. I'll remember then and try to fix it. Unfortunately I can't promise that it'll be done soon though, sorry. :-S
@strange bear Thanks for the response! It’s definitely not critical! Like I said, si missing the Active Effect for the summons still does the proper dismissal. I’ll post a bug today…I always like to check just to make sure it’s not some boneheaded mistake on my part. SWADE did get an update yesterday as well, it no clue if that has anything to do with it. From my layman’s seat, it looks like the macro can’t tell the token is a summons anymore.