GuiService:AddSelectionParent throws warning due to duplicate "PlayerlistGuiSelection" group

[KrimsonWoIf (ClassicDev)]

Title:

GuiService:AddSelectionParent produces warning due to duplicate “PlayerlistGuiSelection” registration

---

Description:

The method GuiService:AddSelectionParent triggers a warning stating that a selection group with the name PlayerlistGuiSelection already exists. This warning appears to originate from internal Roblox scripts and is observed consistently when the PlayerList CoreGui is toggled on and off, either programmatically or through user interaction.

This behavior results in repeated warning messages in the output console, which interferes with debugging and suggests possible redundant selection group registration without prior cleanup or validation.

---

Reproduction Steps:

1. Launch any game in Roblox Studio or live client.
2. In a LocalScript or command bar, execute the following:

local StarterGui = game:GetService("StarterGui")
StarterGui:SetCoreGuiEnabled(Enum.CoreGuiType.PlayerList, false)
wait(0.5)
StarterGui:SetCoreGuiEnabled(Enum.CoreGuiType.PlayerList, true)

3. Observe the output window. The following warning will appear each time the PlayerList is re-enabled:

GuiService:AddSelectionParent already has selection group with name PlayerlistGuiSelection, overwriting selection group.

4. Repeating the toggle multiple times results in repeated occurrences of this message.

---

Expected Behavior:

Re-enabling CoreGui elements such as the PlayerList should not result in warning messages under normal usage. Internal selection group registration should verify the existence of a group before attempting to register it again, or remove the previous group as needed.

---

Actual Behavior:

Each time the PlayerList is re-enabled, GuiService:AddSelectionParent appears to be called internally with the same group name. The method does not validate whether the group already exists, leading to repeated warning messages in the developer console.

---

Impact:

The repeated warning interferes with debugging by cluttering the output window. It may also indicate an inefficient or redundant registration process within internal UI handling scripts.

Relevant Post:

GuiService:AddSelectionParent already has selection group

Bumping because this message has been plaguing me recently. It seems that it occurs every single time you enable and then re-enable the player leaderboard. game:GetService("StarterGui"):SetCoreGuiEnabled(Enum.CoreGuiType.PlayerList, false) --Other code might go here, or something... game:GetService("StarterGui"):SetCoreGuiEnabled(Enum.CoreGuiType.PlayerList, true) If you run this in the command bar, the warning should appear. RōBLOX pls fix.

[br_cks]

Noticing this each time the player list is opened

[Sim_Q1 (Sim)]

I’ve noticed this often when looking at the dev console. I don’t think it impacts the game(s) performance, but it’s quite noticeable.

[Chris0neilson0]

Hi. there are spam in warning message our game.

Reproduction Steps: A

After launch our game then hit the esc key to show display and hit esc key to release it display.
I check state: error message. what happened.

Its Player List is display after load game.

Reproduction Steps: B

After launch our game and load screen while loading… or 100% be ready play.
Is in LocalScrpit StarterGui:SetCoreGuiEnabled(Enum.CoreGuiType.PlayerList, true)

There produces warning due to duplicate “PlayerlistGuiSelection” in our game.

[br_cks]

[SubtotalAnt8185]

Same here. This time I didn’t even do anything other than open up the menu and change the volume.

@daidoujicomplex

custom reset bindable

When this is in effect it also occurs as well.

[ParadoxSoftwork (Paradox)]

I’m getting this too now. It’s EXTREMELY annoying.

[ChickwensRule]

It’s also happening to me.

[Lucatacos2213 (Lucatacos)]

I’m seeing the same bug:

[PadinFull89]

@KrimsonWoIf we will investigate soon, given this thread has not been looked at in a while we would like to know if the issue is still reproducible/relevant by you?

[Oghmond]

Although not directed toward me, yes it is still happening. I just ran into this issue.

[PadinFull89]

thanks for confirming @Oghmond well put into the back log as an item to be picked up soon

[extraclear (Maybelline)]

Will it be possible to get this fixed soon? I’m working as part of a team and we’re developing a secure in-house CLI for our experiences (for reasons where off-the-shelf solutions weren’t cutting it). We’re propagating server errors and client errors, but this warning not only spams our CLI, it breaks any normal formatting at random and no other ROBLOX-generated warning causes this behaviour.

There is a workaround right now, that is otherwise not fun to use because the ROBLOX team has marked the endpoint as deprecated, causing an deprecatedApi warning in the new typesolver.