{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by PilksUK:
7/28/2018 8:47:25 PM
1
....the script doesn't do a good job at preventing long streaks of the same event.....That is not a bug that just means the script needs improving a bug is something that breaks what the script is meant to be doing the fact its working as coded means its not a bug which is why they said they would work on it as it would most likely need a re code to improve the system.
English
-
That is semantic garbage and PR spin. Either they intend to have it spawn back to back Cabal events for hours when the quest is active or they don’t. They can just tell us what it is: on purpose or bad code. Then they can tell us if they plan to fix it. If they don’t then people should understand that their time isn’t respected so they can decide if they want to waste it waiting on IO or invest it into something else.
-
Your thinking is so off. Streaks in public events did not matter before adding in this quest. And yes they probably did want streaks to happen so it wasn't just always every other time. But there was no reason to prevent a long streak at that time. Because without this no would ever care or notice. You also have to realize no one has complained about this in almost a full year of the game being live.
-
You mean that the team implementing the new event shouldn’t know how the starting point for the event works?
-
No I'm saying that the 2 were coded from different departments at different times. And not enough testing the outcome. Undesirable results are not necessarily something broken in the code.
-
What is your point? Do you think Bungie is responsible for their game locking players out of the event for 5 plus hours each week because of the PE RNG system?
