Community Members
  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral


  • Rank
  1. Serving cap broadcast, a better method?

    I'll absolutely not step on anyone's toes and try to to impose any new or confusing methods outside of doctrine. But I think institutional momentum shouldn't be the strongest argument against potentially positive changes. I'm not great at explaining things, but it honestly is not difficult to manage cap broadcasts the way everyone did in TVP years ago.
  2. Serving cap broadcast, a better method?

    I totally agree with all of this! But is that method of giving 2-3 cycles and then coming back around actually written down anywhere in doctrine? That's basically what the OP is proposing.
  3. Serving cap broadcast, a better method?

    These strategies aren't mutually exclusive and can both be done. You should always be using your cap transfer to hit the frequent broadcasters and hungry newbies. This should be done when there aren't any actual broadcasts. This isn't where the OP is looking to improve efficiency. My specific gripe is with an individual basi claiming a single broadcast and performing it alone. I think this can be done better by each basi servicing each request. If you want to talk to a newbie and explain about implants or pulsing the MWD, that will help too.
  4. Serving cap broadcast, a better method?

    I agree that there are similarities, but they also have important differences that wouldn't be negligible. I'm a huge proponent of preemptive capping to reduce future broadcasts. That should always be done when you're not receiving broadcasts but that isn't where I think we have room for improvement. Lets break the time a logi spends into 3 sections. No broadcasts, Sparse broadcasts, and TONS of broadcasts. (ignoring Outunis for simplification) No Broadcasts: Proactively cap the hungry Vindis or newbros (coordinate with the other basi so you're not hitting the same people) Sparse Broadcasts: Each basi provides 3 cycles to each broadcast and then moves on. I don't think it helps to call out the name of each broadcast in chat when we're only getting 1 at a time. Here's what i've experienced. I have to leave my focus on the field and take my hand off the mouse in order to type a message. When i'm typing, i can't lock up new broadcasts or activate modules. In my opinion, the amount of times I need to move to the keyboard should be reduced to a minimum so that I can spend more time doing my job. I don't see any reason why we need to communicate when it's obvious what to do when we receive a single broadcast. If everyone gives 3 cycles, then all the basi's are free and the BC is complete in 3 cycles instead of tying up a single basi for much longer. This also keeps the chat clear so that other important messages can be read. Obviously you should be checking the chat every couple of seconds, but if we keep unnecessary chat out, we'll be able to notice important messages faster and they'll stay on screen longer. TONS of Broadcasts: I want to reduce the time it takes from broadcast until first cap served. When we get 8 broadcasts at once (with 4 basis), we could type in chat who we're starting with so that half of the broadcasts get cap immediately, then claim another unhandled request after 3 cycles and inform the basis in chat. Then we continue to handle the backlog in any order so that each request always receives 3 cycles from each basi. Each basi doesn't need to get every broadcast to full capacitor before moving on because the first 25% cap is vastly more important than the last 25% and the rest of the basis will catch up to them over 15 seconds. If each Basi stays with their first assigned broadcast until full, the 4 newest broadcasts don't get anything while the oldest broadcasts are getting up to 75% which they don't need right away. This means half of them aren't firing, can't get in position, or might not even have hardeners on. I think the vindis would much prefer getting even 3 cycles of cap quickly than a full capacitor 30 seconds after broadcasting. It would be much less frustrating if you could rely on getting the cap within 10 seconds at most rather than 30 seconds in the worst case.
  5. Serving cap broadcast, a better method?

    The difference between 0% cap and something is the ability to shoot. We need to keep hardeners on and guns shooting as quickly as possible. This would have much more consistent response times instead of waiting 30 seconds or getting missed entirely when it's busy.
  6. Serving cap broadcast, a better method?

    You don't have to do every request in order, as long as everyone is getting something right away. In this example, you get 5 requests at once with 4 basi: You each call the name of the person you're getting, when you finish your first person, someone calls the name of the 5th request in basi-chat and gives him 3 cycles before moving on and covering the previous requests (which have all been serviced with at least 3 cycles already). The most recent requests have priority to get at least a little cap before you finish your backlog which should have gotten some already. That way, you can get a little cap right away and then you'll receive the rest in a moment as the basis finish up getting the most recent requests their cap first. The highest priority is obviously situational, but if we have 8 vindis all wanting cap at once, we'll get all 8 of them their first cap within 4 cycles instead of like 30 seconds.
  7. Serving cap broadcast, a better method?

    He's suggesting that each basi gives 3 cycles to each broadcast. You'd get 3 from EACH basilisk. This wouldn't be chaos at all. This is what has been done for years with TVP. Using this system, if you received a wall of broadcasts, you would then call out the name of the pilot you were starting with, but you'd still move on and hit everyone. If there's 4 basis and you get 4 broadcasts at the same time, each broadcast starts getting cap immediately (like the current WTM system). The benefit of giving 3 cycles is that you can start new requests faster if you get loaded with 7-10 at a time. It also make all the constant coordination of single broadcasts unnecessary. Putting names in basi-chat for 1-2 broadcasts at a time wouldn't be necessary because everyone just knows that they are each responsible for giving their cap to each request. With the current WTM system, if you get 5 broadcasts and you have 4 basi, the 5th guy waits for 8 cycles before receiving anything. I think it's important to get your first 3 transfer cycles quickly because they can get your capacitor back into peak recharge without having your guns off for 30 seconds.