Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- so it can be expressed as( [total mass income] \ [total buildpower consumed]) * ([time] * [unitbuildpower required])
- yeah so its
- [aia]Anaryl:
- so if [total mass income]/[buildpower] = [average buildtime] we can derive that buildtimes are smaller will receive higher priority because bt = ubt/bp
- bp/m ?
- m/bp
- mass is distributed to bp where it has most effect
- think of it as the thing likely to finish fastest gets priority
- and what is buildtime prey tell!
- 
- [aia]Anaryl:
- no actually express it mathematically fellas
- 
- [aia]Anaryl:
- what *is* bt
- so if bt is [unit build time]/ [buildpower] then ?
- yes so you have [total eco mass] / total bp
- thats because mexes need e to run
- so if [total mass income]/[buildpower] = [average buildtime] we can derive that buildtimes are smaller will receive higher priority because bt = ubt/bp
- yes so you need to get the unitbuildtime for the defence issile
- kay yeah so the build time is 5 ins for SMD yeah?
- so its 1080 * (5*60) = [total buildpower consumed]
- so mass translatres to buildpower over your engy's bp
- 
- [aia]Anaryl:
- which is just bp*time
- 
- [aia]Anaryl:
- the less efficient assisting is and the more set that mass cost is
- 
- [aia]Anaryl:
- so if we considered 1080 to be virtually unassistable - as it requires a total of ...
- 
- [aia]Anaryl:
- 1080*(4*60) = 324000
- 
- [aia]Anaryl:
- so thats total build power consumed
- if you then factor that into [total mass income] / [total economic buildpower]
- [aia]Anaryl:
- that number should let you determine how much preference it gets mass per buildpower
- so if you have a total mass income of 100, with 3 draws 1 T3 factory drawing 90 build power 1 SMD drawing 1080 build power at - 15 second off 1 T3 mex 18 M - how is the mass distributed
- 259200 / 1080 = 240 [unit buildtime from factory]
- for T3 factory draw = [factory buildpower] / [unit mass cost] in this case
- for missile draw it is 1080 / 3600 = - 15
- total build power draw is 1080 + 90 = 1170
- total mass draw is 3600 +
- so if buildtime is [unit build time]/ [factory buildpower] then
- we can infer that mass per build power is [unit build power cost] / [total unit mass cost] = ... 72
- need more functions
- Percy:
- totalBuildPowerConsumed: [factory build time]240 * [factory build rate] 90 = [total buildpower consumed] 21600 + 10% delay = 23760
- FactoryBuildTime: [Unitbuildtime]6000 / [factory build rate] 90 = [factory buildtime] 240 seconds + 10% 264
- DelayedFactoryBuildtime: [UnitBuildtime]6000/ 90 = 264
- MassDrainPerSec: [Unit Masscost] 1280 / [Factory Build Time] 240 = 5.33
- DelMPerSec: 1280 / 264 = 4.84...
- " " " " : [] 3600 * 240 - 15
- BuildConsumePerSecond ([[factory build rate] 90 / [totalbuildpowerconsumed] 21600]) = 240 bp consumed per second
- DelConPerSec 90 / 23760 = 264
- TotalDraw [total mass economy]18 / [total mass draw](15 + 5)20 = 0.9 (90%)
- [TotalBuildPower] 1170 / [total mass draw] 20 = 58.5 (9 = 65?)
- SMD.Buildpower = 1080
- SMD.Masscost = 3600
- SMD.MassDrainPerSec = 15
- SMD.FactoryBuildTime = 240 seconds(4 minutes)
- SMD.BuildConsumePerSecond = 240 units of bp consumed per minute
- BuildPowerConsumedPerMassDraw: [totalbuildpower]259200/[standard mass draw]15 = 17280 of build*cost* per 1 fullsecond of masscost at 1080 buildpower
- delayscan be applied as either time damage (thus for each 10% of mass overdraft the build cost remains static as the multiplying (1 second per masscost can become 1.06 of full mass cost)
- this might be demonstrated with a 50% overdraft the buildtime for that second blows out to 2 seconds or 50% of that seconds build cost 8640(est.) a rather serious reduction in timebuilt which represents simply the progress towards totalbuildcost.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement