Updates To MarketplaceService GetProductInfo Return Values

This topic was automatically opened after 11 minutes.

JayePirate: To support platform health and legacy structures Could we get more detail on how this supports anything better? As far as I can tell, this changes existing behaviour without making anything new possible.

Is this really worth breaking backwards compatibility for? Can’t we keep the existing behaviour with recommendations to use the new method?

I’m assuming Creator.ID can be the ID of whoever last updated the product in the web API? So that’s why this change is being made? But otherwise this doesn’t make any sense just based on this announcement.

The Id in the creator field represents the Agent ID, with users it is known as the User ID. Groups’ agent ID can not be used anywhere except legacy purchase web endpoints.

local MarketplaceService = game:GetService("MarketplaceService") -- Wrap the raw creator table so legacy `.Id` reads still work local function wrapCreator(rawCreator) -- rawCreator is what Roblox now returns: -- Id = userId (User) or 0 (Group) -- CreatorType = "User" | "Group" -- CreatorTargetID = t

Does this mean that the return value will finally be typed instead of any

I would not recommend doing this. Any existing code using only Id and CreatorType is already broken for groups because Id is the Agent ID, not the group ID/creator target ID. This will also break code that utilizes the fact that each group and user have a unique agent ID. Please see this group-owned

-- holy claude. please do not just shove out AI-generated code here, you’re just going to end up confusing people especially when the code itself is just, not valid

This update seems to create more inconsistencies than it solves. Instead of making the API cleaner, it forces us to rewrite perfectly functional legacy code just to handle a 0 value. If CreatorTargetId already correctly identifies the group or user, Creator.Id should either do the same or be depreca

Mr927x: it forces us to rewrite perfectly functional legacy code just to handle a 0 value What “legacy code” actually even uses this that is in use in any games that would be meaningfully impacted?