Page 2 of 2
Re: SM balancing questions: Orbital Bombardment and DropPod
Posted: Wed 19 Feb, 2014 7:21 pm
by Wise Windu
It does 500 melee_heavy damage in the smaller radius (6), which means 250 damage to vehicles. Plus, it does 30 melee_heavy dps (so 15 dps to vehicles) in the radius of 4 while it lifts stuff.
I was just talking about where Orkfaeller's ogryns were, which was on the outer edge of the beam (likely radius 9 or 10), which deals 185 piercing. I'm aware of the damage it deals.
Re: SM balancing questions: Orbital Bombardment and DropPod
Posted: Wed 19 Feb, 2014 8:32 pm
by Arbit
Hrm... I've tested it a few times now and a pred will get killed by a single beam (700 HP) and an upgraded pred will survive with 55 HP (down from 900 HP, so 845 damage).
I managed to get one terminator caught in the periphery of the beam and it did 150 damage.
So, uh, I don't know WTF is going on.
Also, fun fact: your units can be snared by your own OB, but only when the beam first appears. You can walk your own units into the center if you like.

Re: SM balancing questions: Orbital Bombardment and DropPod
Posted: Wed 19 Feb, 2014 9:24 pm
by Wise Windu
Huh, interesting.
Re: SM balancing questions: Orbital Bombardment and DropPod
Posted: Wed 19 Feb, 2014 10:12 pm
by Forestradio
Orbital Bombardment does explosive_pvp damage to my knowledge in elite
Re: SM balancing questions: Orbital Bombardment and DropPod
Posted: Wed 19 Feb, 2014 10:40 pm
by Wise Windu
So it does...
I was looking at the wrong version of it. 150 explosive on the outer, and 500 explosive on the inner radius.
Re: SM balancing questions: Orbital Bombardment and DropPod
Posted: Wed 19 Feb, 2014 11:17 pm
by Myrdal
The DoT also does 195 explosive dmg over 6.5s in the inner most radius so Arbit got it right with 845 = 500 + 150 + 195.
Re: SM balancing questions: Orbital Bombardment and DropPod
Posted: Thu 20 Feb, 2014 1:00 am
by Nuclear Arbitor
i was under the impression that it only snared at all when the beam first lands; after that you should be able to walk around. probably part of the issue.