# Blueprint

### Blueprint System

#### Blueprint Types

1. **Specific Blueprints**: One blueprint per item
   * Create item with name matching the recipe
2. **Shared Blueprints**: One blueprint for multiple items
   * Use `blueprint.name` in recipe to link to common blueprint
   * Example: `brake_blueprint` used by multiple brake recipes

***

You can define blueprints for sale in **lvs\_shop or use** [**exports**](/qb-esx/lvs-crafting/exports-and-commands.md)

```lua
shops = {
    {
        type = 'youtool',
        ...
        items = {
    			{
    				type = 'blueprints',
    				name = 'lvs_blueprint',
    				price = 1500,
    				label = 'Toolbox blueprint',
    				metadata = {
    					type = 'blueprint',
    					label = 'Toolbox blueprint',
    					recipe = 'mechanic_toolbox', -- items name
    					durability = 100
    				}
    			},
    			{
    				type = 'blueprints',
    				name = 'lvs_blueprint',
    				price = 5000,
    				label = 'Brake blueprint',
    				metadata = {
    					type = 'blueprint',
    					label = 'Brake Blueprint',
    					recipe = 'brake_blueprint', -- general name defined in recipes
    					durability = 100
    				}
    			},
        },
        ...
    },
    ...
}

```

#### Blueprint Durability Mechanics

* **Starting durability:** 100 (or custom value in metadata)
* **Durability loss:** `recipe.blueprint.degrade * 100` per craft or default `Config.DefaultBlueprintDurabilityDegrade`
* **Example:** `degrade = 0.05` → loses 5 durability per craft → 20 crafts until destroyed
* **When durability reaches 0:** Tool is automatically removed from inventory
* **If `degrade = 0`:** blueprint has no durability losses


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://fivem.lvsoft.com.ar/qb-esx/lvs-crafting/blueprint.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.