• Content count

  • Joined

  • Last visited

  • Days Won


Skeltek last won the day on January 10

Skeltek had the most liked content!

Community Reputation

6 Neutral

About Skeltek

  • Rank
    Advanced Member
  1. Returning to Eve and Incursions

    Hi wanderingbort and welcome back. I think what you want to fly is personal preference. We often start out with an abundance of Logi which declines over time and end up with people having to switch to Logi to maintain minimum safety numbers. You of course also just decide to bring both ships, but currently we have an island spawn and I assume you know that means it is too dangerous to travel there. Besides, nearly nobody moved so far.
  2. Old logi pilot wondering what’s up with the Basi?

    You're welcome. Though I may be wrong though. Someone on Command Core just told me Marauders did not have double fire rate before the timer got lowered to 30 seconds, but they always had only 4 guns. So according to him, the reason for not using Marauders was they used to deal significantly less damage than a regular battleship. That is not how I personally remember it, but I don't want to lean too far out the window, since I only restarted playing EVE like 2 years ago after a break of nearly a decade.
  3. Old logi pilot wondering what’s up with the Basi?

    If CCP didn't temporarily lower bastion duration to 30 seconds, people would still be reluctant and protest of using them in Incursion. Only the duration reduction probably made it ollerable to actually try, but now they still keep them, despite the duration having been increased back to 60 seconds. But it's like that... if the gap of change is too big, people will outright refuse to change their conduct, no matter what you do. Kind of funny they did not revert to Vindicators when CCP turned the duration back to 60 seconds ^^ But luckily there are ways to compensate, should CCP ever decide to increase the timer to 2 minutes
  4. Old logi pilot wondering what’s up with the Basi?

    Hello T'vaar mostly what Hamxus said. Though I can just presume the sane choice back then would had been 3/3 Basis to double cap while only sacrificing 1/4 shield rep. Having 10 locks on Basi is sufficient imho and lock speed on BS is really fast anyway like 2 seconds I think. I essentially did nearly the same fitting WTM is using shortly after Logis were indroduced to game to make it autonomous and less susceptible to failure. It was nice to see to find same setup here when I joined. And welcome back.
  5. Serving cap broadcast, a better method?

    Thanks for your answer. Yeah, I know those techniques, also work well when not alone and Vindicator pilots not changing all the time. And admittedly, over the past few days I did not experience such fleets. Even boosting as the only Basi is kind of extremely relaxed (almost easy/boring to the point of getting sleepy). I probably just unluckily had the false impression about such fleets being moe common/regular with constantly switching members.
  6. Serving cap broadcast, a better method?

    Yeah, it's usually just 3 or 4 people needing frequent help, and a few just broadcasting on occasions. And admittedly, such regular fleets are not really problematic and rather get boring to cap-support. What I'm talking about is those '16-18 Vindicator + 4 Nightmare + 3 Hyperion' fleets I recently experienced, where having 4-5 Basilisks doesn't really help against the upcoming simultaneous broadcasts of 12-14 people. Even though I was proactively cycling through the most demanding guys, the buildup of cap deficit seemed inevitable. Not really that stressfull, just feels like investing much more work than needed, which could be used elsewhere like spotting DCed members. Yeah I agree, had that just yesterday for like nearly an hour, felt nice. Maybe I just experienced a really bad day or something, which may be a rarer occurence than I currently think. Having more than a dozen people screaming for cap simultaneously just made me think. Especially after someone already received 4-5 cycles and immediately broadcasts for cap again 10 seconds later.
  7. Serving cap broadcast, a better method?

    I understand the reasoning behind it. That's why I suggested only utilizing them only if the FC explicitly asks for it and limit it to just one. Yeah, I also donated a few times. They're not always there though. And if their occasional presence was sufficient, there wouldn't be cases where people turn off guns to save cap, several members having to wait half a minute for cap or people getting skipped or forgotten. Too often I see people broadcasting for cap multiple times, even though they were already received several cycles of cap... Yes, that's an ideal long-term solution. It is inconvenient though, if WTM keeps getting new untrained additions (which is good in it's own way) and the rare cases where 10-15 people broadcast for cap at the same time during a split-aggro to split-aggro transition are making problems. It is rare for a Basi pilot not being able to keep up, especially with slow fleets. I am unsure though, if the 'ideal' would help against a differing reality (not meant negatively, it's just how I perceived it until now). But with fast fleets and a lot of cap hungry ships, a 'giving a recommendation for futher training' doesn't help immediately alleviating the issue at hand during a contest or whatever. In the end just a few turned off guns per Vindicator could easily decide on winning or loosing a contest. You are much more experienced with leading Fleets, so you are probably right. But I wanted to give some feedback here, since I often noticed a massive surplus of Scimitars, while the whole Fleet had to wait for a Basi replacement or had to tell a well experienced DPS to change ships to a Basi. Also the need would be eliminated, to have a minimum of 2 Basilisks, while there's an oversufficiently large amount of Scimitars at hand, which could take over the logistics part of remote repair. Please don't consider my feedback as coming from someone who believes 'to know it better'. What you make of my input is up to you guys, I'm just trying to help.
  8. Serving cap broadcast, a better method?

    Greetings, I'm rather new with maybe 3 weeks into Incursions after an 8 year break from Eve, but I'd like to share my experiences here. I noticed the amount of cap broadcasts often not decreasing with the addition of more Basi pilots to a fleet. While I'm constantly locking Vindicators, Hyperions and occasionally Nightmares and Tempests (depending on Site the composition varies) and give them 3 cycles with a single cap projector, there are usually only a few broadcasts left every now and then, even while contesting. In the end it all depends on the number of Vindicators; if you can lock up 7-9 of them (keeping the required locks ready for current shield broadcasts) and remember who else you are not spraying cap to, then you can easily give cap to everyone not locked on the next lock-cycle, so no broadcast is ever seen. Yesterday I was the sole Basi in fleet for a pretty long time and we had just 2 cap broadcasts during a contest. In the Logistics channel some were confused about the DPS maybe not overheating or something. But this of course was not possible because of personal skill, but only because the amount of Vindicators being 'just' 9, making memorizing who already got proactive Cap in the TPPHs easier. It also helped a lot by not cluttering up the broadcast history and making it confusingly cramped. An hour later we had 3-4 Basis and the chat was cramped with many people repeatedly broadcasting for cap - even with several people repeatedly complaining on voicecomms about their cap being dry. Though I noticed some Basi pilots only serving the broadcasts, some (at least one of them) of them were not transfering cap at all. Shield broadcasts were another problem during split-aggro, since many people don't broadcast 'in position' and it ended up with 6 of my locks being occupied by shield broadcasts, while the aggro partially switched on multiple new persons. Not knowing whom to unlock, makes the unlocking rather speculative, so I had to 'guess' which target was not receiving damage any more in order to make room for new shield locks... the cap broadcasts of the 14-16 Vindicators, 5 Nightmares, 4 Hyperions and 1 Tempest had to be completely ignored in favor of fleet safety. At some point, the amount of cap projectors just isn't enough to keep the broadcast history 'clean'. And even if people broadcast 'in position' when having received enough cap, can make the broadcast history comparison with the locks quiet complicated. I usually don't have problems doing the Basi job, but sometimes at peaks (and if the other Basis are not distributing cap pro-actively), it can be difficult to browse through the history to determine what to unlock. Unlocking is easier for people in the watchlist, since you can see who's under attack and relock rather fast, but I usually have all Logis in it, the DDDs, the FC, the meatshield, and it quickly adds up to being nearly maxed out. My recommendation would be to have a single cap-dedicated Basi in each fleet (in addition to the usualy Scimi-Loki-Basi-Mix), capable to equip and run 6 cap transfer arrays and lock 10-13 targets. That way the bulk of the Vindicators could be easily served with a massice amount of proactively distributed cap, and it would make the job of the other Basi pilots to only battlecap the 'problem children' much easier and less stressfull. As I see it, flying Basi is rather stressing for a lot of people, and some surely stop proactive capping every once in a while because they get half a burnout - it's probably not sursprising most people prefer flying Scimmitars or Lokis, since properly flying Basi comes with such a workload, you don't even have time to actively watch out for people out of position or possible DCs. WTM is a shield-based fleet with a probably high amount of Caldari pilots... why our fleets keep having a Basilisk shortage is a thing to think about. Having a single dedicated Cap-Basi in fleet would make life easier for all the other Basi and Logi pilots as well, freing up broadcast history, making the job much less stressfull for the one proactively capping and freeing up resources and locks(!) for emergencies. And cap projectors having much smaller powergrid and CPU needs than shield transfer arrays would allow anyone to fly them even without a Powergrid rig. I made two screenshots where I realized it would be possible to keep the whole fleet from constantly broadcasting for cap. The only problem an hour later on was the massive amount of Vindicators and the lack of cap projectors. Also switching targets for proactive battlecapping takes time off of each modules activity time, which could be futher reduced by assigning a single projector to 6 targets each longer. For me proactive battlecapping makes up 75-80% of my workload... I can understand, if many Basi pilots don't proactively distribute cap, since it is a large amount of extra work. I can also imagine the workload on FCs and searching for new Basi pilots being lower, since a less stressed Basi/Logi pilot would probably be willing to stay in fleet longer, requiring less frequent substitution. for the time being though, I would recommend to allow such a Basi in fleet only (!) if the FC explicitly requests for one (and of course the Cap-Basi having to leave fleet eventually or re-equip to standard fitting if a new FC doesn't want it). So far, it is just an idea/recommendation. I wanted to see what other Logi pilots and FCs think about it as a possibly viable option to reduce the massive overhead and stress for proactive battlecapping. kindly regards, Skeltek