Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposal for drop_ship record expansion #51

Open
Nishisonic opened this issue Dec 16, 2019 · 5 comments
Open

Proposal for drop_ship record expansion #51

Nishisonic opened this issue Dec 16, 2019 · 5 comments

Comments

@Nishisonic
Copy link

According to the current specifications, you can see how many ships you drop, but you don't know the probability.
So I suggest that you can get all the ship daughter possession like TsunDB.

Example:
counts:{ shipID: count, ... }

counts:{"1":1,"2":1,"6":1,"7":1,"9":1,"10":1,"12":1,"13":1,"15":1,"16":1,"17":1,"18":1,"20":1,"21":1,"22":1,"23":1,"24":1,"25":1,"26":1,"27":1,"28":1,"29":1,"30":1,"31":1,"32":1,"33":1,"34":1,"35":1,"36":1,"37":1,"38":1,"39":1,"40":1,"41":1,"42":1,"43":1,"44":2,"45":1,"46":1,"47":1,"48":1,"49":1,"50":1,"51":1,"52":1,"53":1,"54":1,"55":1,"56":1,"59":1,"60":1,"61":1,"62":1,"63":1,"64":1,"65":1,"66":1,"67":1,"68":1,"69":1,"70":1,"71":1,"72":1,"74":1,"75":1,"76":1,"77":1,"78":1,"79":1,"80":1,"81":1,"83":1,"84":1,"85":1,"86":1,"87":1,"89":1,"90":1,"91":1,"92":1,"93":1,"95":1,"96":1,"97":1,"98":1,"99":1,"100":1,"101":1,"102":1,"103":3,"110":1,"111":1,"113":1,"114":1,"115":1,"116":1,"120":1,"122":1,"123":1,"124":1,"125":1,"126":1,"127":1,"128":1,"131":1,"132":1,"133":1,"134":1,"135":1,"137":1,"138":1,"139":1,"140":1,"143":1,"153":1,"154":1,"155":1,"161":1,"162":1,"164":1,"165":1,"167":1,"168":1,"169":1,"170":1,"171":1,"174":1,"175":1,"176":1,"181":1,"182":1,"183":1,"184":1,"186":1,"190":1,"191":1,"331":1,"404":1,"405":1,"409":1,"410":1,"413":1,"414":1,"415":1,"421":1,"422":1,"423":1,"424":1,"425":1,"431":1,"432":1,"433":1,"439":1,"440":1,"441":1,"442":1,"443":1,"444":1,"445":1,"448":1,"449":1,"451":2,"452":1,"453":1,"454":1,"455":1,"457":1,"458":1,"459":1,"460":1,"465":1,"471":1,"473":1,"474":1,"475":1,"479":1,"481":1,"484":1,"485":1,"491":1,"492":1,"493":1,"495":1,"511":1,"515":1,"519":1,"520":1,"521":1,"527":1,"528":1,"531":1,"532":1,"534":1,"535":1,"544":1,"549":1,"561":1,"562":1,"571":1,"574":1,"575":1,"581":1,"583":1,"589":1,"590":1,"596":1,"601":1,"613":1,"621":1,"625":1}

@gakada
Copy link
Contributor

gakada commented Dec 16, 2019

This was touched before in #36 (comment).

@KagamiChan think this still stands?

@gakada
Copy link
Contributor

gakada commented Dec 16, 2019

Maybe reporter plugin can have an option (as a checkbox, maybe also disabled by default) to report extra info like full owned ship lists for drops, so there is an explicit user consent.

@KochiyaOcean
Copy link
Member

I can understand necessary of these data, but it will significantly increase db size (more disk space usage & more traffic). Maybe we should expand our server first 🤔

@gakada
Copy link
Contributor

gakada commented Dec 16, 2019

Something like #44 also requires quite a lot of extra space/traffic (at least for routing/sortie collection), as large as drops right now.

@Nishisonic
Copy link
Author

I saw the master branch and didn't notice it because it didn't look like it was prepared.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants