r_communityservice by rumaier is the resource shown in the original preview below. The reviewed 3.3.0 source assigns a count of tasks inside a configured zone. It does not substantiate the old article’s fixed sentencing times, five job types, orange-vest system or 25% logout penalty.
Original repository and current source
Install dependencies and configure access
The manifest requires ox_lib and r_bridge. Check that your bridge version supports the framework, inventory and progress interface you use, then start those dependencies before r_communityservice. The default command is /communityservice. Cfg.AllowedJobs contains police; staff access uses the r_communityservice ACE permission. Assign it only to the intended staff group and test a normal player’s refusal.
Configure tasks rather than jail minutes
Cfg.MaxTasks defaults to 60 and Cfg.TaskTime to 10 seconds per task. Zone coordinates and radius are configurable. Walking, failed actions and interruptions mean that multiplying these values is not an exact sentence duration. The server checks assigned tasks, location, elapsed time and access, with request rate limits. These checks were read in source, not certified through gameplay.
Protect confiscated items and saved assignments
The script records assignments and confiscated inventory in core/server/tasks.json, keyed by player identifier. It attempts to return items on release and handles insufficient capacity or persistence failures. Back up this file before replacing the resource and do not overwrite active assignments with an empty copy. The resource’s assignment storage is JSON; the surrounding framework can still depend on a database.
On a separate instance, test item counts and metadata through assignment, reconnect, restart, normal completion and staff removal. Include a full inventory and a denied file write, and verify that items are neither lost nor duplicated. Review who can assign or remove another player’s tasks. This review used commit 9a95c65; it is not a complete security audit or gameplay test.