Template talk:KeyValue

Key Value definitions incomplete

Key value definitions should include both the "Friendly Name" for the keyvalue and the name used in the code, if only for the sake of completeness. A field should be added to this template along with a statement to that effect. Kp.2012 20:57, 4 May 2012 (PDT)

Output and input values

Inputs and outputs can have values, this should be standardized.--Henke37 09:40, 1 September 2012 (PDT)

Default engine values?

Apart from FGD definitions (which can be modified), keyvalues can have in-engine defaults which would be useful to know for the various ways in which entities can be created. So should something like that be added here, or maybe done in some other way, or even at all? I found myself needing to know default values a few times but I couldn't rely on the FGD since it may not always reflect the true defaults, especially for custom FGDs. It would of course affect a lot of pages and require a lot of work to add to all the entities (which can be done slowly over time), but I think it would be a useful addition to consider, if not purely just for completeness. --BetweenReality (talk) 20:56, 25 August 2025 (PDT)

I've drafted the proposal in Template:KeyValue/sandbox, and the relevant draft doc in Template:KeyValue/sandbox/doc for testing. I essentially just copied the existing code for default values used in Template:MatParamDef since that's an existing standard, and I fixed the formatting to work with this template, though I also moved it to be after KV Type instead of at the end since it's more relevant to the keyvalue itself than the game availability parameters are.

I'll wait a few days before merging these into the real template in case anyone has any reservations about this proposal. Once implemented it shouldn't affect any pages until people start using it. --BetweenReality (talk) 12:44, 28 August 2025 (PDT)