JavaScript is required to use Bungie.net

Help

Help us help you.
Edited by Lord Magris: 6/6/2024 7:02:55 PM
0

Recently Added Effect to Weaver's Call Has Function Issues on Prismatic (EDITED)

"Targets defeated by Strand damage have a chance to generate a perched Threadling". (Old post info): This just doesn't do anything. I ran through a whole mission with a Rufus's Fury (Adept) getting kills with it and not a single extra Threadling spawned. None from the enemy bodies, none perched around my Warlock immediately, nothing. It's like pre-buff Weaver's Call still. EDIT: Suddenly it's working out of nowhere. I'm not sure what changed. It might be an inconsistent bug. I was on Prismatic and switched to Solar, so maybe switching the subclasses around while it was equipped to Prismatic fixed it. EDIT 2: It also randomly stops working. Doing as mentioned above does indeed fix the issue. EDIT 3: After some experimenting, I now know what's going on. While on Prismatic with Weaver's Call equipped WITHOUT a Strand super equipped, [b]at the start of a session or after you die[/b], the new effect on Weaver's Call stops functioning. To make it work, you switch to a different subclass and then back. That means that at the start of a game instance, to get it to work, you have to immediately do this or have the Strand super equipped from the start. [b][u]There is no issue with this when using Weaver's Call on the normal Strand subclass[/u][/b]. So, this is a Prismatic-related issue when using a super that isn't the Strand one. A little bit of an issue there.

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

You are not allowed to view this content.
;
preload icon
preload icon
preload icon