Density Control
make the world follow your rules.
ra_density centralizes population, traffic, ambient services, dispatch, emergency behavior, scenarios, cleanup and routing-bucket population in one configurable resource. Instead of accepting a fixed preset, server owners decide which background systems remain active, which are reduced and which are removed.
From default world behavior —
to intentional server behavior.
Default background systems continue spawning pedestrians, vehicles, services, dispatch responses and aircraft even when a server already has its own departments, events and scripted workflows. That can create duplicated activity, visual noise and scenes that behave differently from the server's intended design.
ra_density moves those systems into one clear configuration. Population groups can be tuned independently, unwanted ambient behavior can be disabled, existing population entities can be cleaned up and server-side routing buckets can receive their own population state.
Fourteen configuration areas.
One complete world-control layer.
Every major control group is separated in shared/config.lua, allowing a server owner to change one system without rebuilding the entire resource around a fixed preset.
Choose how populated the world feels
Control pedestrian and scenario-ped density independently. Population budgets can also be configured, giving the resource control over both density multipliers and the wider ped population limits used by the world.
Put ambient traffic on your terms
Tune standard vehicle density, parked vehicles and random vehicle activity separately. Vehicle population budgets and nearby vehicle generators can be controlled as part of the same configuration.
Remove background behavior that adds no value
Control random service activity, garbage trucks, boats, trains, sirens and weapon drops from ambient pedestrians. Related ambient audio flags can also be managed from the configuration.
Keep emergency activity under server control
Configure dispatch services, wanted-level behavior, ignore rules, emergency dispatch and emergency-vehicle suppression. This helps prevent default responses from competing with custom departments and scripted scenes.
The resource continues beyond simple density multipliers.
Selected vehicle scenario types and scenario groups can be disabled, specific ambient vehicle models can be suppressed and selected relationship groups can be neutralized. When density is disabled, already spawned population pedestrians and vehicles can be removed inside a configurable cleanup radius.
DENSITY Client.density — ped and vehicle density multipliers
AMBIENT Client.ambient — random services, transport, sirens and drops
AUDIO Client.audio — ambient audio flags
BUDGETS Client.budgets — ped and vehicle population budgets
DISPATCH Client.dispatch — default dispatch services
EMERGENCY Client.emergency — wanted, ignore and suppression behavior
GENERATORS Client.generators — nearby vehicle generators
SCENARIOS Client.scenarios — vehicle scenario types and groups
SUPPRESSION Client.suppression — selected ambient vehicle models
CLEANUP Client.cleanup — spawned population entities inside a radius
RELATIONSHIPS Client.relationships — selected relationship groups
ROUTING_BUCKETS Server.routingBuckets
1.0 preserves the default density level
CONFIG remains editable after installation
ra_core handles the shared foundation.
ra_density stays focused on world control.
ensure ra_density
[02] Do not rename the ra_density folder
[03] Configure the resource in shared/config.lua
[04] Disable overlapping density or world-cleanup logic in other resources
[05] Review startup and compatibility warnings in the server console
[06] Test normal population and configured routing buckets before going live
Runtime density access on the client.
Population control for routing buckets on the server.
exports.ra_density:setDensity(name, value)
exports.ra_density:resetDensity(name)
exports.ra_density:SetDensity(name, value)
exports.ra_density:DecorSet(...)
exports.ra_density:applyConfiguredBuckets()
VEHICLES moving / parked / random / generators
AMBIENT services / transport / sirens / audio / drops
EMERGENCY dispatch / wanted / ignore / vehicle suppression
WORLD scenarios / model suppression / cleanup / relationships
SERVER compatibility warnings / routing buckets
[02] Configuration file: shared/config.lua
[03] Resource folder name: ra_density
[04] Compatibility conflicts are reported, not stopped automatically
[05] Documentation: docs.redactor.studio
Keep the world systems that support your server, reduce the ones that do not and move population, traffic, dispatch, cleanup and routing-bucket behavior into one clear configuration.