Forged Alliance Forever Forged Alliance Forever Forums 2015-03-27T11:05:26+02:00 /feed.php?f=3&t=9643 2015-03-27T11:05:26+02:00 2015-03-27T11:05:26+02:00 /viewtopic.php?t=9643&p=97181#p97181 <![CDATA[Re: Often getting the same map in ladder]]>
ZLO_RD wrote:
Give human random data, and he will find tons of patterns in it

i actually heared story that some one replaced random algorithm to a not random one cause users were compainig that it was not random enought...


That was, I think, Apple, for the iTunes "shuffle" feature.

Statistics: Posted by ckitching — 27 Mar 2015, 11:05


]]>
2015-03-27T08:35:01+02:00 2015-03-27T08:35:01+02:00 /viewtopic.php?t=9643&p=97174#p97174 <![CDATA[Re: Often getting the same map in ladder]]> Statistics: Posted by ZLO_RD — 27 Mar 2015, 08:35


]]>
2015-03-26T22:51:48+02:00 2015-03-26T22:51:48+02:00 /viewtopic.php?t=9643&p=97147#p97147 <![CDATA[Re: Often getting the same map in ladder]]> (from TheRedViper)

p < 10^-graham's number

Statistics: Posted by Vee — 26 Mar 2015, 22:51


]]>
2015-03-26T17:20:34+02:00 2015-03-26T17:20:34+02:00 /viewtopic.php?t=9643&p=97123#p97123 <![CDATA[Re: Often getting the same map in ladder]]> Statistics: Posted by Gorton — 26 Mar 2015, 17:20


]]>
2015-03-26T17:11:49+02:00 2015-03-26T17:11:49+02:00 /viewtopic.php?t=9643&p=97122#p97122 <![CDATA[Re: Often getting the same map in ladder]]>
i actually heared story that some one replaced random algorithm to a not random one cause users were compainig that it was not random enought...

Statistics: Posted by ZLO_RD — 26 Mar 2015, 17:11


]]>
2015-03-26T11:46:16+02:00 2015-03-26T11:46:16+02:00 /viewtopic.php?t=9643&p=97101#p97101 <![CDATA[Re: Often getting the same map in ladder]]>

Statistics: Posted by Vee — 26 Mar 2015, 11:46


]]>
2015-03-26T02:02:28+02:00 2015-03-26T02:02:28+02:00 /viewtopic.php?t=9643&p=97084#p97084 <![CDATA[Re: Often getting the same map in ladder]]>
Code:
(SELECT mapid
FROM   game_stats
        INNER JOIN game_player_stats
                ON game_player_stats.gameid = game_stats.id
WHERE  playerid = ?
LIMIT  5)
UNION DISTINCT
(SELECT mapid
FROM   game_stats
        INNER JOIN game_player_stats
                ON game_player_stats.gameid = game_stats.id
WHERE  playerid = ?
LIMIT  5);


Having two select clauses ensures we get the latest 5 maps for each player.

I'm assuming this isn't very controversial, so I'll get this into the network update.

Statistics: Posted by Sheeo — 26 Mar 2015, 02:02


]]>
2015-03-26T01:02:56+02:00 2015-03-26T01:02:56+02:00 /viewtopic.php?t=9643&p=97078#p97078 <![CDATA[Re: Often getting the same map in ladder]]> How hard would be this change?

Statistics: Posted by speed2 — 26 Mar 2015, 01:02


]]>
2015-03-26T00:19:06+02:00 2015-03-26T00:19:06+02:00 /viewtopic.php?t=9643&p=97074#p97074 <![CDATA[Re: Often getting the same map in ladder]]>
Vee wrote:
Perhaps the problem is that the table ladder_map_selection contains duplicate entries


This assumption is false: https://github.com/FAForever/server/blob/develop/src/lobbyconnection.py#L1054

While the code is a bit contrived, duplicates are indeed filtered on insertion to the database.


I could analyze the map selections of some players who claim they are unfairly given the same maps, if you'd like.

Statistics: Posted by Sheeo — 26 Mar 2015, 00:19


]]>
2015-03-25T16:52:28+02:00 2015-03-25T16:52:28+02:00 /viewtopic.php?t=9643&p=97032#p97032 <![CDATA[Re: Often getting the same map in ladder]]> https://github.com/FAForever/server/blo ... er.py#L109

Common maps still have more chance to be played because they are in the pool of both players so they have double chance to be played, but now you will not only get common maps. We could also give some extra chance to common maps to make it more than double, just not 100% chance. But if the database contains duplicate rows then that should be fixed first of course (that is the only other reason I can think of why some people often get the same map).

Statistics: Posted by Vee — 25 Mar 2015, 16:52


]]>
2015-03-25T16:43:17+02:00 2015-03-25T16:43:17+02:00 /viewtopic.php?t=9643&p=97029#p97029 <![CDATA[Re: Often getting the same map in ladder]]>
Edit: i kinda like idea, not sure about removal of common maps thought.

Statistics: Posted by ZLO_RD — 25 Mar 2015, 16:43


]]>
2015-03-25T13:41:17+02:00 2015-03-25T13:41:17+02:00 /viewtopic.php?t=9643&p=97010#p97010 <![CDATA[Often getting the same map in ladder]]> https://github.com/FAForever/server/blo ... er.py#L130 This code seems OK. Perhaps the problem is that the table ladder_map_selection contains duplicate entries, so that you have a higher chance to get those maps that have duplicate entries. Or perhaps it is the algorithm after all. How about changing it to this:

Code:
def choose_ladder_map_pool(self, player1, player2):
   lucky_player = [player1,player2][random.randint(0,1)]
   maps = self.getSelectedLadderMaps(lucky_player.id)
   missing_maps = 15 - len(maps)
   if missing_maps > 0:
      maps += self.getPopularLadderMaps(missing_maps)[:missing_maps]
   return maps


Explanation: we randomly pick one of the two players's map pools. If that map pool has less than 15 maps, we extend it to 15 with popular maps. Then we pick a random map from that list. This code is simpler and will result in a more diverse set of maps being played because all maps that a player has selected have some chance to be picked, rather than just the intersection. Also the 33% popular maps chance has been removed. Now you will only get your mappool extended with popular maps if you have selected less than 15.

Statistics: Posted by Vee — 25 Mar 2015, 13:41


]]>