Forged Alliance Forever

Re: Unit DB

2015-11-11T21:51:56+02:00

The Unit DB needs an update since the last patch. 'Cause I didn't notice the few changes in Aeon, Cybran and UEF informations.

Statistics: Posted by Kaeden — 11 Nov 2015, 21:51

Re: Unit DB

2015-05-12T02:04:41+02:00

solarflare_nz wrote:
I moved servers around and didn't redirect this url properly.

it was a cool project but I don't know if there's any point to keeping it running?

Stick it on GitHub if you haven't already. The unitDB needs a revamp at some point, maybe your code will come in handy.

Statistics: Posted by ckitching — 12 May 2015, 02:04

Re: Unit DB

2015-05-08T12:19:20+02:00

I moved servers around and didn't redirect this url properly.

it was a cool project but I don't know if there's any point to keeping it running?

Statistics: Posted by arkitect — 08 May 2015, 12:19

Re: Unit DB

2015-03-05T05:47:29+02:00

I don't think he's doing this anymore. Kinda sad cause I did like the site.

Statistics: Posted by Reaper Zwei — 05 Mar 2015, 05:47

Re: Unit DB

2015-03-05T04:24:27+02:00

this url crashes:
unitdb.solarflare.co.nz

Statistics: Posted by nine2 — 05 Mar 2015, 04:24

Re: Unit DB

2014-06-13T12:13:52+02:00

If I remember correctly, the Cerberus third gun is listed as rack. The unit has muzzle salvo size = 2 and rack salvo size = 1. This is awkward, because all three guns shoot at the same time, but i think it works that way.

The weapons with damage over time are not described / calculated properly
For instance, Janus:
Bomb: 60dps (range 60) AOE3
Napalm Carpet Bomb 5 projectile damage; 8 bombs (splitting into 15 projectiles) every 10s,

Real description should be :120 DPS (range 60 ; AOE 3)
Napalm Carpet bomb : 75 initial damages + 5 damage 15 times over 2.5 seconds = 150 damages
8 bombs (=1200 damage total) every 10 s

Same for Scorcher. It should be :
Bomb: 87.5 dps (range 40) AOE3
Napalm Carpet Bomb : 47.5 initial damages + 4 damage 10 times over 1.5 seconds = 87.5 damages
4 bombs (=350 damage total) every 4 s

Statistics: Posted by pip — 13 Jun 2014, 12:13

Re: Unit DB

2014-06-13T11:46:49+02:00

found a bit of time just now to fix up some calculations.

the muzzles for the cerberus is weird. There are 3 muzzles, muzzlesalvosize = 2, and rate of fire = 3, yielding 3 projectiles every 0.3s. I am assuming that if there is more than 1 muzzle, muzzlesalvosize is ignored due to the order in which the engine handles weapon logic? anyone know?

Statistics: Posted by arkitect — 13 Jun 2014, 11:46

Re: Unit DB

2014-06-11T04:11:03+02:00

Could you add the following functionality: The user can not only compare units to each other, but calculate the cost of desired army compositions, builds, etc.

I guess the least work wold be an implementation such as:
"Calculate Cost" checkbox on top (in unused white space)
If it is checked, then the total cost of all units in the comparison footer are added (based on their quantity) and displayed in the header. (Summed separately over mass-cost, energy-cost, build-time)
Furthermore it should unhide an edit field (which is hidden and set to 1 as default value, when the div is created) on every unit in the comparison footer.
If it is checked a "Calculate again" button is shown on the top to call the sum function (with possibly new quantity values) again.

Statistics: Posted by Fernest — 11 Jun 2014, 04:11

Re: Unit DB

2014-06-03T11:06:45+02:00

Thanks, I am slowly tidying up all the calculations as I get time

Statistics: Posted by arkitect — 03 Jun 2014, 11:06

Re: Unit DB

2014-06-02T00:42:06+02:00

Good stuff so far. I like the double click function, a lot easier then pulling things down all the time. like those missile stats too, easier to be able to see them then have to remember them. Things that would be nice to see added in the future(if you don't mind) would be the build time of units and the build power of units.

Statistics: Posted by Reaper Zwei — 02 Jun 2014, 00:42

Re: Unit DB

2014-05-31T02:28:46+02:00

and you're right about the zthuee. someone commented out the creation of the child projectile on same trajectory as parent, thus reducing the projectiles by 1 and only leaving the spread projectiles.

Code:: # One initial projectile following same directional path as the original #self:CreateChildProjectile(ChildProjectileBP):SetVelocity(vx, vy, vz):SetVelocity(velocity):PassDamageData(self.DamageData)

Statistics: Posted by arkitect — 31 May 2014, 02:28

Re: Unit DB

2014-05-30T14:28:52+02:00

Hehe, it seems that you're right for the lobo, but I rechecked for the zhtuee, and I see only 5 projectiles (also when I shoot at a factory, it deals 225 damages = 45 *5, and not 270). Maybe their code is different.

Statistics: Posted by pip — 30 May 2014, 14:28

Re: Unit DB

2014-05-30T13:42:47+02:00

pip wrote:
Just launch a game and count the projectiles that fall on the ground when you ground fire a lobo and zhtuee, you'll see that the parent projectile doesn't hit the ground.

yip, did that. for lobo there are 5. The initial projectile is destroyed above the ground, and 1 to replace it on the same trajectory is created. 4 more at random trajectories are then also created.

Statistics: Posted by arkitect — 30 May 2014, 13:42

Re: Unit DB

2014-05-30T12:06:36+02:00

Just launch a game and count the projectiles that fall on the ground when you ground fire a lobo and zhtuee, you'll see that the parent projectile doesn't hit the ground.

As for nuke damage, it's all at the bottom of the unit bp, in these parameters (here for the Sera t4 nuke):

NukeInnerRingDamage = 1000001,
NukeInnerRingRadius = 45,
NukeInnerRingTicks = 24,
NukeInnerRingTotalTime = 12,
NukeOuterRingDamage = 7500,
NukeOuterRingRadius = 60,
NukeOuterRingTicks = 20,
NukeOuterRingTotalTime = 5,

To sum up, nuke total damage = Nukeinnerringdamage + nukeouterringdamage and total AOE is nukeinnerringradius + nukeouterringradius.

Statistics: Posted by pip — 30 May 2014, 12:06

Re: Unit DB

2014-05-30T05:44:34+02:00

Thanks pip, one the projectiles though, the lua code for OnImpact is:

Code:: # One initial projectile following same directional path as the original self:CreateChildProjectile(ChildProjectileBP):SetVelocity(vx, vy, vz):SetVelocity(velocity):PassDamageData(self.DamageData) # Create several other projectiles in a dispersal pattern local numProjectiles = 4 local angle = (2*math.pi) / numProjectiles local angleInitial = RandomFloat( 0, angle ) # Randomization of the spread local angleVariation = angle * 0.35 # Adjusts angle variance spread local spreadMul = 0.5 # Adjusts the width of the dispersal local xVec = 0 local yVec = vy local zVec = 0 # Launch projectiles at semi-random angles away from split location for i = 0, (numProjectiles -1) do xVec = vx + (math.sin(angleInitial + (i*angle) + RandomFloat(-angleVariation, angleVariation))) * spreadMul zVec = vz + (math.cos(angleInitial + (i*angle) + RandomFloat(-angleVariation, angleVariation))) * spreadMul local proj = self:CreateChildProjectile(ChildProjectileBP) proj:SetVelocity(xVec,yVec,zVec) proj:SetVelocity(velocity) proj:PassDamageData(self.DamageData) end

it definitely looks to me like it creates 5 projectiles after impact. 1 on same path as original and 4 in random directions?

edit: this is for lobo, TIFFragmentationSensorShell01

edit: do you know where nuke damage is specified? I can't seem to see it.

Statistics: Posted by arkitect — 30 May 2014, 05:44