… since this will prevent LFG from showing that the Commander’s map is full.
Moving yourself (Commander) to a separate subgroup was once used to help others to find the player whose map they should join. But this is no longer needed, since
But since LFG apparently uses Subgroup1 to determine whether a Squad’s map is full, keeping this habit does more harm than good.
Yep, I agree, LFG is a mess.
I don’t get from where information about map full comes from It doesnt make sense to use subgroup to determine it at all. Map is much bigger than 50 people, checking squads for map capability would always be wrong because there are people without squads. They must be checking number of players on the entire instance, and count all the players. Codding a search for commander instance IP in squad function to only work in subgroup one doesn’t make any sense. I have joined many squads by queuing where commander was in the subgroup without any problems
Re-posting from my lemmy.wtf account, since outgoing federation from lemmy.sdf appears to be broken at the moment:
@necropola@lemmy.sdf.org said:
Of course I don’t know for a fact that LFG actually checks subgroup 1 to figure out whether a squad’s map is full, but it seemed pretty plausible.
Also, I didn’t say that map full detection is in any way related to the squad size limit. The question is how does LFG determine whether a squad’s map is full? Does it actually check the map of the squad’s commander (squad might not have one) or does it check the map of the first player in subgroup 1 (which is what I think).
I have even seen squads to explicitly use subgroup 1 as a lobby/queue for players not in the commander’s map (yet) which would be really bad, if LFG actually uses the first player of subgroup 1 to check whether the squad’s map is full.
