Report, edit, etc...Posted by BroodKiller on 2006-01-28 at 04:15:57
I've messing with some DATS recently (as if that was of any surprise) and when I consulted the specs for some value, I noticed that none of the 'Time'-related properties stored in different DATs (I run a wide search for it) had their time units defined. 
So, I sat down, thought for a moment, run SC a few times, and here are my findings:
#1-Unit's build Time, Tech research Time and both normal and 'factor' Upgrade Time properties are using 1/15th of a second as 1. That is, if you input, say, '150' , the research will take 150/15 = 10 seconds.
This can be easily guessed if you recalculate the Hex values against what StarEdit allows you.
#2-Weapons Cooldown time. Now, this was a real challenge. At the beginning I thought that this too may use the same unit as the others - 1/15 of a sec. This was not the case however (what I realised when I modded SC and checked that Cooldown of 150 does not make the unit attack each 10 secs).
Then came a boring and tiring process of checking each other possibilitiy: 16, 17, 18, 19 etc.
I'll shorten your pains and tell you right away - the cooldown is scaled using....1/23rd of a second! (which means that if you want the weapon to be used every 1 second, you need to input '23' as its cooldown).
Don't ask me why this is like that - Blizzard do have their own mysterious designs....
So, I sat down, thought for a moment, run SC a few times, and here are my findings:
#1-Unit's build Time, Tech research Time and both normal and 'factor' Upgrade Time properties are using 1/15th of a second as 1. That is, if you input, say, '150' , the research will take 150/15 = 10 seconds.
This can be easily guessed if you recalculate the Hex values against what StarEdit allows you.
#2-Weapons Cooldown time. Now, this was a real challenge. At the beginning I thought that this too may use the same unit as the others - 1/15 of a sec. This was not the case however (what I realised when I modded SC and checked that Cooldown of 150 does not make the unit attack each 10 secs).
Then came a boring and tiring process of checking each other possibilitiy: 16, 17, 18, 19 etc.
I'll shorten your pains and tell you right away - the cooldown is scaled using....1/23rd of a second! (which means that if you want the weapon to be used every 1 second, you need to input '23' as its cooldown).
Don't ask me why this is like that - Blizzard do have their own mysterious designs....
Report, edit, etc...Posted by Ermac on 2006-01-28 at 06:15:08
This really is weird...
Report, edit, etc...Posted by TERRAINFIGHTER on 2006-01-28 at 10:46:29
Nice find, now all we need is to solve flingy speed/acceleration times so we dont have to guess anymore
Report, edit, etc...Posted by BroodKiller on 2006-01-29 at 13:02:47
Yeah, it'd be nice to know these 'lil items. What I keep thinking (against everything and everybody) is that these should rather be thought of as drop-down menu items, and not digital values...dunno why I think like that tho...:/
Report, edit, etc...Posted by DiscipleOfAdun on 2006-01-30 at 09:49:27
Because you forget how speed is stored in memory. It should be a digital value. Accel, I don't know about.
Report, edit, etc...Posted by BroodKiller on 2006-01-30 at 14:51:51
Well, to my mind the 'storeing' itself has nothing to do with this. After all, all and every data is stored in the memory as digital value - It's the way the SC engine interprets these values that is the problem here. I Gotta think of it and try it out in some time...
Report, edit, etc...Posted by DiscipleOfAdun on 2006-01-30 at 15:41:04
Well, I believe speed is something along the lines of pixels per tick, or something like that. I don't know how we'd go about figureing it out though. Probably and accel of 1 so that the unit is always at its top speed, then try to figure out how far it has gone in a second.
And accel is probalby a time value, what unit I don't know. Figuring it out would probably take knowing what speed is, then finding a way to remove speed, so we know how long it takes to get going. I forget what a speed of 1 does to accel, but that might be an option. Or an insanely high speed, so it is quite obvious when it hits that high.
And accel is probalby a time value, what unit I don't know. Figuring it out would probably take knowing what speed is, then finding a way to remove speed, so we know how long it takes to get going. I forget what a speed of 1 does to accel, but that might be an option. Or an insanely high speed, so it is quite obvious when it hits that high.