Reilly Reese
#1 Top Forum Poster & Raiben Jackpot Winner
You're just saying that cuz it's similar to yours in the sense it looks like a halo ship :3
You're just saying that cuz it's similar to yours in the sense it looks like a halo ship :3
You're just saying that cuz it's similar to yours in the sense it looks like a halo ship :3
good for youForgot to mention this earlier but I stole a vaygr warhead bomber off TAW
Vaygr Centipede looks about as gross as its name implies...'yo deb what has trinova been up to'
mostly joint ops with FCM and a few of our guys dicking around on TAW breaking people's things. Here's some pictures.
Idle drones nice, wut a battleMultiple victories reported on TAW!
Over the past few days, Trinovan ships have launched repeated attacks on Vaygr space and destroyed multiple Vaygr vessels, including more than ten destroyers and a Vaygr scout craft which was attempting to reclaim systems lost to Trinovan forces prior. Along with this, a number of intimidation missions have been sortied against Vaygr ally Synch-Tron involving the loitering of ships multiple orders of magnitude larger than the Synch-Tron homebase right next to it.
Trinovan losses:
Small cloaker lost to Vaygr centipede turrets. (87 mass)
Port side turret on TTS Blue Ridge lost due to returning fire from Opposer class destroyers (100 or so mass)
Vaygr losses:
Opposer Class Destroyer (Logic JDI variant) (17k mass)
Opposer Class Destroyer (17k mass)
Opposer Class Destroyer (17k mass)
Opposer Class Destroyer (17k mass)
Opposer Class Destroyer (17k mass)
Opposer Class Destroyer (17k mass)
Opposer Class Destroyer (17k mass)
Opposer Class Destroyer (17k mass)
Opposer Class Destroyer (17k mass)
Opposer Class Destroyer (17k mass)
Opposer Class Destroyer (17k mass)
Spook Class Scout (500 mass) -Assin9 killed
Multiple claim stations and planets
nah they fought back, they just lost is all :^)Idle drones nice, wut a battle
Your faction's fault for leaving them defenseless, thenIdle drones nice, wut a battle
It is a well known bug that fleets will set themselves to idle after a server restart and even after a client restart.Your faction's fault for leaving them defenseless, then
nice, you are actually using a proper warship now.nah they fought back, they just lost is all :^)
190k mass worth of shit getting killed is 190k mass worth of shit getting removed no matter how you spin it broski
Can confirm, I saw the wreckage myself.Second off, we took the ships back to our base for salvage and at least one or two other players saw them and can verify this happened on TAW.
FlyingDebris staged the battle on his own buildserver, considering the Opposers were being distributed by someone who shall not be named for the sake of a standing agreement this is very possible
While this may not change the result of the battle, the screenshots FlyingDebris took of it question the authenticity.
Also that screenshot doesn't show them shooting, that red missile is going directly for one of the opposers, fleets do not friendly fire, so one or more of several things most likely happened.
It is a well known bug that fleets will set themselves to idle after a server restart and even after a client restart.
As it is our job to enlighten when that can happen, consider this duty: When you enter a ship into fleet and give it sentry or formation sentry command, the AI is on. When you log off, the fleet is in 'idle' status, however AI is still on. When enemy is within engage-able range or is firing upon the drones, AI turns on and engages with enemy.If the ships were without AI just floating in space, no one would care now, but idle AI, oh my.....