Class Names

[ac-arcana]

I'm curious how people feel about putting class names on basically everything? It's not something necessarily done by default, but I'm finding I want to override a lot of classes. This means I need a class name.

Right now in my Coop MP project (which I'm still progressing on) so far I'm overriding player and pause_menu_controller, but there are probably other things that other users would want to override and we can't anticipate them all.

Should everything have a class name? Is there a down side to class names?

It is a minor first world inconvenience when every time that I merge the main branch I need to re add all my class names.

[Phazorknight]

I've kinda only realized a bit late on how useful and versatile using classes for a lot within COGITO is, but it's slowly getting there.

I'd avoid just turning everything into a class, rather figure out a solid base class and then just customize one-offs in scripts.
For example, I don't think a Flashlight class is necessary, but using the CogitoWieldable class to then do a custom script for the flashlight works great.

Other than that, I'm definitely open for introducing more classes. I suggest to keep Cogito-prefix to avoid naming clashes and clarify what it's used by.

[ac-arcana]

Alright, sooner or later I'll commit a change to add a class name to the player unless you beat me to it.
Stylistically, is it COGITO or Cogito? In code for a prefix, would it be class_name CogitoPlayer for example?

[Phazorknight]

Go for it. And yeah, I'd use Pascal case, so CogitoPlayer.