BuzzerBeater Forums

BBAPI Support > Future Features

Future Features

Set priority
Show messages by
From: modred

This Post:
00
96104.9 in reply to 96104.8
Date: 6/11/2009 11:01:27 AM
Myopic Marauders
III.8
Overall Posts Rated:
2424
well, then getting the "match string" in raw form for people to parse?


That would be a great addition.

From: wozzvt

This Post:
00
96104.10 in reply to 96104.9
Date: 6/11/2009 11:40:53 AM
Overall Posts Rated:
228228
If you do a little digging you can get this in bits and pieces (not through the bbapi though), but parsing it is a tall task without any documentation.

From: elboss

This Post:
00
96104.11 in reply to 96104.10
Date: 6/11/2009 11:59:40 AM
Overall Posts Rated:
00
If you could get the whole thing with the API it'd be relatively easy. correlate that with the match report, do that for say 20 matches and you should get the key...

Or perhaps I'm too optimistic. But hell, I cracked things that were way less open than that :)

/elboss

This Post:
00
96104.13 in reply to 96104.10
Date: 6/11/2009 12:52:32 PM
Overall Posts Rated:
3737
If you do a little digging you can get this in bits and pieces (not through the bbapi though), but parsing it is a tall task without any documentation.


Hooray for Wireshark (or whatever else)... I didn't have any idea where to start in reverse-engineering that.

This Post:
00
96104.14 in reply to 96104.12
Date: 6/11/2009 2:21:21 PM
Overall Posts Rated:
00
Note that to get substitution informations, you don't need to understand all commentaries, just the part about remplacement. I think a regexp could easily get that.