Wulf2k / DaS-PC-MPChan

77 stars 30 forks source link

Report more info to DSCM-Net #105

Open Chronial opened 8 years ago

Chronial commented 8 years ago

Report more info about ourselves, so the connection decisions can be made smarter.

Wulf2k commented 8 years ago

Even if we don't know the specific event flags yet, we should probably work out a format for this data.

I imagine the most efficient method would be to mimic the way they store event flags in game, in a bit array. (I honestly have no idea if anybody else calls it that.)

eg, 8 = boss 1 dead. 4 = boss 2 dead. C = boss 1 and 2 are dead.

So we'd end up with xxxxxxxx xxxxxxxx to tack onto the end of the report. We should probably figure out how many xxxxxxxx we need to track everything we might possibly care about in the future, with some free bits around the edges to add whatever we inevitably forget to care about.

Chronial commented 8 years ago

The report has a completely different format now – It's just json. But yes, putting the boss flags in a bitfield would probably make sense.

CatboyPrincess commented 8 years ago

I happen to have a p decent CE table if you need some addresses.

Also, aside, how is the data reported to the server? Is it an ordered set? I was thinking that an associative array would be best to make it easy to push the data. E.g. use associative arrays in JSON format and send that to the server. It would be easy to parse, easy to form the data, and easy to accommodate future required values.

Chronial commented 8 years ago

I happen to have a p decent CE table if you need some addresses.

I probably have the same table, so that is covered. Somebody just needs to add this to the code :).

E.g. use associative arrays in JSON format and send that to the server.

Way ahead of ya ;).