that would only work for instances that are a part of the original place file, it is not a viable solution for dynamically created instances in live servers.
that would only work for instances that are a part of the original place file, it is not a viable solution for dynamically created instances in live servers.
why is this a condition? why wouldnt you be able to use List Instance Children method during a live server session? if it’s not viable because there’s too many API calls or too much latency that’s fair. otherwise you could also create a queueing system that batch gets instance IDs behind the scenes for dynamically initialized instances , so you can sort of have them “ahead of time” and not wait till the last second to make the API call.
because this API only exposes instances that exist within the original place file, it does not expose instances that exist only in a live server.
is that documented anywhere? i believe you considering roblox’s documentation can be spotty but i would hope that is mentioned because it is a glaring oversight. unique ids are an essential part of restful APIs so it seems odd they’d just just leave it out for dynamically generated live instances when it works for static instances. i understand it can be difficult to sandbox lua but im confused why it’s exposed on the rest api side then if it’s not properly sandboxed.