CollectionService:GetTagged() returns nil on client

Help and Feedback Scripting Support
#1

When I use CollectionService:GetTagged() on the client it returns nil, but when I use it on the server it returns the expected result. Why is this happening?

And yes I’m sure I have put the exact same string on both places.

On Client:
image

On Server:
image

2 Likes
#2

Can you show us the scripts so we can see what you have put?

2 Likes
#3

Client:

local collectionService = game:GetService("CollectionService")
print(collectionService:GetTagged("BoosterPad"))

Server:

local collectionService = game:GetService("CollectionService")
print(collectionService:GetTagged("BoosterPad"))

Exact same code but still different results.
Also I will not provide any more code since that doesn’t have much to do with my issue.

2 Likes
#4

Are you certain they are all tagged on the server? It could be a replication issue. I personally use Tag Editor - Roblox in my workflow while developing and have never encountered an issue like this, as tagging instances follows the same replication rules as anything else.

2 Likes
#5

Yes I also use Tag Editor when tagging my instances.

#6

Yeah, my thoughts were similar, I just tried to replicate the issue in studio and couldn’t do so.

1 Like
#7

Interesting. Have you updated to a newer version? You can check by clicking the manage plugins button.

1 Like
#8

Also when hovering over tagged instances in-game it shows this:
image

Not too sure if this has anything to do with it.

1 Like
#9

I do not have any updates available.

#10

Interesting. I’d just try restarting studio then and see if the issue persist, because I have not been able to replicate this issue.

#11

I’ve been trying to fix this for some time now and have restarted studio multiple times already.

#12

Also testing this in a throwaway place.

#13

Wait. Perhaps try adding a task.wait(5) or something on the client script? There could be an small chance that all the data just didn’t have time to replicate yet? Other than that, I don’t know what other explanation there could be. It’s incredibly unlikely though. If the problem persist I’d try filing a bug report.

1 Like
#14

I can’t replicate this issue here.

#15

This didn’t work either, going to try to delete all of the tags and recreate them again.

#16

Found the issue, I had StreamingEnabled turned on so the instances didn’t load in time.

2 Likes
#17

Thanks a lot for the help anyways!

1 Like