-
Notifications
You must be signed in to change notification settings - Fork 30
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
Report more info to DSCM-Net #105
Comments
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. |
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. |
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. |
Report more info about ourselves, so the connection decisions can be made smarter.
The text was updated successfully, but these errors were encountered: