Template talk:Studio rendering note

Feedback would be appreciated

I was thinking this should be used instead of the {{KV CBaseAnimating}} template for any entity that isn't specifically designed as a generic model entity (so not prop_dynamic, for example). Unlike {{brush rendering note}}, I added a field to specify KVs that are basically unusable since game code will often override them.
— SirYodaJedi (talk) 12:24, 26 March 2025 (PDT)

Wanted to create template like this after the brush rendering note but couldn't figure out how to actually make it generic enough and not confusing which is still giving me a headache and thus I only made the Rendering and studio model related KIO draft page and something still feels off.

In case of brushes it was simple because everything only affects rendering and it's same for all brush entities and there is also far fewer brush entities than entities that use studio models.

In case of studio model it's far more varied and there are keyvalues like body, model, solid which also affect collision and therefore other stuff than rendering. The animation stuff is also mostly relevant to prop_dynamic and any other entities mostly override such functionality. It's also lot of times not relevant for the given entity as 99.999% you are not going to touch such stuff for example prop_minigun, weapon_smg_spawn or prop_coreball etc. will always be used as is and the rare person that wants to do something more with it will probably find their way to CBaseAnimating (as many entity pages now have class hierarchy) and from there to Rendering and studio model related KIO.

Overall I think it's good way to deprecate {{KV CBaseAnimating}} but it probably shouldn't be on every entity derived from CBaseAnimating. And maybe I am overthinking certain stuff --Nescius (talk) 14:24, 26 March 2025 (PDT)