Hopefully Hotfix Foxtrot takes some of the ideas from this thread. We only started discussing it 7 months ago to the day.

Not getting my hopes up. Learned to not do that ages ago, but a Logi can dream...

I think you and I have a different understanding of how capacitors might work, because refilling nades is wack! I believe the capacitor would work with active and infinite equipment. Bandwidth takes care of product placement. But should broadcasting cut into capacitor energies? A little I think. Bandwidth just means we have the availability to maintain communication. Sending that signal is something else.

Active modules (future) and active equipment like the scanner, reptool, and cloak (shield bubble, miasma bubble etc, in possible future) will have an effect on the capacitor, each will take a sustained portion. Maybe even weapons or the additions to weapons in the future. While each item has its own power-source or workings it needs to connected to the suit to work. But their initial activation and possible sustained activation may drain resources.

So if there is a capacitor of 50 for a logi and a Scanner takes 20 upon activation with a recharge time of 3 per second once it is drained the scanner just wont work unti there are enough resources available. whether that be 1 scanner or 4. Meanwhile if a reptool took 15 to activate it would be a new formula to decide to scan and then rep or decide that 2 scans were needed and wait for the ability to rep.



Maybe it's a buffer with current CPU so that running a high capacitor suit meant keeping all equiped stuff at a low cpu level, meaning that to have a super scanner one could wear very little in the way of gear.




I'm not saying its perfect, I'm just saying that it stops the scan spam with a soft solution. Obviously peppering is a possibility but if it took 20 regardless it may not be worth it.

How about a new variant of hives and uplinks?

All capacitor based.

Instead of hives being infinite,how about a 'tactical' version whose refills are capacitor based?

Hives:
Throw down a hive.
Arm cloak/RE detonation prompt comes up to turn it on/off.
Press the button.
Sends out a pulses to refill allies.
Can be done until capacitor runs out,but it does refill.

Benefits:
-'infinite' refills
-Invisible to scans while not active

Drawbacks:
-lower amount deployed at a time (max 1)

Uplinks:
Throw down an uplink.
Arm cloak/RE detonation prompt comes up to turn it on/off.
Press the button.
Allows respawns.
Can be done until capacitor runs out,but it does refill.

Benefits:
-'infinite' spawns
-Invisible to scans while not active

Drawbacks:
-low spawn amount (3-5)

Then,apply Cal and Am logistics bonuses.


Presto,tactical equipment.
Without nerfing others.

Also, not surprising.
The only thing in hotfix echo that could be construed a logistics role buff (the equiment carried amount buff) even somewhat... Didn't go through? At least fully?

Proto hives carried amount still 3 (gauged 4). Adv carried amount 6.

I mean, yes, it buffs the adv hives. A lot. But still.

I view it as a nerf.

All suits can now carry a shitton of equipment. Scouts have hives and links for days. This makes the need for Logis moot. Two Scouts, 2 Assaults, a Heavy and a Logi will have more than enough equipment to last an entire match.

Logis should be the only ones that can carry enough equipment to last a whole match, imho...

Scouts have hives and links for days.

Bandwidth (Scout v Logi)
STD - 6 v 20
ADV - 9 v 28
PRO - 12 v 36

2 Points:

Bandwidth Visibilty & Nanohive WP output increase.



As of right now, players have to try to puzzle together what active equipment they can and can't have on the field pending upon which suit. You can imagine the confusion that can take place when suits maybe switched out at fast pace, one could lose track of what will be lost vs what will be sustained. Visually, having the BW capacitor in the HUD/cluster. I feel that if the player could see on each suit the actual capacity of active equipment bandwith, it could be a very valuable tool to the Logi, as well as any other suit playable. This pont has been on my mind since the patch was instated.

i.e. Proto amarr Logi having a 36 max BW would display something like 36/36 after I place 6 uplinks (4BW each), followed by one allotek nanohive (6BW each) simultaneously. This would be max capacity. Now, switching off to a min Logi (32BW); my first link would pop due to the FIFO [first in first out] laws. This would regulate back to 32/32 max, visibly descending or rising based on suit preference.

Another Idea has to do with the Cal Logi. As of right now it is still not a viable contender to call upon like its three racial peers. With the equipment buff giving a slight edge on the Cal logi, I feel that a WP buff would be sufficient from the standard +10.

Keyword "have". Doesn't mean they can all be deployed at the same time. The amount of carried equipment is equal no matter the suit. This degrades the Logistics role, imo.

This tells me scouts need more bandwidth.

Off topic for just a 'bit:
...
Reducing cooldown would very likely worsen today's problems with permascan. ...

This is the wrong place to complain about your invented "problem."

Again with the distractions... The simple truth is that there is nothing OP about the most precise scans having a small chance of picking up the stealthiest scouts. For you to suggest that scans are OP in the current system, where the most precise scans have ZERO chance of picking up the stealthiest scouts, simply is not reasonable.

Over the past couple years, I've pointed out dozens of balance issues here on the forums. I did not invent a single one of them, and pretty much every single one I've pointed out was eventually addressed and resolved. I don't waste my time making stuff up, and I don't appreciate your implication that I would.

When there's a problem my department, I do everything I can to study and fully understand the problem. Until the problem is resolved, I brainstorm with other subject matter experts to hammer out and vet various solutions. I'd like to think that Cross would do exactly same when there's a problem in his department.
7
Scans need work. Cross needs to know that scans need work. Whether or not you remain to be convinced (or intend to remain willfully ignorant of the facts) is of no consequence. Scans still need work.

Check your numbers dude, you're quoting at least one error and have repeatedly. Doesn't exactly help your cause when anyone who actually uses or does what you are describing can look at your numbers, and see the error(s).

... I don't waste my time making stuff up or "inventing problems", and I don't appreciate your implication that I would.
... Scans still need work.

Oh but you have invented a fake problem, the "permascan." I'm not implying that you're inventing problems. I'm being explicit.

The low-risk, massive-reward 21dB scans pose the bigger balance problem; they should be the priority fix.

That sentence, in a nutshell, is why you read like a troll. You're being absurd. You have an option to fit for completely avoiding 21dB scans 100% of the time. Where's my option for a CHANCE to scan the stealthiest scouts before they one-shot-kill me?

That you would complain about assault suits failing to avoid scans shows that good game balance isn't your concern; buffing stealthy play styles is.

If you don't think that permascan is real, change your battle server to Americas, queue up for an Ambush match and wait for your turn to be pubstomped by Nyain San.

That Scout has to be within 2m to one shot you. You already have your chance. Now add a Myo and hop out of his range when he enters your 8m TacNet inner ring.

20dB recon scout passive scans ..

You're nuts. In your head, you can't separate knowing where the enemy is and obliterating them. Guess what. The guys getting stomped by Nyain San, can and sometimes do scan Nyain San just as much, which is why your pointing to scans as the "problem" is entirely in your head. Or did you mean that Nyan San uses so many unscannable scouts that the people they're stomping can't see them coming, because none of their scanners can pick up the stealthiest scouts?

Contrary to your obsession with a fake problem, the real problem is that a logi can scan the enemy, see them coming, and be so ineffective when they arrive. The real problem is that EVEN WITH knowing where some the enemy is and the direction from which they're approaching, one class in particular is weaker than the others when the enemy arrives.

That's the priority fix that's needed. That's why your pretending that something as stupid as enabling assaults to duck scans is a higher priority, in this thread, is such a trollish thing to write.

[quote=el OPERATOR]

So ... there's an error in my numbers but you don't know where it is?

Not doing your homework for you is not the same as not knowing how to do your homework for you. Truth is you have a bad conclusion because it's based on bad data. Pointing out that you have bad data is all I need to say. If you aren't capable of vetting your own info, that you choose to present, that you choose to use to justify your conclusion and try spreading anywhere you can find an ear for it while it's bad isn't my problem, it's yours. My problem is that for a guy who claims to be such an infallible resource of all things broken your conclusions are crap, because your data is crap and you're too invested in the convincing of people of the legitimacy of your [bad]conclusion to realize it.

Confirmed: You are a yahoo.


/your steamies you keep trying to float in this thread

Says the guy who didn't know until last week that 21dB scans existed.
Would you like me to find the post?

You'll have to pardon me for not taking you at your word on this.

What you have there is me being polite. You spent two weeks debating and defending GalLogi scan precision without knowing the precision of GalLogi scans. Or caring enough to even look it up.

"Oh. So the 200m / 90 degree scanner is 21dB. Hmm. This whole time, I was defending the Focused scanner ... the one with the narrow angle and huge cooldown; it couldn't possibly permascan anything, so I thought you were making stuff up. My bad. "

Would've been nice to get something like this from you. But instead, I get a 1.7-Spkr-like "everything is still fine ... go away ". And now you want to call me out on non-specific "bad data" ...