-
Notifications
You must be signed in to change notification settings - Fork 49
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
A random bug about ${_ffxivparty} #71
Comments
To back this up It isn't just role related. ${_ffxivparty[1].name} will sometimes return null. I have gotten a lot of people asking for help on why my triggers works for 7 of the party members but the 8th will randomly break. They report it was working a previous day and not the next. The solution I have to give them is to hardcode the names. Issue has been reported to me by people using both XIV Quick Launcher as well as vanilla game. |
Me too, I also found it later. Now I have to save a list of player names and jobs before the battle to make sure the triggers work properly. Edit: It seems that _ffxiventity does not have this bug. I am using _ffxiventity instead of _ffxivparty in most cases now. (except for those related with party order) |
I met this issue as well. (Plugin Version: 1.1.6.0) |
Hi,
I found my triggers sometimes do not work properly. After debugging, it showed that ${_ffxivparty[a party member's name].role} randomly returns empty value, instead of "DPS", "Tank" or "Healer".
This trigger is expected to be executed in P2 Sanctity (Dragonsong) to identify the two meteor players, and I am sure that other parts were not written wrong.
Thanks.
The text was updated successfully, but these errors were encountered: