Stash Saboteur quest bugged.

[SWBeta]

The Lv. 22 quest, Stash Saboteur (Auphiliot, Buscarron's Druthers, South Shroud) is bugged. Objective cannot be completed because the interactable objects are not selectable/targetable. The interactables glow greenish-blue, and cannot be targetable (All items are selected to be targetable in filter menu, so that is not the issue).

This occurred during one of the emergency maintenances that were held today. After maintenance, some players could complete, but others are unable to, including myself.

[e90guy]

I have the same problem. I saw the three crates but couldn't target/select them.

[Eowyn]

Getting the same error, can't target the stashes.

[Magnesium02]

Do you have a key item related to the quest? There are a few quests where instead of interacting with the destination and then using an item, you need to click on the item on your quest sidebar which then brings up a targeting icon. You move the target onto the destination and confirm.

[e90guy]

Do you have a key item related to the quest? There are a few quests where instead of interacting with the destination and then using an item, you need to click on the item on your quest sidebar which then brings up a targeting icon. You move the target onto the destination and confirm.

I have the key items and you need to select/target the creates but I couldn't.

[Magnesium02]

Have you played Arcanist or used a limit break? The targeting is similar to moving your pet or placing the limit break. I use a controller and it takes using the left stick to move it. Also the circle must change from purple to orange in order to be used. I'd it is purple the 'terrain' under the circle isn't a suitable location to activate

[Shadowedge]

The targeting is similar to moving your pet or placing the limit break. I use a controller and it takes using the left stick to move it. Also the circle must change from purple to orange in order to be used. I'd it is purple the 'terrain' under the circle isn't a suitable location to activate

Thank you so much for this. I was having the same problem, but didn't realize this is what was happening.