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
For Pharos Sirius (Hard) unsynced, AutoDuty doesn't attempt to interact with the mob-dropped Candlekeep Key, or the Locked Door which the key unlocks. It kills the monsters but does not attempt to pick up the key, and does not automatically interact with the locked door. When allowed to continue, it auto-runs the character against the locked door in an attempt to reach the boss inside.
I noticed that both of these interactables don't have coordinates assigned, perhaps that's the problem?
Version Number
0.0.0.181
Steps to reproduce the error
Load up AutoDuty to run Pharaos Sirius (Hard) unsynced. Let AutoDuty run through its pathing until it reaches the point where it needs to interact with the Candlekeep Key and the Locked Door.
Relevant log output
No response
Other relevant plugins installed
No response
Plugin config file
No response
The text was updated successfully, but these errors were encountered:
What happened?
For Pharos Sirius (Hard) unsynced, AutoDuty doesn't attempt to interact with the mob-dropped Candlekeep Key, or the Locked Door which the key unlocks. It kills the monsters but does not attempt to pick up the key, and does not automatically interact with the locked door. When allowed to continue, it auto-runs the character against the locked door in an attempt to reach the boss inside.
I noticed that both of these interactables don't have coordinates assigned, perhaps that's the problem?
Version Number
0.0.0.181
Steps to reproduce the error
Load up AutoDuty to run Pharaos Sirius (Hard) unsynced. Let AutoDuty run through its pathing until it reaches the point where it needs to interact with the Candlekeep Key and the Locked Door.
Relevant log output
No response
Other relevant plugins installed
No response
Plugin config file
No response
The text was updated successfully, but these errors were encountered: