# F.A.Q > Frequently asked questions for ML Smelter Stations Category: SMELTER STATIONS · Source: https://miciomods.it/docs/ml-smelter-stations-faq · Last updated: 2026-07-05 ## Setup **What frameworks and inventories are supported?** All frameworks supported by ml_bridge: QBCore, QBox, ESX, and Standalone. Inventory support includes ox_inventory, core_inventory, ps-inventory, qs-inventory, and tgiann-inventory. **Can I use TextUI instead of ox_target?** Set `Config.Interaction = 'textui'` in `shared/config.lua`. When set to `nil`, ml_bridge auto-detects the available target system. **Can I disable the floating in-world DUI?** Set `Config.DuiRenderDistance = false` in `shared/config.lua`. **How many languages are available?** Six: English, Italian, German, Spanish, French, and Brazilian Portuguese. Set via `Config.Locale`. ## Stations **What is the difference between persistent and temporary stations?** Persistent stations (`persistent = true`) are saved to the database and survive server restarts. Temporary stations (`persistent = false`) are removed when the server restarts. **Can I create stations that players cannot pick up?** Use `Config.FixedStations` to define permanent world stations. These cannot be picked up or destroyed by players. **Can fixed stations use existing map props instead of spawning new ones?** Set `spawnProp = false` in the fixed station definition and configure a zone instead: **shared/config.lua** ```lua { id = 'my_campfire', stationType = 'campfire', coords = vec3(100.0, 200.0, 30.0), heading = 0.0, spawnProp = false, zoneType = 'sphere', zoneRadius = 2.0, } ``` **What happens when a station runs out of durability?** The station breaks and cannot be used until repaired. Repair items are defined per station type in `RepairItems`. When picking up a broken station, the item preserves its durability via the `furnacelife` metadata field. **How does the station limit work?** Each player can place up to `Config.MaxStationsPerPlayer` stations. Fixed stations do not count toward this limit. The count is based on the player's identifier, not the server source. ## Recipes **What is carbonization?** Each recipe has a `carbonize_time` in seconds. After crafting completes, a timer starts. If the player does not collect the finished item before this timer expires, the item is destroyed (carbonized). **Can one station handle multiple recipe categories?** Add multiple entries to the station's `cook_categories` array: **shared/config.lua** ```lua cook_categories = { 'food', 'medical', 'default' }, ``` **How do I add a new recipe?** Add a new entry to `Config.Recipes` with a unique key. The `category` must match one of the categories in a station's `cook_categories`: **shared/config.lua** ```lua ['my_recipe'] = { category = 'food', tier = 1, cook_time = 30, carbonize_time = 120, ingredients = { { name = 'item_a', count = 2 }, }, results = { { name = 'item_b', count = 1 }, } }, ``` ## XP / Progression **How do I disable the XP system?** Set `Config.XP.Enabled = false`. All tier restrictions are bypassed (every recipe becomes craftable regardless of level) and the Progression tab is automatically hidden in the UI. **Which XP provider should I use?** - `'internal'` if you want it to work out of the box with no extra resources - `'ml_skills'` if you already have the ml_skills resource and want the crafting tree synced with player skills - `'devhub'` if you run the DevHub XP system - `'custom'` to wire your own backend via the handlers in `open/server.lua` **How do I switch between XP providers?** Change `Config.XP.Provider` to one of: `'internal'`, `'ml_skills'`, `'devhub'`, `'custom'`. Each provider has its own configuration block in `Config.XP`. **What bonuses do tiers give?** Two bonus types, both configurable per tier in `Config.XP.Tiers`: - **speed**: Reduces cook time by a percentage (e.g., `0.12` = 12% faster) - **antiCarbonize**: Extends carbonization time by a percentage (e.g., `0.20` = 20% more time to collect) Both can be toggled globally in `Config.XP.Bonuses`. ## Updates **How do I update the script?** 1. Download the latest version from CFX Portal 2. Backup `shared/config.lua`, `server/config_server.lua`, and `open/` folder 3. Replace all files except your backed-up configs 4. Compare your config with the new defaults for any added keys 5. Restart the resource Database tables are migrated automatically, missing columns are added on startup.