devtrackers.gg
Description Banner gadgets acting as respawn points disappear earlier than intended.
Platforms All
Workaround None
Discussion Reddit
...
Description Banner gadgets acting as respawn points disappear earlier than intended.
Platforms All
Workaround None
Discussion Reddit
...
Description Retrieve the Data Missions will sometimes be unable to start normally which prevents players from progressing in the mission.
Platforms All
JIRA FORT-259608
We’re aware of this issue, and we will be fixing it. As we’ve said before, we will be getting to most reactive effects and fixing them for StW. Thanks for the report though!
Hey, all!
We're posting to let you know that we've released a maintenance patch on PC to address stability.
Thanks! 🙂
External link →Well... were you trying to increase the amount of spawns for the ''no dancing'' event? I can only see that as the reason behind it, even though the spawns before were perfect enough.
There is supposed to be a slightly higher number due to the event. Currently the amount that are actually spawning feel higher than the intended number. We're gonna take a look at the spawns and see what's up with that.
THIS IS AMAZING
so many references
We're taking a look into the amount of lobbers that spawn in zones. Definitely feels higher than intended.
- **Explanation**: Skins, backbling and pickaxe from BR aren't being applied locally in the game, but appear fully functional in the locker. *it seems it is only locally since you can see other players skins in the mission*
- **Evidence**: https://imgur.com/a/ZgRq8ZC
- **If reproducible, how**: Applying a skin, backbling and pickaxe from BR and entering a mission.
- **Platform*\*: PC
Thanks for the report! I've passed this along to our QA team to make sure it's something they're aware of.
**Explanation**: Storm King’s Onslaught still bugged. The projectiles not seeking the target head. Sometimes they turn to the ground. This since v12.00
**Evidence**: shooting hucks with the Storm King’s Onslaught in regular mission
**If reproducible, how**: same as above
**Platform**: PC
Thanks for reporting this. I've sent this over to our QA team to make sure they're aware of this issue.
