Roam members (18)
Spoiler
Anidien Dallacort - Osprey
Apo Bong - Atron
Flash Prime - Osprey
Flatline Kasenumi - Atron
Giacomo Belenos - Osprey
Gislind Havel - Moa
Jonathan Gusborn - Moa
Larkvi - Moa, 3IC
Marcel Eriker - Moa
Martindale - Moa
Nienke Solette - Moa
Tim NineOwls - Osprey
Tolerin Escipion - Osprey, Logi FC
Tungon Akeela - Moa
Tyrion Edwardes - Moa
Zairnix Onren - Moa
manda doomsslayer - Moa
Please let me know if something is missing/wrong in this list and I'll edit in!
another Unista was a bit late to the party. Next time, I need to put/link scout fits in the forum announcement post's description so that low skill point scouts can better prepare. Furthermore, I need to delegate latecomers to 2IC/3IC so that I can focus on getting the fleet going. In this case, the latecomer was lucky because of our scouts who needed a bit more time to prepare.
At form-up, some fleet members thought of bringing some points on their Moas and mentioned that over comms. Great thinking of them and I fully agreed. I asked two DDs to x up and we brought a bit more points which we needed.
The first destination was Akidagi since I had asked the Fleet Support program to put some reship contracts up in the neighbouring system (Ichorya). It was a huge improvement compared to earlier LowSec Roams as can be seen from the amount of content we had this fleet. While travelling to Akidagi, our scouts started to look for content.
On the recordings, I noticed that we can use a bit more talky talk. For the next fleet, I think I need to explain more about... basically, everything that happens. Furthermore, I assigned a vanguard on our way to Akidaki. In this case, before any kills/losses but yeah, I want to do this before undocking and preferably the ones who x-ed up for bringing points. Also, I plainly forgot to use the drones provided with the Moa. *facepalms*
We also did a bit of LSC promotion by going through Eugales. I recommend everyone to join at the Round Table coming Sunday!
Kills and Losses
Scouts reported 16 in local in ALD. Long D-scan report was, and I quote, "crowded". Ships listed were: one Malediction, two Ares', one Caldari Navy Hookbill, one Tristan, one Osprey Navy Issue and a Wolf. I asked our scouts to check the plexes, the ONI and one Ares were in a Large. I asked the scout to get tackle while the fleet was still warping to the ALD gate. I asked the vanguard to prepare to jump and asked how far the plex was from the gate. Definitely an improvement compared to the fleets a bit more than a week ago.
Plex was reported 5AU from the gate and I called the vanguard to Jump On Contact. After landing I asked the fleet to get an Atron which was warping off. Not sure why, because it would have got us a weapons timer...
Video 1
(21:09:58) Aldranette
Atron -4.06m
Atron -1.96m
Scout had pointed the ONI and I called the fleet to jump through and warp to our scout. Unfortunately, our first scout died rather quickly (14s) and the distance of the ONI and the Ares from the plex was only called after the fleet was warping to the plex. We landed 130km from the ONI and 220km from the Ares. I called anchoring up (also an improvement from earlier fleets) and asked the scout to reship in Ichoriya. Meanwhile, an Orthrus and an Imperial Navy Slicer landed at 100km. I asked the fleet to align to the NEN gate. The Orthrus was, unfortunately, able to catch our second scout, after which I warped the fleet to the NEN gate. The earlier reported Malediction landed at 100km just as we warped off. In hindsight, we might have got a good fight here, because gfs were thrown in local and the INS's pod jumped through the NEN gate.
While our scouts were reshipping I decided to wait for them in Akidagi at 100km from the sun. The new destination was Pynekastoh.
After re-shipping, we got on our way again. Our scout reported a Praxis and a Dominix on Long-range D-scan in NEN and an Imperial Navy Slicer jumping into AKI. We were just landing on the gate so I called to anchor up. Unfortunately, the INS uncloaked on the other side of the gate. As evaluation: we could never catch the INS unless we would alpha it. Next time, I should focus on the situation in the system we're about to jump into.
A Maller landed on our gate. Not sure why (probably to catch the Maller), but I decided to let the fleet jump into NEN and called for the vanguard to uncloak and orbit the gate at 10km. Nothing came in so I called to align to the HIK gate. When warping the fleet, a Macharial appeared on grid. The fleet held on the gate and our scout reported ten in local and a clear d-scan. The Macharial followed us. I called to pre-lock it and wait with engaging. The fleet put its Hard(ners on) and I called to anchor up. I noticed way too late that the Macharial was flashy and that we could engage without taking gate-guns. However, I still waited with engaging because of the weapons timer. I also noticed it was Bundspecht who is known for giving good fights at Ky's Sunday Funday fleets in the past.
A Praxis, Gnosis and Dominix then landed on our gate. I had a couple of options: 1) try to warp out and risk someone getting tackled or 2) engaging on the gate, risking gate-guns and losing more ships than just warping out or 3) jumping through the gate and see what happens. I chose option 3 because I thought three battleships and a battlecruiser was too much for us to fight. While jumping the scout reported a Sacrilege and a Vigilant on D-scan at the sun. Because my brain was focussed on the bigger threat following us, I think it decided to plainly ignore that information.
Video 2
(21:25:26) Hikkoken
Osprey -9.11m
Osprey -8.64m
Gnosis +58.04m
Osprey -9.11m
Osprey -9.11m
Moa -23.75m
Moa -82.44m
Moa -32.94m
Moa -79.94m
Moa -25.22m
Moa -36.34m
Capsule -0.01m
After jumping, we still had a couple of options. The wise call would have been to warp away and keep losses at a minimum. However, at this point, I wanted some action and pew-pew. Despite the odds, I, therefore, decided to stay cloaked and see what our gate would poop out. I took most of the cloak timer to assess the situation. When I started talking, we had a Dominix, a Praxis, a Gnosis, a Machariel, a Maller and an Armageddon on the grid. The last ship was blue to me personally because past me thought that was a good idea... I edited my contacts list to prevent this for future fleets.
I prepped the fleet by calling the Gnosis primary and the Praxis secondary (because I thought the Maller and the battleships looked too tanky). Just as the timer expired, I called to anchor up and cycle the prop mods. I started burning away, which was in hindsight the wrong call. I should have put an orbit around the Gnosis at 15km. I asked the Logi to move away from the gate to prevent them from getting primaried. Only after this I realised my mistake and started to orbit the Gnosis at 10km. At this point, another Hecate warped on to the grid.
The recording shows a couple of interesting things. 1) Only a part of the fleet (mostly DD I think) anchored up properly. For the next fleet, I think this can be improved by doing an anchor check after undocking for both DD and Logi squads. 2) Logi was primaried and we lost two of our five Ospreys relatively quick. I don't know what Logi comms was like then (Logi FC, I'd love your feedback on this one!) but I would like Logi FC to be more vocal and communicate over full fleet comms (and not by whispering). 3) Broadcasts were generally in time. Big compliments to the fleet!
At the point that we had one Logi left, FC went into 10% shield. I noticed this and aligned to a random thing in my warp out tab. I called that I needed to bounce and 2IC needed to take over. I warped off with approximately 80% hull left (living on the edge ^^). Unfortunately, when the Praxis was in hull it managed to warp off (didn't we have point for this?).
2IC called the Hecate primary. Shortly after, 2IC needed to bounce and we had one or even none Logi left. 3IC decided to call scatter to prevent more losses. Not sure how low the Hecate was at this point, but 3IC did his job by calling scatter. We exchanged gfs and I gathered the fleet again at a safe to see what was left, which was a grand total of four Moas and one Osprey. Our next goal: reshipping at Ichoriya.
Video 3
(21:33:46) Nennamaila
Osprey -9.11m
Moa -36.08m
This part was ugly. Our scout reported two Hecates at the NEN gate. I will directly say that I should have rerouted to take the Hallanen -> Enaluri -> Akidagi to prevent the kills in NEN. However, my brain was stupid and lazy. I warped the fleet to the NEN gate without waiting for +1 info from our scout. While warping, 27 were reported in NEN local and gate was red. I called the capsules to make best speed to Ichoriya, which was a reasonable call because of insta-align. On-grid with our scout: two flashy, six oranges. Ships: Jackdaw, Stiletto, Harpy, Retribution, two Scalpels. All from RvB. Since we were on the gate and some of the ships were jumping, I decided to go full Leroy Jenkins and just jump into NEN. There were three on the grid (Hecate, Stiletto and the Retribution). I should have cold-warped everyone immediately but somehow decided to wait and see if they jumped.
Of course, the opposite happened and when warping off, there were fifteen frigs/destroyers on the gate. As I said, ugly and definitely could have been prevented the loss of an Osprey and a Moa. The fleet made best speed to our reshipping point and had a bio-break after this.
Video 4
(21:55:16) Akidagi
Abaddon +242.7m
When returning, we had four Ospreys, two scouts and seven Moas left. We needed a new vanguard and new points and that was fixed rather quickly. I decided to see if I could create content and bring the fleet home safely. Our scout reported five on local in AKI with a clear grid and d-scan. After a bit of hunting our scout found an Abaddon on a Large plex 27AU from the gate. Called the vanguard to jump through and warp. When the scout got point I followed with the fleet. Our scout did a great job at giving intel on both 1) the Abaddon having a Micro Jump Drive (scout lost point and Abaddon was 100km off our scout) and 2) the Abaddon warping to the Sun afterwards. Because of this, the main part of the fleet could warp directly to the sun (at different distances) and catch the Abaddon. Kudos to our Logi on keeping our Atron alive too! ^^
Video 5
(22:10:50) Oinasiken
Atron -1.03m
Atron -1.65m
Osprey -9.09m
Osprey -9.11m
Caldari Navy Hookbill +22.11m
Osprey -9.11m
Hecate +63.88m
Osprey -17.61m
Moa -34.68m
Kikimora +157.9m
Moa -21.54m
Moa -50.51m
Moa -28.43m
Moa -24.66m
Moa -24.61m
Capsule -0.01m
Capsule -0.01m
Capsule -0.01m
The fleet continued on the road back to Amygnon. Our scout reported an RvB Kikimora 14km from the Pynekastoh gate in Oinasiken. It jumped through and I let the fleet orbit the gate at 10km with hardners on and one cycle of prop-mod to attempt a catch on the Kiki. On the other side of the gate, our scout reported a Tengu at 100km from the gate. The Kiki warped away and I kept changing the fleet between approaching the gate and orbiting the gate at 10km, depending on whether there could jump ships into PYN. Our scout then reported a Scalpel and a Hecate on the gate in OIN, later to be followed by another six or seven ships from RvB. Our scout had to jump back into PYN because it lost gate cloak and reported that some of the RvB squad were following. I called to anchor up, cycle the prop-mods for two cycles, put the hardners on and asked the Logi to burn away from the gate. Our scout went back into OIN to get eyes again. Somehow, our other scout got killed by a Jackdaw in OIN, don't know exactly what happened there but eh, that happens I guess?
The scout that went back into OIN reported a Retribution and a Stiletto 10km from the gate and 8-10 flashy RvB destroyers and cruisers at 8000km (probably at a different gate or Player-Owned Structure). At this point, I wanted the next fight and see what we could get in OIN, so I slow-boated to the gate while I mentioned that we would try to get a fight and stay cloaked after jumping through. The scout then asked permission to tackle the Retribution because the gate cloak ran out. Since the fleet was close to the gate I gave permission, called the fleet to turn the prop-mod on and jump into OIN. In hindsight, I should have asked the scout the distance between the gate and the Retribution. Furthermore, I would have liked to know the fleet composition of the RvB squad which was 8000km+ off. Now, I only got that information after I jumped the fleet into OIN.
On-grid, I saw the Retribution around 80km off the gate and I called it primary. Here, instead, I should have let the scout burn back to the fleet and start the usual anchor up, hardners on, prop-mods on for x cycles and Logi burn away commands. Then, the RvB squad warped on top of us. Ships warping in; two Scalpels, one Svipul, one Kikimora, one Imperial Navy Slicer, two Harpys, one Hecate, one Jackdaw, one Caldari Navy Hookbill, one Crucifier and one Stiletto. Here, I doubted what to primary and was slow/unclear with my commands (called to uncloak and called the Kikimora as primary pretty late without a broadcast and without calling a name). The whole RvB squad jumped through with only the Retribution and a random Garmur left on the grid at 170+km. A different Kikimora decloaked (probably went from PYN into OIN?) and jumped back into OIN before we could do anything to it. Only at this point, I called to anchor up.
At this point, I could have asked someone to check local and see whether the RvB squad was jumping back into OIN. I didn't and was, therefore, caught off-guard when the RvB squad uncloaked with even greater numbers. I called a Kikimora primary for the bling, which got enough distance just before we were able to take it down *sad face*. I called a different Kiki as secondary, but that one was now at a bigger distance too. Switched to a Caldari Navy Hookbill as primary. Meanwhile, I was trying to position the fleet somewhere reasonable, keeping my eye on my own health + spinny things and watching the watchlist for our Logi's health.
We took down the CNI and I called a Hecate as primary. I noticed my distance from the gate and started to approach our unfriendly content-creators. I noticed reps coming in, but didn't know which of their ships were Logi back then (now I know I should have primaried the two Scalpels on the grid). After we took down the Hecate I called the first Kikimora as primary again. At this point, we lost our Logi and I decided that this was the point where the whole fleet dies. We tried taking down another Svipul with the five Moas which were left but had no success. 2IC and 3IC were down and FC started to get hits too, which was for me a good point to call scatter. One Moa was saved during this operation. ^^
Stats
ISK Destroyed: 544,628,943.82
ISK Lost: 599,883,718.02
ISK Delta: -55,254,774.2
Efficiency: 47.586%
Overall evaluation
- ✔ (Positive stuff)
- Fleet members thought of bringing more points before undocking
- Reships available at Ichorya were awesome sauce! This kept the fleet running so that we could get another proper fight
- FC did a better job in anchoring and broadcasting compared to earlier fleets
- Repair broadcasts were generally good, compliments to the fleet!
~~ (Neutral stuff) - Improved usage of the vanguard a bit and I asked for distances from the gate more often. Improvement is still possible, though
✘ (Learnings) - FC needs to 1) put/link scout fits in the forum announcement post's description; 2) delegate latecomers to 2IC/3IC; 3) assign a Vanguard before undocking and 4) do an anchor check after undocking, both for DD and for Logi.
- Moas have drones... Use them!
- I think more experienced Unistas might be able to explain more. Explain what our scout is doing, explain which ship is what, explain what our goal is, explain more about the ships we are using. (this includes me, too!)
- Be careful with engaging targets just before jumping through a gate because of the weapons timer. It's a recipe for losing your scout+vanguard
- I would love if Logi FC would call repairs over main fleet comms instead of whispering
- Despite having points on our Moas, a Praxis warped off... Bummer
- We could have made better use of local to see system spikes
- Scalpels are Logi and should be primaried