Summary
There is no 'FindCreativeObjectWithTags(Tags:tag)` function in the digest, only single tag queries exist.
# Generates a `creative_object_interface` for every creative object that has been marked with the specified `Tag`. Will not find anything if called on a default constructed object.
(InCreativeDevice:creative_device).FindCreativeObjectsWithTag<public>(Tag:tag)<transacts>:generator(creative_object_interface) = external {}
The following function in the Fortnite.digest.verse is missing <transacts> specifier.
Returns a queryable tag_view which can be used to query the tags on CreativeObject.
(CreativeObject:creative_object_interface).GetTags<native><public>():tag_view
This leads to a situation where you cannot query for tags in the same decides context, and must write your queries like this:
for( TaggedObject : CreativeDevice.FindCreativeObjectsWithTag(MyTag) ):
TagView := TaggedObject.GetTags()
if( TagView.Has[ OtherTag ] ):
# Now you have to return this out of here… (Not scalable or user friendly.)
### Please select what you are reporting on:
Creative
### What Type of Bug are you experiencing?
Assets
### Steps to Reproduce
You can just read the digest and think about it, or if you feel compelled you can open vscode and write the code to find an object that contains more than 1 tag.
### Expected Result
You would have the same functionality that was available with `GetCreativeObjectsWithTag` prior to deprecation.
### Observed Result
You end up with a function like this and no easy way to return the value and encapsulate the behavior.
for( TaggedObject : CreativeDevice.FindCreativeObjectsWithTag(MyTag) ):
TagView := TaggedObject.GetTags()
if( TagView.Has[ OtherTag ] ):
# Now you have to return this out of here…
### Platform(s)
All
### Additional Notes
This highlights and important part of the change management process that is often overlooked:
Before deprecating a process, it's important to test and make sure that you can still complete its intended purpose with the new process prior to deprecating it.
Also, if you guys aren't going to look at any of the requests in feature requests and this kind of stuff requires bug reports to actually be addressed I think there may be a breakdown in the handling chain somewhere that may need to be addressed. There's a feature request from August 2023 to add <transacts> to GetTags() that never got any substantial response.
I have been outspoken in the past on the structure and handling of the forums here and QA issues generally so I won't beat the dead horse, but I will mention that the Star Citizen bug reporting system and handling has a lot of good ideas on how you could distribute and decentralize the handling of bugs and features to allow the community to help organize and contribute which is a much more scalable approach than what is currently going on. This wouldn't impact your internal handling, just everything up to the intake portion of your Forums > QA workflow.