Did something change with Matches for Player?

OK, this might be a dumb question, but is anyone else seeing odd results when returning games for players?

I was running my application, which uses HaloSharp, and I noticed that I was getting 50 games back every time, instead of 25. I didn’t change anything in my code. I have it set to run the following:

> new GetMatches().InGameModes(gameModes).ForPlayer(member.Gamertag).Skip(0).Take(25)

with gameModes as a List<Enumeration.GameMode> including both Arena and Warzone. In the past, I would always end up with results numbering 25. Like I said, it went up to 50 today.

So I went to the documentation section of the API, but it still lists 25 as the limit for Matches for Player. However, when I run it there, I am getting odd results. I don’t know if I just never noticed before or if it actually changed. Here are some examples:

> Asking for 2: “Start”: 0, “Count”: 2, “ResultCount”: 8
> Asking for 5: “Start”: 0, “Count”: 5, “ResultCount”: 20
> Asking for 10: “Start”: 0, “Count”: 10, “ResultCount”: 40
> Asking for 15: “Start”: 0, “Count”: 15, “ResultCount”: 60
> Asking for 20: “Start”: 0, “Count”: 20, “ResultCount”: 80
> Asking for 25: “Start”: 0, “Count”: 25, “ResultCount”: 100
> Asking for more than 25: “Start”: 0, “Count”: 25, “ResultCount”: 100

When running it through the example in the documentation, it seems to return 4 times the amount of unique matches requested (up to 100). When I run it through HaloSharp, it seems to return double the amount of matches requested (up to 50).

I looked to see if this sort of thing was mentioned, but I didn’t see anything about it. Is anyone else seeing this (or was it always like this)? I don’t want to have my application expect additional results and not get them or request fewer than is allowed and waste time.

Hopefully this is an intended change and not a happy little accident. I sure would like to get more than 25 games at a time. I hope I am not the kid reminding the teacher to collect homework before the bell rings. :smiley:

b

Can confirm there is something up with it.
I was experiencing this some days ago. I usually just request for one Mode at once and it was returning me all games of the season at some point, not just 25.
As of now it looks like you get 25 games for every mode you pass as param. If you request for just Arena you get 25, if you request Arena and Warzone you will get 50.
I guess for your examples running against the try-out mode in the documentation you didnt pass a gamemode so it will probably return the games for all 4 modes (arena, warzone, custom, campaign) leading to your numbers.

Ahhh, I didn’t make the connection to the modes. I always passed in Arena and Warzone in my app. I never really thought about custom and campaign because of that. At least I am not going crazy…

Maybe some more information will be coming our way soon.

Yeah, I also noticed this recently.

It would be nice to know if this is deliberate.

I just tried to recreate this and have come up short. Is anyone still having the issue?

I also noticed a one (or more?) new properties that appeared, but have since been removed. We might have seen an not-for-public version of the API.

> 2753093343646559;5:
> I just tried to recreate this and have come up short. Is anyone still having the issue?
>
> I also noticed a one (or more?) new properties that appeared, but have since been removed. We might have seen an not-for-public version of the API.

It looks like it is back to normal. in both the example and when using HaloSharp.

After playing around with it, I kind of liked requesting 25 games and getting 25 from each game mode requested. Maybe they will make it an option.

Thanks for the report. This issue was resolved on Friday (2/26) night. Thanks for keeping us honest!