when dustin browder said they're going to fix the ingame clock "pretty soon" so it will be real time instead of blizzard time, i didn't thought i had to wait until hots, because you know, how hard could it be to fix this with a patch or something. now we have the beta and there is still no change on the ingame clock.
seriously, the fact that blizzard is not able or not willing enough to fix the easiest thing about WoL you could think of is ridiculous. is it because we are not vocal enough about it? is it because nobody cares? why can't blizzard JUST ONCE make a useful qol change without the community demanding it.
and no, i'm not making a big deal out of it. i couldn't care less about the ingame clock. it's not about the clock, but about how less blizzard cares about their products. and it's not even like we expected anything special. we all know they don't care as much as they used to anymore, but not fixing the ingame clock? seriously blizzard? there is no reason at all to not fix this. not for a multi million dollar company like blizzard.
in times of more and more quality f2p games rising, it's absurd to realize that i'm gonna spend at least 40 euro for a game with a broken clock. it's almost funny.
On September 07 2012 03:13 Charon1979 wrote: whats wrong with "blizzard time" when everything ingame is measured in "blizzard time"?
whats wrong with blizzard time? how about measuring everthing in real time, how about that? i don't thing it's too much to ask for. lol, even dustin browder admits that it's stupid.
On September 07 2012 03:16 Plansix wrote: Clearly because it was not fixed during the first three days of the closed beta, it will never be fixed. It is totally a reason to not buy HotS.
wanna bet? besides, i never said in not gonna buy it.
There must be an option to toggle between Blizzard time and real time, and it will change all ingame descriptions to real time or vice-versa. I mean if we chose real time format, it will convert time displaying at description for worker build process from 17 seconds to 15 (for example!)
I think Blizzard is comfortable with Blizzard-time. After all, why should Blizzard change their ways? Why not the rest of the world so inconsiderate to use a different definition of time?
I bet you know everything about the programming aspect of the clock. Ever thought that it might be not as easy as you think it is, else... it would be done?
You can easily play in real-time, except everything will be slower (obviously). For them to 'fix' blizz time they're going to have to change EVERY timing (build times etc), I doubt is as easy as 'LETS FIX THIS SHIT NOW'
On September 07 2012 03:13 Charon1979 wrote: whats wrong with "blizzard time" when everything ingame is measured in "blizzard time"?
whats wrong with blizzard time? how about measuring everthing in real time, how about that? i don't thing it's too much to ask for. lol, even dustin browder admits that it's stupid.
So a Spires tooltip wont state 100 seconds build time but 71,94 seconds... seems legit
On September 07 2012 03:21 Duval wrote: I bet you know everything about the programming aspect of the clock. Ever thought that it might be not as easy as you think it is, else... it would be done?
You can easily play in real-time, except everything will be slower (obviously). For them to 'fix' blizz time they're going to have to change EVERY timing (build times etc), I doubt is as easy as 'LETS FIX THIS SHIT NOW'
i'm not stupid, i never said it take zero effort to fix it, but don't make it sound like it's too hart for blizzard to fix it in a reasonable amount of time, because its not, and they failed to do it. it's basically their job, and they failed to do it.
i don't have to know anything about programming to know that progamming a clock is a lot easier than programming new units and all the other new features in HotS.
On September 07 2012 03:13 Charon1979 wrote: whats wrong with "blizzard time" when everything ingame is measured in "blizzard time"?
whats wrong with blizzard time? how about measuring everthing in real time, how about that? i don't thing it's too much to ask for. lol, even dustin browder admits that it's stupid.
So a Spires tooltip wont state 100 seconds build time but 71,94 seconds... seems legit
how about make it 70 seconds? this certainly wont break the game
Btw, from a programming point of view this isn't hard. The reason Blizzard is hesitant has to do with the default speed being different, so nice values like 40 seconds become like 33 seconds, so it's weird.
The one downside of switching to real time is that time-resolution will be lower. Example: In ten minutes of real time we have 600 seconds (600 points of time) to which we can correlate the game events to. In Blizz time that resolution is about 40 % larger, so ten real minutes is about 14 bliz minutes, which means that we currently have 840 points of time to correlate events to.
Not that this is extremly important in pracice though...
Sigh, people bitching about worthless shit. So great. As has been stated, if they change it from blizzard time to real time they have to update every single tooltip about buildings and units. Why does it matter that we use blizzard time? It doesn't. It's not like it somehow affects your real life. Can't believe there's actually a thread on something that matters as little as this.
Do you want it to take 12.325 seconds to build a worker? Blizzard time is already ingrained in the game. They would need to change the time it takes to build, cast, recharge, or do ANYTHING. This means they would have to retest for balance as well as rewrite a bunch of things. Just leave it the way it is. There is absolutely no problem with having different times, especially with an in game clock.
On September 07 2012 03:13 Charon1979 wrote: whats wrong with "blizzard time" when everything ingame is measured in "blizzard time"?
whats wrong with blizzard time? how about measuring everthing in real time, how about that? i don't thing it's too much to ask for. lol, even dustin browder admits that it's stupid.
We have possibly hundreds of vital strategy timings memorized that are measured in blizzard seconds. Changing it now is retarded.
This is something that should have been changed in the WoL beta. What's really funny is that at the start of that beta, normal time didn't even exist. That's right, there was no speed setting in the game that would produce an scv in 17 seconds, despite what the tooltip said. Fast and slow speeds existed, but no normal. For some reason, someone at Blizzard found it important to fix that, but not to address the fact that everyone plays in faster and it screws up the clock and apm readouts as a result. It would be trivially easy for the tooltips to update themselves depending on game speed and to have a clock and apm measurements in real time. This wouldn't affect anything gameplay-wise -- it's simply cosmetic. The tooltips would have to be rounded off and they wouldn't be 100% accurate, but rounded tooltips already exist in the game as it is.
I would like the option/or the game to be in real time - that way I would have a better sense for how long abilities last based on tooltips (e.g. Force fields come to mind, where you can't count in your head in real time seconds (except if you convert) to know when to put up the next one / know when the enemies FFs run out - yes we all do have some idea of how long it is based on experience but it'd be nice to have a tooltip "duration" that you can use without looking at the clock in game).
As for strategy timings, I agree, but a lot of these timings (especially after 10min mark) will change due to new units in HotS and possible balancing that will happen during beta. I still agree though, it will be a bit of a hassle at first - but still I have a better measure in my head of how many real time minutes have passed than in game minutes etc.
I prefer it to be real time.
On September 07 2012 04:14 two_sheds wrote: The one downside of switching to real time is that time-resolution will be lower. Example: In ten minutes of real time we have 600 seconds (600 points of time) to which we can correlate the game events to. In Blizz time that resolution is about 40 % larger, so ten real minutes is about 14 bliz minutes, which means that we currently have 840 points of time to correlate events to.
Not that this is extremly important in pracice though...
Starcraft 2 must have way more points of time to correlate events to than mere seconds (just that in replays you can only jump to different times in terms of seconds). Otherwise an event that you do at 0.5 game time seconds would be in effect 0.5 seconds later or if this was the case in replays all events that happened on decimal points would accrue to the next second. So I believe changing to real time wouldn't change anything in terms of time resolution
On September 07 2012 04:17 Infernal_dream wrote: Sigh, people bitching about worthless shit. So great. As has been stated, if they change it from blizzard time to real time they have to update every single tooltip about buildings and units. Why does it matter that we use blizzard time? It doesn't. It's not like it somehow affects your real life. Can't believe there's actually a thread on something that matters as little as this.
if its worth asking dustin browder in an interview its worth making a thread about it. if it wouldn't matter, /r/starcraft wouldn't have ask this question, right?
i don't get what you are trying to argue here. dustin browder said it's stupid and he said they're working on it. so it matters to them too. they wouldn't hire someone to work on it if they would have a problem with updating all tooltips, thats the most obvious consequence of fixing the game clock. so there is this guy called allen, and he is working on it for "many many months" now, and "its driving him crazy". and now, here we are, hots beta, and my question is: what happend? how incompetent you have to be not being able to fix the easiest thing in the world despite working on it for months?
EPT
