![]() Here is a snippet of the Terms of Service which almost seems to contradict itself. They claim user-content is ours but they also claim we cannot really access it unless we use it like they do. that data is an aggregation of our experiences, triumphs, defeats, and more. Whether it be you, me, or anyone else who wants to write the most basic of scripts. You all deserve to access the data just as we deserve to see post-match stats in-game. They chose the views.Ī fuckin horrid site built in flash with an animated background and animated frames that make slow computers appear choppy and mobile browsers shit a brick. but there is no way to ask for a dataset containing K/D on a particular map, playlist, gametype, and weapon. Sure 343i found particular aggregates (like K/D per map) that are useful stats. ( example of basic xml query without OAuth) Is a fake live account using OAuth to create a login-based query which is just a re-engineered waypoint-site query. Point is I know you all at HaloTracker can share that love for data. I had breakdowns and improved queries (I only did extreme specifics to my gamertag) for gamertag lookup.Īnother example of specifics in an overview format: I could view a list of everyone played against on a particular playlist from 14:02 to 15:38 (example) in a chart layout with stats such as K/D over time or aggregate (group by aggregations on tabular gui), and much much more Line charts generated my linux module gnuplot indicating changes over time specific to the playerĪnd that is just the player-player portion of my database (built from individual match data. Most common teammates of player (descending list) Other characteristics of player relative to meġ. Killed By / Assisted in Getting Killed By / Killed / Assisted in Killing One snippet of my own database I made back in Reach: I could query another player's gamertag (on my own metrics) and getġ. Sidenote: why I personally loved the API from Bungie Many players do not realize how important this is. You should have the equivalent of a stateless restful service with usage access for particular datasets akin to Google apis query limits if we can somehow justify a stateful connection in the first place. It is complete bullshit that you do not have an API. We want to see Halo succeed as much as 343 does, and we know our contributions make up for a small part of that success. Bungie did it back in the Halo 3/Reach days, and it worked marvellously for the community. If you'd like to see these communities continue to serve you in the future, please help us by letting 343 know that you want this data open to the public. We cannot expect 343 to really provide the in-depth player profiles that you can find on alternative sites like HaloTracker, because that isn't their primary concern. This is not ideal, because not everyone comes to see the same level of stats analysis. As of right now, the only reason we can see for 343 not providing this information is so that they can keep their stats locked down and force people to use their own solutions. If you would like to see the continuation of 3rd party communities like and HaloTracker, it's essential that we let 343 know that we want this information to be publicly accessible. This is because 343 has gone out of their way to make accessing this information extremely difficult. ![]() This data allows websites like HaloTracker (featured many times here on Halo Waypoint) and others to keep track of your personal scores both in campaign and in multiplayer inside the Halo universe.Īs of right now we are unable to access much of the information that's required in order to provide the community with these in-depth stats and player profiles. Usually the sites have been able to grab the stats relatively easily without much contention from the developer (first Bungie then 343) in order to provide more in-depth player analysis that the community seems to love so much. With the impending release of Halo: MCC, Halo communities have been scrambling to get access to data feeds for the latest Halo release. In threads with a vague title and Rumor/Leak/Datamine flair detailed outline on acceptable titles.Lore may be freely discussed three months past release. New official lore and datamined/leaked game content are spoilers. ✅【DROPS】Live from SSG Invitational! - Spoiler Policy SLC WATCH PARTY!!! BIRTHDAY UNCAPPED SUB. Ģ4 HOUR STREAM !DROPS ~ HCS SLC Day 3 Wa. R/Halo Discord + LFG | Infinite Season 4 | 343 Plz | Game FAQs ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |