Browse docs
Job Bells
Configure and place a bell
Open /jobconfig → your job → Bells. The same feature works for ordinary registered employment jobs without the Jobs Creator; it is not a gang bell system.
- Add a bell with a unique ID, label and sound.
- Place it and choose its prop/marker settings.
- Choose who receives the request and whether employee recipients must be on duty.
- Save the job. Unsaved editor changes do not change the live bell.
An unpositioned bell remains inactive. Each job supports up to 32 bells. Built-in prop choices include sky_job_deskbell and sky_job_doorbell.
| Bell settings | Purpose |
|---|---|
active, positioned, x/y/z, heading | Availability and world placement |
propModel, spawnProp, showMarker | Prop and interaction-marker presentation |
sound, volume, radius | Selected sound, volume and audible radius |
interactionDistance, cooldown | Ring distance and repeat limit |
notify, requireOnDuty, recipients | Notification policy |
recipients accepts nearby, employees or both. Nearby recipients share the caller's routing bucket. Employee delivery can reach online employees elsewhere, including another bucket; the bell's duty setting controls whether off-duty employees qualify.
Visitor and employee workflow
The visitor activates the bell at its placed location. Eligible recipients receive a request for 30 seconds:
- Y sets a waypoint to the caller's position at the time they rang.
- Enter dismisses that recipient's notification.
Personal dismissal does not dismiss everybody else's copy. Global defaults belong to Config.Bells, including enabled, keyMappings, requestCooldown and customSounds.
Sounds
Choose one of the seven built-in sounds (R1, R2, R3, A1, A2, A3, A4) or configure local OGG/WAV/MP3 files in customSounds. The custom-sound list supports up to 32 entries. Keep the audio assets in the resource location referenced by that configuration.
Personal notification placement
Players open /notifications or Tablet → Settings → Bell notification to place their own notification. This is a personal preference; it does not move world bells or change the job's recipient rules.
Other client resources can open the same preference page through OpenNotificationSettings.
Integrate another job resource
Jobs Base owns the bell runtime. Use the server bell library API when registering definitions from another resource. There is no separate RegisterJobBell Cfx export.