In a given instance, if a player disconnects and reconnects, the PartyChanged event either doesn't fire or doesn't have the reconnected player's details, causing raidboss trigger data.party.details object no longer knows about them.
Additional information
I use the following helper function for custom triggers:
This results in the following error stack when that trigger fires for the given player after they've disconnected and reconnected (trimmed irrelevant lines):
Description
In a given instance, if a player disconnects and reconnects, the PartyChanged event either doesn't fire or doesn't have the reconnected player's details, causing raidboss trigger
data.party.details
object no longer knows about them.Additional information
I use the following helper function for custom triggers:
This is being used in the following trigger:
This results in the following error stack when that trigger fires for the given player after they've disconnected and reconnected (trimmed irrelevant lines):
Possibly related to #151.
Relevant Cactbot code segments:
https://github.com/quisquous/cactbot/blob/ed9b3b912a3107f3481cc5d92fa9b81349c68f5a/ui/raidboss/popup-text.ts#L519-L521
https://github.com/quisquous/cactbot/blob/ed9b3b912a3107f3481cc5d92fa9b81349c68f5a/resources/party.ts#L28-L48