Map drops biased towards map host?

I haven't hosted a single map this week, and I haven't got a single map drop for the last +50 maps or so.

My friend who has been hosting the maps gets at least one map drop each round. Sometimes up to 4 (although crappy ones).

We don't play SA, so there's no chance that I miss the drops and some loot noob steals them.

Is this an intended, hidden mechanic?
If so, I think it's great that the map host gets at least one map whenever they host.

I'm fairly certain that map drops within maps get assigned to the person that plugged the map into the laboratory.

Of course maps drop only for the host.

I may be misunderstanding this, but:
- all white, blue and yellow maps go the map host
- all unique maps are randomly distributed over players
so if you are not hosting you normally get no maps.

Map hosts get between 0 and 13 (most I have ever seen) maps. Getting 1 or more for long streaks is not abnormal. And, as everyone finds out sooner or later, getting long streaks of zero maps is also quite normal.

It's poor documentation I only found out about that by chance
You could play for years and never find out that was how it worked

Ah, that's nice. Thanks for the confirmation, I was getting worried that I wronged the RNG god somehow.

And yeah, I only started noticing this since my friend started hosting all maps. Before that I thought that map drops were random, like currency.

"

mrjonno wrote:

It's poor documentation

Well there really isn't much documentation for anything in PoE, it's a play and learn game :)

Maps used to drop for anyone, and it was terrible. You had to know people to map with, you couldn't even do 66s from party board. No one wanted to use their only maps so some random person could get the drop.

"

mrjonno wrote:

It's poor documentation

It's intended that way. If you want to know what's going on, read patch logs, read dev logs and take a look at the PoE wiki.

The only exception is "unique maps" since they are considered "unique" before "map" by the game engine, and are therefore allocated randomly and not to the map host only.

and yes, it makes public party's a lot easier. There used to be a unspoken rule of "m2m" meaning "map to maker", but not everybody in a public party could be trusted with this rule-set.

I am quite happy with the current implementation.