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
+2Lines changed: 2 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -51,6 +51,8 @@ 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.
55
+
54
56
**Warning:** When tagging an instance, it is common that some resources
55
57
are used to give the tag its functionality, e.g. event connections or
56
58
tables. To prevent memory leaks, it is a good idea to clean these up
Copy file name to clipboardExpand all lines: content/en-us/reference/engine/classes/Instance.yaml
+2Lines changed: 2 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -321,6 +321,8 @@ methods:
321
321
already applied. Successfully adding a tag will fire a signal created by
322
322
`Class.CollectionService:GetInstanceAddedSignal()` with the given tag.
323
323
324
+
**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.
325
+
324
326
Note that when tagging an instance, it's common that some resources are
325
327
used to give the tag its functionality, for example event connections or
326
328
tables. To prevent memory leaks, it's a good idea to clean these up
0 commit comments