Skip to main content
sh-progressbar displays an animated circular countdown ring at the bottom-center of the screen, giving players a clear visual indicator during timed actions such as crafting, lockpicking, or harvesting. The ring fills using a CSS conic-gradient as time elapses, a live countdown timer in seconds ticks down inside the ring, and a colored label below the ring describes the current action. When the timer reaches zero the element hides itself automatically — no cleanup code required in your script. The resource is fully standalone and exposes a single Lua export, so you can call it from any client-side script without adding a framework dependency.

​
Installation

1

Add the resource to your server

Place the sh-progressbar folder inside your server’s resources directory.
2

Start the resource in server.cfg

Open your server.cfg and add the ensure line. Place it before any scripts that call the export.
server.cfg

​
Export Reference

Trigger the progress bar from any client-side Lua script using the progressbar export:

​
Parameters

​
string
required
The action text displayed below the progress ring. Keep this short and descriptive so players immediately understand what is happening.Example: 'Picking Lock'
​
number
required
The total duration of the progress bar animation, in milliseconds. The ring fills completely over this period and then disappears.Example: 5000 (5 seconds)
​
string
required
The color applied to the progress ring and the label text. Accepts any of the following formats:

​
Usage Examples

​
Pairing With Actions

The progress bar is visual only — it does not block player input or pause script execution by itself. To prevent players from moving or acting during a timed action, add your own control-disabling logic around the export call and use a coroutine or Wait() to match the duration.
Calling the export while a progress bar is already on screen will restart the animation immediately. Add a guard flag in your script to prevent players from triggering overlapping progress bars.
Match your durationMs value and any Wait() call exactly so the bar disappears at the same moment your action resolves — a mismatch creates a confusing experience where the ring ends before or after the action completes.