Re: PR v0.85 Screenshots
Posted: 2009-04-05 01:18
Bunch of mines I missed out of pure like. Another reason not to type while driving 



McLuv wrote: ....
After getting about 100 meters over our runway (that's right Welshy, we weren't over the hills), a sly Havoc hits us with an AA missile. This wasn't a crash, rather a death 10 meters from the pad as I did a back flipping hatchet attack to try and save us. But the fire wasted us too quickly
PS, Welshy, I forgive you![]()
The first time yes, but this was the second timeShor0999 wrote:You were about 800 meters upWe probably did hit you over main but just didn't notice where we were. You got us back a few million times though.
![]()
I was sad panda.McLuv wrote:![]()
That was Carebear and Jake who killed you. Me and Matty kept getting owned so we just took a tankMcLuv wrote:The first time yes, but this was the second timeWe weren't exactly over the runway, but we were at most 200-300 meters up (I think lower, but I can't remember). Yea, we were a few hundred meters off of the runway too, so I'll let it pass. Besides, we were pushing you into a corner in which you had to do it out of desperation, it felt like
Was a fun round, though, all the same. Until I got a lagspike at main and died.
I think I we went with 3 deaths over all. 2 were near main (though the first was fine, because we were far away, and I saw you at least), the second one is pictured, and the last involved FPS going down to about 5, and the apache's odd way of tilting from side to side even when grounded, coupled with lagspike = fail
![]()