Template talk:KV BreakableProp: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
mNo edit summary |
||
| Line 1: | Line 1: | ||
Should this template include kv_targetname, kv_damagefilter, and kv_shadow? Or should those go in each article? —'''[[User:Maven|Maven]]''' <sup>([[User talk:Maven|talk]])</sup> 19:34, 5 Oct 2005 (PDT) | Should this template include kv_targetname, kv_damagefilter, and kv_shadow? Or should those go in each article? —'''[[User:Maven|Maven]]''' <sup>([[User talk:Maven|talk]])</sup> 19:34, 5 Oct 2005 (PDT) | ||
:I'm aware that the system has changed somewhat since my fix, so things might look different now. Moving ''kv targetname'' to this template seems possible unless I'm mistaken, but the benefits are minor: It only appears in two places: ''kv basepropphysics'' and ''kv prop dynamic base''. Just make sure that it ends up as the first keyvalue in every entity. | :I'm aware that the system has changed somewhat since my fix, so things might look different now. Moving ''kv targetname'' to this template seems possible unless I'm mistaken, but the benefits are minor: It only appears in two places: ''kv basepropphysics'' and ''kv prop dynamic base''. Just make sure that it ends up as the first keyvalue in every entity. | ||
''kv damagefilter'' is now a part of the ''kv breakable'', and ''kv shadow'' is a part of ''kv studiomodel'', each which are applied in lots of other places than here, in perfect harmony. Apart from the ''kv targetname'' the two entire days I spent optimizing this system tells me that this system has now reached perfection. --[[User:Andreasen|Andreasen]] 16:22, 15 Mar 2006 (PST) | :''kv damagefilter'' is now a part of the ''kv breakable'', and ''kv shadow'' is a part of ''kv studiomodel'', each which are applied in lots of other places than here, in perfect harmony. Apart from the ''kv targetname'' the two entire days I spent optimizing this system tells me that this system has now reached perfection. --[[User:Andreasen|Andreasen]] 16:22, 15 Mar 2006 (PST) | ||
Revision as of 17:22, 15 March 2006
Should this template include kv_targetname, kv_damagefilter, and kv_shadow? Or should those go in each article? —Maven (talk) 19:34, 5 Oct 2005 (PDT)
- I'm aware that the system has changed somewhat since my fix, so things might look different now. Moving kv targetname to this template seems possible unless I'm mistaken, but the benefits are minor: It only appears in two places: kv basepropphysics and kv prop dynamic base. Just make sure that it ends up as the first keyvalue in every entity.
- kv damagefilter is now a part of the kv breakable, and kv shadow is a part of kv studiomodel, each which are applied in lots of other places than here, in perfect harmony. Apart from the kv targetname the two entire days I spent optimizing this system tells me that this system has now reached perfection. --Andreasen 16:22, 15 Mar 2006 (PST)