Related Games: Fortnite
Related app/team name (not a must if you want to keep it private): FortniteAI
Issue Description: During certain matches the phase info event will not be triggered
Steps to reproduce: If you play a match and at the end of the match hit “ready up” without going back to the lobby and do this a few times you will usually get one match that does not have any phases triggered. At the end of the match if you were to then click “ready up” again the next match would usually have it. It happens randomly, sometimes it occurs the second match and other times it can be the tenth. For testing, we just keep landing and jumping off from a tall location to end the match quickly so we can test it. We tested quite a few times to and were looking at the direct events that were coming in from the listener to ensure that the events were not being triggered.
Impact for my app: show-stopper
Do you currently have a workaround? Nope.
Please reproduce and attach a zip package of your OW client logs
Will attach shortly.
@danv hi, we tried to reproduce this now, did about 10-15 sessions just killing myself each time and used the “ready up” button as mentioned by you.
Unfortunately, “phase” event worked fine each session, it never missed.
The only thing that I did find is that the inventory count event was sometimes skipping a sessions, which is a bug in and of itself, but it’s a separate subject.
I forgot to mention that during our testing we have found this to happen in squads and duos. I haven’t yet tested extensively in solos to determine if it also happens there.
@danv Re-creating this in squad/duo is far far far more time consuming and cannot be done quickly…
We tried our best with around 5 sessions straight and the phase events continued to work for us without any issue.
If this is consistently happening to you we can provide a gep_fortnite.dll to try and debug it. Would you like to do that? it’s a special version of the dll that generate logs with much more details. That might help to “catch” more hints about what is causing the issue.
Yeah we’ve already forwarded your logs to one of our devs, and it’s in his weekly tasks to look at it.
Hopefully we can get a fix out by the end of the week.