You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en-us/reference/engine/classes/CollectionService.yaml
+8-4Lines changed: 8 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -51,11 +51,15 @@ methods:
51
51
signal created by `Class.CollectionService:GetInstanceAddedSignal()` with
52
52
the given tag.
53
53
54
-
**Warning:** An instance's tags that were added client-side will be dropped if the server later adds or removes a tag on that instance, because the server replicates all tags together and overwrites previous tags.
54
+
##### Warnings
55
+
56
+
- An instance's tags that were added client-side will be dropped if the server
57
+
later adds or removes a tag on that instance, because the server replicates all
58
+
tags together and overwrites previous tags.
55
59
56
-
**Warning:** When tagging an instance, it is common that some resources
57
-
are used to give the tag its functionality, e.g. event connections or
58
-
tables. To prevent memory leaks, it is a good idea to clean these up
60
+
- When tagging an instance, it is common that some resources
61
+
are used to give the tag its functionality, for example event connections or
62
+
tables. To prevent memory leaks, it's a good idea to clean these up
59
63
(disconnect, set to nil, etc) when no longer needed for a tag. Do this
60
64
when calling `Class.CollectionService:RemoveTag()`, calling
61
65
`Class.Instance:Destroy()` or in a function connected to a signal returned
0 commit comments