https://flsr.engi.io/loadouts Source of inspiration
Ability to select ship and ID
make through Htmx and request/response interaction.
Web go routine server on top of the rest of darkstat data that reuses its all other data.
do not make separate web port
make separate cli group for faster debug
permit being initialized on web with extra flag
1st section with hardpoints same
2nd section with stats, make top section with gun parameters for:
potentially make two columns out of it (left with values Avg/Sums, the right one with row names)
DPS
range
speed of projectile
burst DPS
damage
and etc
after you finish with gun params, you can do the rest of ship stats below. (make fonts smaller to fit all)
Potentially bottoms of both second and third section can be given to other ship stats. ( <==== i am not sure i like this choice)
Or if not, then make 4th section of gun selection actually wide and going into third section. ( <==== i like this choice more)
third section that is currently empty for Gun columns and showing per each gun stats.
its row names will be coming from right column of 2nd section
second section will be keeping summarized data and column raw names
4th section top about infocard keep the same
4th section bottom keep the same or expand into fully fledged darkstat tables of data
column names in 3rd section will have names gun Analystics: Revisioning server side cfgs #1 , gun Feature: Ship comparison #2 and etc.
on hover they will highlight weapon slot
weapon slot on hover will highlight gun column with its stats
beyond mvp
control groups to summarize stats?
somehow highlighting proj speed mismatches?
Ship visible where hardpoints are?
We could use Coloring scheme/visible hover info to distinguish if gun on top or at the bottom of a two dimensional pic of ship
https://flsr.engi.io/loadouts Source of inspiration
webwith extra flagbeyond mvp