Skip to content

addDesignEvent et al. should produce an error if provided a player instead of a user ID #122

Open
@Ozzypig-Gamefam

Description

@Ozzypig-Gamefam

The following call fails silently despite it being incorrect:

GameAnalytics:addDesignEvent(player, {
	eventId = "Buy:Apple",
})

The reason for this is that player should be player.UserId, which is not the way a good chunk of Roblox's API works. Therefore, the function should:

  • Extract the userID from a provided Player object to support this call, and/or
  • Produce an error immediately when called using incorrect arguments, ideally via a runtime type check library like osyris' t library

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions