Proper form for property and channel naming

I’ve seen a lot of different ways people name properties and channels.
Some Just Use Spaces Normally.
sometimes_ill_see_them_using_underscores.
thenThere’sCamelCase
AndPascalCase.
What do you guys think is the best way to go about it?

  • Normal Typing with Spaces
  • under_scores
  • camelCase
  • PascalCase
0 voters

As someone who’s done a lot of Python, i_usually_use_underscores.

Personaly it depends on what the name is for me! If its a long name

ThisPropertyTextIsLong


If its shorter
Short Name


If its kinda in between
Random_Property

Normal text is nice but underscores make it look more a like a variable to me

For Channels i just shorten it

Example: Game End - gmEND

For gimkit I think I mostly just use all lowercase, but for different things I also use camel and pascal cases. Never dashes or underscore though, they’re just a waste of space imho. And why in the world you put spaces it’s just completely useless.

2 Likes

Having inconsistency in your nomenclature can be a problem though. IfIKeep_switching_likeThisThings can be reallyConfusing, especially when you want to try and refer to a property or channel name with a string that can be changed.

1 Like

My channels almost never go over 5 letters

Mostly cuz i’m too lazy to write
But it’s also just quicker to write “lob” than “lobby_teleport” or something like that

3 Likes

All I suggest is consistency – use the same one for the entire map you’re working on!

However, in general, it is by personal preference @some_kid – mine is camelCase.

2 Likes

I don’t see a real use to this topic existing. This does not talk about Gimkit besides asking about properties. Might as well ask what gradient you prefer on props :skull:

But camelCase all the way :partying_face:

I just write Variables in whatever form I like
So I am not gonna vote

I most likely use a format like aVariable CoolVar

InvenCrud

and JUST SOMETIMES
Please_Help

i mostly go with lazy Vars just to get the job done, as I spend time coding as best as I can
Thats my strat plus its easier formatting and unique to you. Just go with what is easier to format and what you think truly fits you

you all may called it camelcase or whatever but The way I do it is
what I call the Lazy Tactic
You summarize the var into smth simple like

PlyrInven

InvenChance

Summary of the story… Im lazy as Frick…
and that I go with what truly fits my coding preferences

1 Like

Honestly when it comes down to it, just name the channel/ property after a sequence of events if you need to remember.

1 Like

I was genuinely curious (and have been for a while now) as to what the forums thought was the best way to format names. I was also wondering if there was a generally agreed best, proper format (though it appears there is not.)

And it is most certainly not off-topic, as it is about building in GKC.
Thanks for your input though!

2 Likes

underscores is called snake_case

3 Likes