Just to follow up, while this change will remain in effect, we're going to watching feedback and looking at data to determine the best next steps to take. Give it some time, let us know what you think, how is defending going, is that much harder, do you like that challenge, etc...
For clarification, will Flingers still throw Huskies in the next patch, or will that be removed to make Flingers as they were before the .20 update? I think most players would agree that Flingers throwing Huskies buffs them significantly to the point of being more artificially hard / frustrating than challenging.
Since this is currently by design, flingers will stay as the currently are in this update.
JFC. I love this game but how patched together and borked is this freakin software?
Im not a game dev personally and i dont work with code. But i have dabbled in some code work in C++ personally for school and other side projects. While i cant speak to how it all works in Fortnite, i can say you'd be amazed how small changes in one place can have an effect elsewhere.
Hey Folks,
The other day i posted that the team was looking into this issue and I presumed that this was uninteded, i was incorrect. Here is an update directly from the dev team.
The Dev team saw these reports and investigated to see if something changed in this update that may have tweaked what Flingers throw. After digging into the data, they confirmed that Flingers are intended to be able to throw basic Husks, Husky Husks, Pitchers, Beehive Husks, Zappers, and Nurses.
Note that the Propane Husky and Riot Shield Husky cannot be thrown - only the basic Husky.
Looking at the file history, the data setting which husk types the Flinger is allowed to throw has only been changed a few times since launch (to add the Zapper and Nurse back when those enemy types were added to the game) and the Husky has been marked throwable since before the launch back in 2017.
Our best guess right now is that there was a long...
Read more External link →Hey can you send a DM to me with your user name. Team has been looking into endurance issues.
There are tools being implemented to help get an understanding when v23.30 launches in regards to the performance issues players have been seeing. Obviously the team is still looking into the cause but ill say now, its unlikely anything changes in the next update. The best goal for a resolution would be v23.40. But thats only if a root cause is found and fixes are implemented and tested in the next couple of weeks.
And on a last note, i bring issues up every meeting to get an update on where they stand and insure someone is working on them. Once again bugs have priorities and some issues that are small might linger others not. Example here are the terrain issues in the new zone. Its expected majority of those issues like the instant eliminations or objectives under the ground are resolved in the next update. Once reported yesterday the team work extremely hard to make sure the fixes got into the next update vs needing to wait until 23.40. With that hard work on terrain issues. It means something that wasn't as high of a priority was moved down and might still linger. Its an extremely tough balance but the dev team does the best job striking a balance based on lots of factors, including my feedback from the players.
Read moreThe team was off for multiple weeks during the winter break, when we got back there was a lot of catch up to do. I started informing folks of the performance issues mid week when we got back. The next week the v23.20 patch was already in whats considered "hard lock" in game dev speak that means the build is completed and no one can make any changes. This is for certification reasons on console and a variety of others.
So yes, that means all the performance issues were still and always going to be in v23.20. The team continues to look into the data to determine a cause. These performance issues aren't a STW issue alone but are across all of Fortnite. Its being looked into but there shouldn't be an expectation that this issue gets resolved magically in a few days when we're still fully investigating the issue. Its just not how game development works with when patches get locked.
In terms of the flingers this was brought up today when i say the post yesterday regardin...
There are tools being implemented to help get an understanding when v23.30 launches in regards to the performance issues players have been seeing. Obviously the team is still looking into the cause but ill say now, its unlikely anything changes in the next update. The best goal for a resolution would be v23.40. But thats only if a root cause is found and fixes are implemented and tested in the next couple of weeks.
Agreed. u/FreightTrainUSA said that he has been telling the devs about the performance issues in every meeting, so for the devs to continuously make these trash changes while ignoring the actual problems THAT THEY KNOW ABOUT, it just seems like they hate us
Another good example is the flux unslot change. It was a bad change for two reasons:
Gold flux is already VERY scarce
It was a change made while DTB was (once again) unplayable and hadn’t even been acknowledged yet
It seems to me that the devs acknowledge anything remotely fun (Plasmatic discharger for example) within days, but actual issues go unspoken about for months on end
And que all the epic games worshipers coming to tell me to “sToP cOmPlAinIng!!”
The team was off for multiple weeks during the winter break, when we got back there was a lot of catch up to do. I started informing folks of the performance issues mid week when we got back. The next week the v23.20 patch was already in whats considered "hard lock" in game dev speak that means the build is completed and no one can make any changes. This is for certification reasons on console and a variety of others.
So yes, that means all the performance issues were still and always going to be in v23.20. The team continues to look into the data to determine a cause. These performance issues aren't a STW issue alone but are across all of Fortnite. Its being looked into but there shouldn't be an expectation that this issue gets resolved magically in a few days when we're still fully investigating the issue. Its just not how game development works with when patches get locked.
In terms of the flingers this was brought up today when i say the post yesterday regardin...
Read moreu/FreightTrainUSA Can you PLEASE PLEASE tell me if the team is aware of the Third Rail problems? it's really broken😔
yes this has been reported.
For a few of these map issues if you can send over your logs that would be great. You can follow the steps here. https://www.epicgames.com/help/en-US/fortnite-c5719335176219/technical-support-c5719372265755/where-can-i-find-the-fortnite-game-logs-a5720385466267?sessionInvalidated=true
Once you have the logs you can send a message with them to me via Discord. FreightTrain#6330
Appreciate it, but there is no reason to really be thanking me. As many in this post have pointed out, what i do is essentially part of my job.
With that said there is some misunderstandings about what my job is.
Im a community manager at Epic Games for Fortnite.
What that means is im covering the entire game, not just STW. I have a focus on STW in terms of writing the homebase status report among other things.
I have said this in plenty of my post in the past. My job is and always has been to be the connection point of the player base to all the teams at Epic, from development, marketing, etc.. and vice versa.
I have also said, that while i dont, and frankly am essentially unable, to respond to every single reddit thread, if i am tagged in something i am seeing it. Thats always been my goal.
After seeing feedback or bug reports or anything that is of value to the team, i share it in meetings, with our live QA team, etc... if i am ...
Read moreSure made it seem big if you teased it to Archer a week in advance. Just want to clarify something. Not mad at you, not mad at Archer, I'm mad at the higher up who told you to tease it a week in advance. Had it of been 3 days or so before the update, wouldn't've been all that bad. But I was expecting a small (I mean very small, like 1% of the roster) amount of weapons and heroes to be reworked to perform better in the endgame (I consider the endgame to be Power Level 100 and on) because endgame in StW is so incredibly boring and unoriginal. Not asking for another Warframe, in terms of combat loop, but at least something better than overreliance on traps!
No one told me to tease anything. I am the one who reached out in regard to the update. It was to inform the person mostly that the update was going to happen on the 18th.
We were off for winter break until Jan 3rd and I hadnt spoken to him or anyone during that time. When I got back i saw a few bug reports, mostly being the console performance issues. I figured I would reach out and give him a heads-up of when the next update was coming since players would be curious. I said the following:
"Next patch isnt huge in terms of length but i think everyone will enjoy it. Its set for the 18th fyi since MLK day is a monday and we're off"
I was then asked if there was something he could share with his community. I never spoil or share something im not allowed to, but i figured it would be fine to say that something "New" was coming. I said the following:
"You can share the word "New" 😂. So something "new" is your ...
Read moreI've passed this feedback along to the Dev team and they're thinking about how to make multiple copies of Campaign heroes easier to acquire.
So whats the question or issue here? She needs to get raised in rarity because of being a campaign hero or just want a better/easier way to get them vs RNG from a llama?
Hey folks,
We've seen the following reports and want to make sure these are all fixed as soon as possible. If you run into one of these areas, not including the two from the post below but a different one, please submit a bug report and send me a DM with your user name so we can find the report.
Thanks for the report, looking into this now.
Thanks for the report, looking into this now.
So the patch introduced bugs, but was fixed before the patch released?
Every single update produces new issues, even on BR. These issues are typically squashed well before players will experience them as the teams work on fixing them all while looking to address player facing issues.
When i use the term player facing i mean something you, as a player will experience. Like maybe there is a reloading issue, or a harvest issue, etc... obviously issues in the live game get a focus on being resolved but we also need to fix a variety of issues behind the scenes that as player, you'll never experience.
There are a lot more bug fixes but that just aren't player facing issues.
When our QA team is testing a build there could be crashes or a varity of other issues that get fixed for us to put out the patch. These are issues players never run into due to being fixed prior to the release of the update.
So yes, while in the patch notes only 1 issue listed in the update notes, the team is working behind the scenes to fix a variety of issues that players never know exist in the first place.
Hurdling is tied to BR, due to it being disabled for a few issues its also disabled in STW. once its put back on, it wll be functional in STW. Check the FNstatus twitter for updates.
devtrackers.gg