> For the complete documentation index, see [llms.txt](https://community.threekit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community.threekit.com/platform-documentation/catalog-2.0-docs/project-data/operators/material-operators/template-override.md). # Template Override Override a single template property of VRay Materials with a new value. ### **Property Name** Name of the property to replace Must start with `TK_` and must be an existing property in a template material ### **Property Type** `Map`, `Color`, or `Number` ### **Map** Texture asset used to replace the original map value Only available if the property type is set to `Map` ### **Color** Color value used to replace the original color value Only available if the property type is set to `Color` ### **Number** Number value used to replace the original number value Only available if the property type is set to `Number` ### Limitations * Can only be applied on an imported VRay material * If the wrong **Property type** is selected, based on the original type of the property in the template material, it's undefined behavior * The number value doesn't have any validation or limits, this might cause undefined behavior depending on the role of the `TK_` property in the material definition --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://community.threekit.com/platform-documentation/catalog-2.0-docs/project-data/operators/material-operators/template-override.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.