Loading...
  OR  Zero-K Name:    Password:   

Post edit history

Units archetypes - statistical analysis

To display differences between versions, select one or more edits in the list using checkboxes and click "diff selected"
Post edit history
Date Editor Before After
5/3/2018 7:47:44 PMPLrankZenfur before revert after revert
5/3/2018 7:45:06 PMPLrankZenfur before revert after revert
Before After
1 I didn't want to use "Maneuverability" as it's long word. I'll call it "Agility", and "Speed" instead "Velocity". 1 I didn't want to use "Maneuverability" as it's a long word. I'll call it "Agility", and "Speed" instead "Velocity".
2 \n 2 \n
3 I've mentioned I'm going to use only per/cost values. My main question was whether to use top table or bottom table? I'm still not sure whether to use "Agility" stat. 3 I've mentioned I'm going to use only per/cost values. My main question was whether to use top table or bottom table? I'm still not sure whether to use "Agility" stat.
4 \n 4 \n
5 I also wonder whether I should characterise each class on separate screen or all on one. 5 I also wonder whether I should characterise each class on separate screen or all on one.
6 \n 6 \n
7 Godde: shouldn't be HP*DPS/Cost instead HP*DPS/Cost^2? 7 Godde: shouldn't be HP*DPS/Cost instead HP*DPS/Cost^2?