Was discussed at a round table at fanfest, would be an incredible load on the server. Only some ships in a fight are taking damage or reps or ewar at a time. ALL ships will be using capacitor with ALL their active modules. Transferring this data to ALL the clients would be quite a drain.

Only 'hidden' info is enemy (and friendly) capacitor. Yeah, you can cargo scan to take snapshots and it's fairly evident when someone is completely out of cap. Twisted

Because that would be stupid.
I'm quite sure you're smart enough to think of a good reason why that shouldn't be released yourself.

Thanks. I'm not a game developer so I'll have to take the dev's word on it.

It does sound a bit fishy though, all clients are already getting position and velocity vector info on every object on-grid, and shield/armor/hull info on anything targeted.

Maybe trade info about who is warp scrambling whom (which doesn't seem worthwhile to relay to all people on grid imo) for cap info?


EDIT: actually each client also gets info on all effects and interactions, otherwise it couldn't graphically render them, right? And in any battle, every ship is either shooting, repping or applying ewar (or two, or even all three), unless they're out of range. So yeah, the server load excuse seems quite fishy, actually!

Thanks. I'm not a game developer so I'll have to take the dev's word on it.

It does sound a bit fishy though, all clients are already getting position and velocity vector info on every object on-grid, and shield/armor/hull info on anything targeted.

Maybe trade info about who is warp scrambling whom (which doesn't seem worthwhile to relay to all people on grid imo) for cap info?


EDIT: actually each client also gets info on all effects and interactions, otherwise it couldn't graphically render them, right? And in any battle, every ship is either shooting, repping or applying ewar (or two, or even all three), unless they're out of range. So yeah, the server load excuse seems quite fishy, actually!

There are plenty of reasons to supply less info to players in combat, many of which I would support if push came to shove.

However, to request a cap readout on a target THAT YOU ARE CURRENTLY PERFORMING CAP WARFARE ON is not a totally unreasonable request. The same could be said for those that you are currently cap boosting as well.

Thank you for typing in large letters to help my eyes. Fortunately they work just fine, so spamming caps lock is not necessary.

A low performance hit way of doing his would be to have the targets current cap print in the log whenever activating a neut or nos on that target.

Someday a mod will be used to read cap levels on a ship. If you can scan cargo, you can scan cap energy levels.

Just give it time.

Yeah, you can cargo scan to take snapshots

It's called emphasis on the key point, which you have apparently missed anyway.

I also was not addressing the remark to you, but thank you for assuming I give a damn who you are or what your opinion is (mistaken though you may be in that regard).

Think of it this way. In a 1000 person fight, if 1 person is shot by 1 other person, that information is relayed 1000 times. If 1000 ships move, the new positions are relayed 1000 times each for 1 million calls. Velocity, angular velocity, and transversal velocity can all be calculated client side from the old and new positions. This means that in combat, module activations, absolute position, absolute position of drones, effects of drones (damage/ewar), and damage taken for targeted ships are the only things (that I can think of) that have to be relayed to participants.

if we assume weapons are grouped, for combat ships, there will usually be 1 weapon activation every 3+ seconds, and longer on prop mod, scrams, webs and other modules. My estimate is 1-2 module activations per second per ship on average. Add in 5 fields updated for drone positions, and some amount of damage taken, and we're looking at 20 or so data points per ship being broadcast, capacitor would be another point that would have to be updated every server tick, so it probably represents a 2-3% increase in server load (I'm assuming my 20 data points estimate is lower than reality). This would be significantly more manageable if only visible on locked targets, but its still another value that has to be updated every server tick.

Notice that when you target someone your client assumes they are at 100%, and it takes approximately 1 second (server tick) for the readout to update with their actual status.

Just because I didn't specifically comment on your point doesn't mean I missed it. In fact my suggestion about outputting that data to notifications/logs instead of having a real time readout was specifically based on your comment. Is this the part where I pretend to be offended by you? [shocked]You heartless fiend![/shocked]

Not sure if you're trying to troll, but:


...it's already a feature of cargo scanners.

I was wondering if it were possible and/or desirable to have real-time info on all active targets, without a mod.

And here I thought the OP was gonna ask for something sensible, like maybe a way to show a percentage readout for there own cap instead of the cap dial. Nope, couldn't be that sensible.

In combat, we have instant info on everybody's position, speed, relative speed, etc.

We also have instant info on EWAR and cap warfare effects applied to us and who is applying them.

If you have the time to look and are familiar with the animations, you have instant info on self-buffs and remotely applied buffs/debuffs and who is applying them to whom. Including who is shooting whom.

If you target somebody, you have instant info on his shield/armor/hull hp.

Etc, etc, lots of useful combat info that the quick & savvy PVPer can have fun with.


Only 'hidden' info is enemy (and friendly) capacitor. Yeah, you can cargo scan to take snapshots and it's fairly evident when someone is completely out of cap.

But still, why no real-time readout on targeted ships' capacitor (both friendly and enemy)?

While your at it, demand instant info on what each pilot is wearing during the fight, their relative location to you in the world, their favorite color and their marital status.

I guess you're not aware that 'show pilot info' already reveals your toon's skimpy top and low-rise trowsers, if you're atk I can roughly guess your longitude and every PVPers favorite color is either yellow, orange or red. Marital status is irrelevant, it's a game not a dating site.

Sarcasm is lost on you I see.