Standardize the "Id" properties

As a Roblox developer it’s currently hard to predict and memorize all the different variations of “Id” . We currently have the following properties:

The Id Group

  • TextureId: Tool, SpecialMesh
  • MeshId: MeshPart, SepcialMesh
  • SoundId Sound
  • AnimationId: Animation
  • BaseTextureId: CharacterMesh
  • OverlayTextureId: CharacterMesh
  • UserId: Player
  • CharacterAppearanceId: Player

The ID Group

  • TextureID: MeshPart

The Image Group

  • Image: ImageLabel, ImageButton
  • TopImage: ScrollingFrame
  • BottomImage: ScrollingFrame
  • MidImage: ScrollingFrame

The Other Group

  • Texture: Decal, Texture, Beam, ParticleEmitter, Trail
  • PantsTemplate: Pants
  • ShirtTemplate: Shirt
  • Graphic: ShirtGraphic
  • CursorIcon: ClickDetector

Where crossover works (Texture) some properties use ID, some Id, and some just use Texture. Where object specific properties are found some use Id, some don’t. Guis are the only area where “Image” is used and Id isn’t found. And this is only for properties. There exist functions with different casing references to Id.

If these properties and functions could be standardized in some way it would save myself (and I’m sure others) time and effort in having to check properties to make sure we’re typing out the correct form of Id. There isn’t anything quite as annoying as having to break my workflow to see if it’s a capital d or some other term entirely.

24 Likes

I guess this is an issue. I mean I don’t really see how standardizing a single convention helps beyond organization. Ok.

1 Like

You have to go to the wiki to check what the image property is named whenever you access it through a script instead of just knowing to type obj.Image.

3 Likes