{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by Epicdudenxt2u:
10/24/2014 12:50:28 PM
1
The timer glitch is easily fixable by a few lines of code while those others are 100s of lines[spoiler]Trust me I'm a software engineer[/spoiler]
English
-
[spoiler]So am I[/spoiler]. Doesn't mean they have the time for it. What happened to this week's patch? I think they have their plate full with more game breaking things than just a timer not going to post rewards
-
Yeah but they could have put the patch out at the very beginning of VoG and yet they haven't when it would have been an easy fix. They watched the stream of the first people to ever do the raid and knew there was a problem yet after about a month (I think) they still haven't apllied a fix much easier than the bladedancer or mythlocast.
-
But those are the ones everyone is yelling about. They're pandering to the biggest voices in the room with nerfs, alterations, removing farming. They've done very little glitch fixing. In fact there was a whole patch that they used simply for better error logging for connection issues to sort out the THOUSANDS of people who still can't log in or play for more than 5 minutes. Far more worrying than a broken timer. Even if it is a simple fix. If its not priority 1, the dev team will be doing more important things. There are only so many hours in the day
-
Also they must have tested the Vault thousands of times before it went live and must have seen this. Why wouldn't they have fixed it then?
-
As a software engineer you should surely know that in-house testing is pointless- coders know how it should work and aren't good at rigorous testing. User testing also falls down because they do miss things. What if their testers never finished it 100% and did parts of it? What happens if between testing and release a minor change affected the end timer and nobody realised they were linked. It's not uncommon for such things to happen when there are lots of coders working on a large scale code-base
-
In the lore atheon controls time in the VoG so when you kill him time freezes. This is why when you die your timer doesn't tick down. Normally even after you die on a nightfall or strike your revival timer still counts to zero although you can't be revived.
-
And this happens in the vault too. It only doesn't on hard as a specific game mechanic to make more teamwork and right gameplay to overcome the challenge
-
Once you beat atheon and die after, even on normal you don't get a timer unlike in the rest of the raid.
-
Same goes for strikes. If you are dead when the boss does and the timer starts, your respawn clock stops and you can't be rez'd. I don't think that's an intentional part of it
-
No your clock doesn't stop, it continues to count down to zero. once it reaches zero you can't be revived. At least that's what I remember. It's easy to test though.
-
Edited by Brother Rhogar: 10/24/2014 1:47:07 PMAnd going by lore, aetheon and co. controlling and warping time, surely after his death would resolve time back to normal as the hierarchy of vex shows they all have a singleminded purpose that is controlled by the higher up units. Cut the head off the snake so to speak. Not to mention Kabr who mashed down a gorgon into a relic to create a stable pocket of space. So at the very least the guardians who won with a relic should be immune :]
-
