GetChildrenWithProperties

[sparker22]

All conclusions you can make in like 10-20 minutes.

@ouohello

What other API do they have to support the use case?

If you know the API at all or basic math you can provide an almost immediate answer.

@ouohello

What if something in that API breaks and lots of old games are using it

Well deprecation the whole point is to discourage use so in the future it can be removed. They’ve removed API members in the past definitely breaking older games.

@TheGamer101

A good concept to use when deciding if an API should be added or not is having the API start on minus 100 points. You then need to come up with sufficient reasons to offset this minus 100 negative. It is easy to think that adding an extra utility API here or there isn’t a problem because it has some value to a small number of people, but you really have to consider if it outweighs the negatives such as harder to understand API or the engineering time taken to implement it.

Thanks for the article. I’ll definitely read it to get more insight on deciding this kind of stuff as I know my personal reasoning may not be the only way of looking at it.

@Anaminus

Based on that criteria, these would also be bloat:

FindFirstAncestor
FindFirstAncestorOfClass
FindFirstAncestorWhichIsA
FindFirstChild
FindFirstChildOfClass
FindFirstChildWhichIsA
GetDescendants
IsAncestorOf
IsDescendantOf

Your filter suggestion would definitely be much better in terms of reducing API count. FindObjectAPI(FilterParam)
Could fit nearly every use case.

[ouohello]

I was talking about general practices in regards to “deprecating” or “removing” an API. But nice.