Installation

Dependencies#

• vrp — framework. Outside vRP, see Integrations.
• oxmysql — warehouse, queues, upgrades, orders and history.
• PolyZone — interaction zones.

Steps#

1. Generate the package in the panel and extract it as resources/sf_crafting.

2. Add it to server.cfg, after the dependencies:

   ensure vrp
   ensure oxmysql
   ensure PolyZone
   ensure sf_crafting
   

   Copy

3. In config/config.lua, check Config.CraftConfig.Grupo. The default is "Admin"; if your staff group has another name, change it here. Only members of that group can open /craftconfig — not even you if the name does not match. Empty means nobody, on purpose: the configuration is never open to everyone.

4. Start the server. Tables are created on the first start.

5. Join the game and run /craftconfig to create the first bench.

A fresh install starts with no benches. That is expected: benches, recipes and routes no longer live in a file. The console says so, and so does /sfdiagnostico.

Upgrading from an earlier version#

New tables are created and old ones migrated on the first start, with nothing lost. Two things worth knowing:

• Existing benches move to shared mode, which is the behaviour they always had: one warehouse per bench. The accumulated stock stays there. If you want a per-player warehouse or a faction vault, change the mode in /craftconfig.
• Upgrades already bought still apply, now attached to the bench's shared warehouse.

Back up the database first, as with any upgrade.

First test#

Start small: one bench, one recipe with two ingredients and a route with two stops. Run /sfdiagnostico before opening it to players — it catches a non-existent item and a wrong permission, the two most common causes of "the bench opens and never produces".