Configuration

This script mainly uses these two config files:

• config/main.lua
• config/builder.lua

Task module code also lives under:

• core/builder/modules

If you remember only one rule, remember this:

• config/main.lua = menu access, XP, clothing, UI, and general behavior
• config/builder.lua = actual routes, rewards, vehicles, and step order
• core/builder/modules = the logic behind each builder task module

Quick Answers#

• Menu command, key, or tablet item: config/main.lua -> Config.BuilderMenu
• Change XP, clothing, score box, or average awards: config/main.lua
• Disable a route: config/builder.lua -> route disabled = true
• Change cooldown: config/builder.lua -> route cooldown
• Change team size, vehicles, rewards, or step order: config/builder.lua
• Change which builder tasks a route uses: config/builder.lua -> steps
• Deep module behavior: core/builder/modules/<module_name>/

What Is Inside config/main.lua?#

The real source file controls:

• Config.locale
• Config.BuilderMenu
• Config.Levels
• Config.XPMultipliersBetweenLevels
• Config.InfoBox
• Config.ScoreBox
• Config.CleanMoney
• Config.JobClothing
• Config.AvgAwards
• Config.debug

Default item-based menu access uses:

itemName = "builder_tablet"

What Is Inside config/builder.lua?#

This file controls the real job routes:

• employers
• specialSkillbars
• blips
• scenarios

Each route entry uses fields such as:

• disabled
• name
• teamSize
• cooldown
• vehicles
• rewards
• steps

How Do I Disable A Route?#

Open:

config/builder.lua

Then find the route block you are testing and set:

disabled = true

If nothing changes in game, you probably edited a different route block than the one you started.

How Do I Change Cooldown, Rewards, Vehicles, Or Team Size?#

Use the same route entry in config/builder.lua.

The values you will usually edit are:

• cooldown
• teamSize = { min = 1, max = 3 }
• vehicles = { ... }
• rewards = { ... }
• steps = { ... }

Which Step Keys Exist In The Default Source?#

The real route file uses step keys such as:

• object_placement
• pour_concrete
• repair_hydrants
• broken_bridge_repair
• repair_electric_box
• pipe_valve_opening
• building_wall
• welding

When you change the steps array in config/builder.lua, you are changing the order and type of builder work the route runs.

Which Task Modules Exist?#

The real source includes these module folders under core/builder/modules:

• broken_bridge_repair
• building_wall
• object_placement
• pipe_vana_opening
• pour_concrete
• repair_electric_box
• repair_hydrants
• welding

For most server owners, config/builder.lua is enough. Only edit module files when you need deeper logic changes than route balance.

If Your Changes Do Not Apply#

Check these in order:

1. Did you edit config/main.lua or config/builder.lua in the correct place?
2. Did you edit the correct route block?
3. Did you restart 0r-builderjob after the edit?
4. Did you change step order in config/builder.lua when the real problem is inside a module implementation?