QBCore Frameworkqbcore.netCommunity docs
On this page

Updated 2026-10-13 · 5 min read

qb-smallresources

qb-smallresources combines several small gameplay behaviors in one resource. Shared values live in config.lua; client and server modules implement the behavior. Removing the entire package to disable one feature can break resources that depend on its other features.

Baseline: e69a9578. Inspect its README, manifest and config. Its manifest loads QBCore locales and PolyZone client modules. Source review does not mean the scenarios below have already been tested in FiveM.

Find the setting for your task

TaskConfiguration to inspectFollow-up check
Food, drink or alcoholConfig.ConsumablesShared item key, use registration and effect handler
Traffic and pedestriansConfig.DensityConsumer and any competing density script
AI dispatch or wanted levelsConfig.AIResponseEnabled services and other AI controllers
AFK behaviorConfig.AFKSeconds, ignored groups and character-menu behavior
Hands-up command/keyConfig.HandsUpSaved mapping and conflicting registrations
Selected HUD/controlsConfig.DisableOther resources changing the same control/state
Harness limitConfig.HarnessUsesThe module that consumes the value and inventory integration

Search for the exact config key and read its consumer before changing units, assumed defaults or execution timing. A file name is not enough evidence of which module owns an effect.

Add or repair a consumable

Start with an item the inventory can already provide. Its internal shared-item key, not its displayed label, must match the consumables table. Check whether another resource already registers a use handler for that item.

For a controlled test using the existing sandwich entry, change only that entry in the existing food table:

Config.Consumables.eat['sandwich'] = 40

Place this after Config.Consumables is defined, or edit the entry in that table; do not run it before the table exists. The value is an illustrative fixed test setting, not a recommended server economy or balance value. Record and restore the original entry afterward.

The pinned config uses expressions such as math.random(35, 54) in this table. A Lua expression in the config is evaluated when that config chunk runs; it does not by itself request a fresh random number every time a player eats. Read the consumer before describing the value as a per-use random effect.

Check the existing use registration and effect flow instead of registering a competing handler. For a genuinely new item, follow usable-item creation and define the shared item, image and behavior deliberately. This one-line configuration edit does not create an item.

Test with a controlled starting hunger value and item quantity on staging. Verify consumption, the relevant effect and any cancellation path. A capped status can make a working effect appear smaller, so compare the handler's cap/units rather than assuming a fixed observed increase from the config alone.

Adjust AFK behavior without replacing the module

The baseline groups AFK settings under Config.AFK. For an illustrative 30-minute staging policy:

Config.AFK.secondsUntilKick = 30 * 60

The config comment defines the duration in seconds, unlike many UI timers expressed in milliseconds. Apply the setting after the AFK table exists. Preserve and review ignoredGroups and kickInCharMenu instead of replacing the whole object with a one-line example.

Test with an ordinary player account: an ignored staff group is a poor test of the configured timeout. Consider login/character selection behavior separately. Restore the original timeout after the experiment. Do not shorten a populated server's timeout simply to accelerate a test.

Avoid competing resources

Density, HUD visibility, controls and vehicle behavior may also be changed by standalone resources. A second script writing the same game state can make a correctly loaded setting look ineffective.

Use a staging-only isolation sequence: record the baseline, identify the two suspected writers, disable one deliberately, repeat the same scenario, then restore it. Record which change affected the result. Do not remove unrelated dependencies or delete the full smallresources package.

The replicated UseTarget convar is shared with other resources. Changing it is an integration change, not a universal interaction repair. Check qb-target, qb-management and their actual startup order before switching modes.

Troubleshooting

SymptomCheck firstEvidence to capture
Food exists but cannot be usedExact item key, registration, inventory integrationFirst server/client error and item configuration
Item is consumed but effect differsEffect handler, units and capsStarting/ending status and quantity
Density change appears ignoredExact consumer and competing writersSame-location comparison with one writer isolated
Key or command stops respondingRegistration conflicts and saved FiveM keymappingBinding and resource startup state
Staff never times outAFK ignored groupsOrdinary account versus staff account
Character-menu AFK behavior differskickInCharMenu and current stateWhether the player has completed character selection

The keybinding guide separates configured defaults from saved player choices. Do not solve a mapping issue by deleting unrelated files or removing authorization checks.

Reward-event changes and authority

The current server consumables implementation adds an inventory check to consumables:server:AddParachute and consumables:server:resetArmor: if the corresponding parachute or heavyarmor item is already present, the handler returns before adding another. This prevents that duplicate-item case; it does not by itself prove that a legitimate use, return or armor-reset operation occurred. Review server-owned eligibility and replay handling before invoking these reward handlers from other resources.

On an isolated server, test both an existing-item and missing-item case and check inventory-full behavior. A source diff is not a successful runtime test.

Update checklist

Diff config.lua and the client/server consumers for every retained feature. On staging, test one change at a time, then the combined set: consumables, controls, vehicle behavior, weapons and density where used. Record conflicting resources and the chosen owner for each behavior.

Keep a reversible config diff and the previous resource revision. Restore only the changed entries when undoing a test, then reconnect/restart on staging as the affected module requires. Manual acceptance instructions here are not completed runtime results or performance measurements. Return to resource references for the integrations you retain.

Found an issue in this guide?

Send the page URL, the affected example, and a source or reproduction to the site maintainer. For a server or resource problem, use the support guide.

On this page

Leonida RP server website built with RPWebsite
RPWebsite

Advertisement · RPWebsite

Want a website for your server?

Launch a site with live player status, rules, and a join button in minutes.

Build your website