Assembly Hall

Recent events about UI restructuring got me thinking about a feature left forgotten by many, and usually used very scarcely:







Possible additions:

• Better sorting: sort by type, subject, amount.


• Better filtering: Filter incoming damage, Reverse filters (everything but one type), Filter by ship type or weapon system.


• Statistical data: DPS, volley damage, hit/miss ratio, success rate for ECM and other modules.


• Separate logs in one window: ....yes spreadsheets...


• Graphical form: Pie charts, Bars...Eye candy for new people to look at and pretend we aren't spreadsheet online.


• More sophisticated log save-file: to be used by 3rd party tools to recreate the engagement for extensive AR


• Fleet command capabilities
1. Access to multiple ship stats for squad, wing, and fleet commanders: each having access to more ships, highest ranking commander defines access rights for lower commanders. Basic stats: DPS, incoming DPS, ECM usage to see the activity level of each pilot.
2. Grantable access: new fleet position - statistician


• Other options

Reasons and benefits:


- Easily accessible data for new players: Doesnt have enough DPS -> checks logs -> large glaring pie chart telling him he is missing 95% of the time -> more specialized search -> easier to obtain answer.

- Data accessibility: Graphs online is much better than spreadsheets online for new players ,

- Data acquisition and processing speed: easier to read the graph in the heat of the moment, than a column of numbers

- Less ambiguity: No need to rely on eyeballing and EFT-warfare - optimization using in-game situations.

- Future implementations bigger plethora of scripts and script like modifications to optimize the ship on the go for each case using advanced data of the log.

- Faster experience growth: with logs it would be easier to see your mistakes: new players will learn faster.

- Posibility of faster ship turnout: smarter pilots + optimized fights = more fights, better fights, memorable fights.

- Audience appeal Many of us like numbers: Math geeks, min-maxers, munchkins admit it you will love to see you numbers rise and a visual representation of that in eve adequate form and not flowing numbers.

- More data for FC same as average player but a level higher: know what your fleet does and what it does not and why, know your mistakes, learn form your mistakes, and more importantly adapt to changing conditions faster,

- Less stress for the FC having pilots aware of their blunders, grantable fleet statistician role reduce necessary data for fleet commander to process in the middle of a fight.

- Optional: you want it - you turn it on.




Possible side effects to consider:

Too much information accessible to FC?

Another learning curve to understand controls: need to have new player-friendly default preset.

Precious CCP man-hours.

N.B.: The suggestions are optional malleable and configurable. This is not final form but more of a suggestion what can be added. Please concentrate on the overall usefulness of such overhaul than on the possible additions introduced by me.



Additional ideas and suggestions to enhance curent ones are greatly appreciated.

I think they would cover rather separate fields: combat log would be more important for separate engagements, while war-dec will poll entire data for the war. But the war-dec scoreboard can benefit greatly from the statistical data obtained from the improved combat log.

For example during or after the engagement the combat log does a background check and if the target was from warring corporation or alliance - sends additional data to the scoreboard.

This addition can be retroactive too so CCP finishes war-dec first then combat log comes after and adds additional info to the scoreboard.


Another benefit i could see - more information present for AR: depending on how it is implemented, perhaps preemptively selected before the large battle or interesting encounter that would allow saving additional data to separate file so pilots can access it later and effective;y reconstruct the engagements from that file alone using 3rd party tools.


This might cause additional strain for weaker computers (dont think that it should be calculated on a server) so optionality must be present.