"bug" in player.max_mmr

[Xample33]

"bug" in player.max_mmr

[CNDRD]

That's a weird thing..
Since that's only supposed to happen when Ubi doesn't return the previous rank mmr and the next rank mmr (basically any case, other than ranked..)

siegeapi/siegeapi/ranks.py

Lines 54 to 57 in 2807841

	if self.prev_rank_mmr == 0 and self.next_rank_mmr == 0:
	self.rank, self.prev_rank_mmr, self.next_rank_mmr, self.rank_id = _get_rank_from_mmr(self.mmr)
	self.max_rank_id = self.max_mmr = -1
	self.max_rank = "Undefined"

Ubisofts API is so stupid it could very well be a one-off case
But, I personally, am using this library daily to grab data for ~10 users every 30 minutes
Never seen that happen

So if you could provide me with the account name you're using so I could investigate further
(Or any other that has only one game played; I ain't searching for one)

(I also don't know why I decided to return -1 and not 0, imma fix that in the next release probably)

[Xample33]

Maybe you can just set the return to 0 instead of -1.
But the username is Xampl3_ (mine), and i have played only one ranked game in this season.

[CNDRD]

I can definitely do that, that isn't a problem
This just isn't supposed to happen when you want ranked stats...

[Xample33]

yeah yeah

[CNDRD]

I have pushed the updated code that correctly returns 0 when calling .load_ranked()
Along with a new v4.1.5 release on GitHub releases & PyPI

This definitely wasn't happening in the past so thanks for letting me know