Peave [Phoenix] - vs - Pyrosisflame [ ] (TD: 3.927.384.500)

    • Top Solo

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • Peave [Phoenix] - vs - Pyrosisflame [ ] (TD: 3.927.384.500)



      New number 1 Solo, I dedicate this hit to Darkor as if it werent for you alerting me when you did i am sure we would have been too late :beer:

      Long story short ex phoenix member pyrosisflame unfortunately went inactive, removed from alliance and a plan was in motion to profit from his fleet sitting on his heavily defended planet.
      However we were not aware that Bfree had already started a relocation count down move next to pyrosisflame. As soon as i seen bfree appear i had to act as to me this was now all about taking the chance of the first hit on ex phoenix member away from bfree regardless of loses.



      Peave -vs- PyrosisFlame

      Attacker Peave

      H.Cargo............ 8.000
      L.Fighter............ 565.973
      Cruiser............ 15.178
      Battleship............ 8.659
      Bomb............. 2.225
      Destr............. 13.045
      Battlecr............. 11.596


      -= V S =-

      Defender PyrosisFlame

      S.Cargo............ 454
      H.Cargo............ 6.188
      L.Fighter............ 3.347
      H.Fighter............ 211
      Cruiser............ 61
      Battleship............ 2.080
      Recy............ 642
      Esp.Probe............ 1.285
      Bomb............. 1.858
      Sol sat............ 1.097
      Destr............. 2.269
      Death star............ 112
      Battlecr............. 1.022
      R.Luncher............ 310.000
      L.Laser............ 12.000
      T.Laser............ 20.000
      Gauss............ 320
      Ion. K............. 2.500
      Plasma............ 1.400
      S.Dome............ 1
      L.Dome............ 1


      - after battle -



      Attacker Peave
      H.Cargo............ 6.815 . . . . . .(lost: 1.185)
      L.Fighter............ 409.953 . . . . . .(lost: 156.020)
      Cruiser............ 13.310 . . . . . .(lost: 1.868)
      Battleship............ 7.808 . . . . . .(lost: 851)
      Bomb............. 2.021 . . . . . .(lost: 204)
      Destr............. 11.783 . . . . . .(lost: 1.262)
      Battlecr............. 10.439 . . . . . .(lost: 1.157)


      Defender PyrosisFlame
      S.Cargo............ 0 . . . . . .(lost: 454)
      H.Cargo............ 0 . . . . . .(lost: 6.188)
      L.Fighter............ 0 . . . . . .(lost: 3.347)
      H.Fighter............ 0 . . . . . .(lost: 211)
      Cruiser............ 0 . . . . . .(lost: 61)
      Battleship............ 0 . . . . . .(lost: 2.080)
      Recy............ 0 . . . . . .(lost: 642)
      Esp.Probe............ 0 . . . . . .(lost: 1.285)
      Bomb............. 0 . . . . . .(lost: 1.858)
      Sol sat............ 0 . . . . . .(lost: 1.097)
      Destr............. 0 . . . . . .(lost: 2.269)
      Death star............ 0 . . . . . .(lost: 112)
      Battlecr............. 0 . . . . . .(lost: 1.022)
      R.Luncher............ 0 . . . . . .(lost: 310.000)
      L.Laser............ 0 . . . . . .(lost: 12.000)
      T.Laser............ 0 . . . . . .(lost: 20.000)
      Gauss............ 0 . . . . . .(lost: 320)
      Ion. K............. 0 . . . . . .(lost: 2.500)
      Plasma............ 0 . . . . . .(lost: 1.400)
      S.Dome............ 0 . . . . . .(lost: 1)
      L.Dome............ 0 . . . . . .(lost: 1)


      Defender PyrosisFlame destroyed.

      The attacker has won the battle!
      He captured: 45.141.252 metal 80.091.055 crystal, and 33.685.748 deuterium.

      The attacker lost a total of 1.017.987.000 units.
      The defender lost a total of 2.909.397.500 units.
      At these space coordinates now float 492.521.400 metal and 310.024.800 crystal.



      -= Result =-
      (Assuming the attacker got the debris..)
      Attacker gain (-lost units): -56.522.745
      The attacker lost a total of 1.017.987.000
      The defender lost a total of 2.909.397.500
      Total Damage: 3.927.384.500

      -= Harvest report =-
      Your recycler(s) (42.000) have a total cargo capacity of 840.000.000.
      At the target 492.521.400 Metal and 310.030.500 krystal are floating in space.
      You have harvested
      492.521.400 metal and 310.030.500 crystal.

      Advanced bilance
      Attacker lost.............gain..........difference
      671.455.000........537.662.652........-133.792.348
      303.451.000........390.115.855..........86.664.855
      43.081.000..........33.685.748..........-9.395.252
      --------------------------------------------------
      Summary: ..............................-56.522.745

      Defender lost.............gain..........difference
      1.809.743.000................0......-1.809.743.000
      865.825.000..................0........-865.825.000
      233.829.500..................0........-233.829.500
      --------------------------------------------------
      Summary: ...........................-2.909.397.500

      The post was edited 1 time, last by peave ().

    • The long story...

      Unfortunately a long standing member had gone inactive which as we all know is a no-no in this game. But we weren't quite ready to boot him even after 11 days. I probed all of his planets to see if they were profitable targets and the one that really caught my eye was the planet with well over 250kk in resources and his entire fleet. I sent an ***Alert*** to Peave to have him take a look which he did. He even lanx'd it and told me there was no fleet activity. That got me wondering about the 2 planets within my lanx range in 2 other galaxies so I took a look at them as well. It's been a bit quiet in 'Origin' for the most part recently but all the top dogs were still in the hunt.

      I saw that a player had indeed launched attacks at both of them using RIPs. 10 launched at PyrosisFlame in G1 and 15 RIPs at him in G4. It just so happened that my fleet was in so I formulated a plan to ward off the two attacks by doing an ACS Defend. I knew the attacker would likely 'safety probe, see the ACS fleet and recall' so to save DU I targetted only the 15 RIP fleet. Had I known what would happen next, I would have ACS Defended both the 10 and 15 RIP targets.

      No safety probe, no fleet delay and no recall while my fleet sat over the G4 planet! 15 RIP-Kill! I didn't post it as it seemed to small and I've never been much for bragging anyway. That's when I decided it might be advantageous to move a planet next to PyrosisFlame's big target as now I knew it was only a matter of time. But I made the mistake of targeting a move into the same system as the target negating any possibility of another ninja so after cancelling the move I decided to wait for the move timer to time out (48 hours) rather than select another planet to move. Besides, there was no immanent threat yet and Peave had it under his lanx so if there was, we would know.

      We worked out a plan to take our ex-member's fleet down safely using our two fleets together to maximize profit and minimize losses and I prepared for a new planet move once the timer had expired. But with less than 9 hours left before the move, Peave told me bfree had moved into the system right next to the target fleet. And within 24 hours from arrival, bfree would have his jumpgate active. We could no longer wait. Peave chose to go it alone. The rest is history!

      Congrats, my friend, on an excellent takedown. Just wish I had let the original planet move go though as planned so I could help.

      And for the poor soul who lost his 15 RIPs, GLOTR. If you see this, you'll know who you are!