Helpers (Pulse.*)
The Pulse global gives you a set of helpers for the patterns that come up in nearly every script. These aren't magic — they're well-tested implementations of things you'd write anyway.
Before reaching for a helper, ask: "What problem am I trying to solve?" Each helper solves exactly one category of problem.
Quick reference
| Helper | Solves |
|---|---|
| Pulse.Log | Structured logging in dev builds, zero cost in production |
| Pulse.Monitor | Live key-value dashboard in the dev overlay (see bottom of Log page) |
| Pulse.Notify | In-game toast notifications for feature toggles and function events |
| Pulse.Loop | Repeating intervals with safe start/stop and error isolation |
| Pulse.Draw | Highlights, circles, and selection boxes without boilerplate |
| Pulse.Aim | FOV check, camera snap, nearest-entity search, lock-on locker |
| Pulse.Hitbox | Resize hitbox parts and restore them later |
| Pulse.Team | Friend/enemy resolver pattern |
| Pulse.Conn | Named connection manager — one live connection per name |
| Pulse.Input | Simulate key presses via VirtualInputManager / UIS |
| Pulse.Memory | Executor capability checks and safe character module resolution |
| Pulse.Perf | Rolling frame-time sampler with warn threshold |
| Pulse.Store | Cross-component reactive key-value state |
| Pulse.Cooldown | Rate limiting — per call or per entity |
| Pulse.Track | Track entities and auto-clean them up when they're gone |
| Pulse.Cache | Cache expensive calls with automatic expiry |
| Pulse.World | Safe workspace navigation |
| Pulse.Restore | Save and restore instance property values |
| Pulse.Remote | Lazy-resolved, cached RemoteEvent / RemoteFunction wrappers |
How they're injected
All helpers are compiled into your script before your components. You don't import or require them — they're available globally as Pulse.X everywhere in your code.
What the helpers don't do
- They don't know anything about your game's structure
- They don't auto-apply themselves — you call them
- They handle errors gracefully (pcall-wrapped internally) but they log warnings, not silently swallow bugs
If a helper is doing nothing, check the dev overlay logs — it's almost certainly a nil argument or wrong path.