Understanding Madness Accelerant
The Madness Accelerant is a Garry's Mod entity addon that forces nearby NPCs and players to enter a panic state. It does exactly what the name implies — it radiates an area effect that drives AI characters insane. Not a visual effect. Not a decorative prop. A functional script hook you drop into any FNAW-style sandbox map and get immediate chaos. I spent about three months tweaking mine to behave consistently across different NPC types before I stopped chasing edge cases. Different games handle the madness variable differently. Some use a flat numeric value. Some use a range. Most break when you push it past certain thresholds.
How to Set Up Madness Accelerant
You need the addon installed first. Download it from the Steam Workshop by searching "Madness Accelerant" — there are a few versions floating around, and the difference between them is mostly how they handle large radii. Pick one with recent updates and decent download numbers. Older forks will fail on maps with multiple entities of the same class. Once installed, spawn it using the Q-menu under Entities. It usually appears under the Garry's Mod or Fun section depending on which version you installed. Right-click it and select the spawn option. After spawning, open the properties panel. You will see fields for range, intensity, and decay rate. Range determines how far the effect extends from the entity. Intensity controls how aggressively NPCs spiral. Decay rate is how quickly the madness resets when they move out of the radius.
Here is where most people mess up. Setting range to the maximum and intensity to max simultaneously will crash half your server within seconds. The physics tick and AI recalculation hit a wall. Keep range under 500 units and intensity at 0.6 if you are running a server with more than four NPCs in range. If it is a local test, you can push higher. I tested up to 800 range on a dedicated local build with eight Combine Soldiers before I hit the wall. Crashed solid.
Get the Full Details
Configuring for Stability
The decay setting is the most overlooked field. Left at default, NPCs will cycle through panic states rapidly as they enter and exit the radius. This causes visual jitter and erratic pathfinding. Set decay to around 0.3 for a smooth transition. NPCs will panic cleanly without constant state flipping. There is also a target filter field in some versions. Use it to specify which NPC classes the effect applies to. If you leave it empty, it affects everything — including ragdolls that shouldn't be affected and player characters who already have their own sanity systems in certain gamemodes. I ran into a bug once where my custom NPC script had no filter hook, so the Accelerant broke my entire combat mod. Took me two hours to trace it back. I solved it by wrapping the sanity variable in a conditional check that ignores the Accelerant output when the NPC is in a combat state. Not elegant, but it works.
Common Pitfalls
The biggest issue is compatibility with existing sanity systems. Maps that already implement a horror-style sanity meter — like many FMV-style or zombie survival maps — will double-process the madness variable. NPCs will enter broken states or skip straight to aggression. Check whether your map has a sanity system before dropping it in. Another problem is networking. If you host this on a server with high latency, clients will receive staggered updates of the madness state. You will see NPCs acting panicked on your end while other players see them standing still. This is not a bug in the addon. It is a network interpolation issue. The fix is reducing the broadcast interval in the entity's Lua file from 0.1 to 0.25 or 0.5 depending on your tick rate. Performance-wise, a single Accelerant running at moderate settings adds roughly 2-4ms to the NPC update loop. That is negligible. But once you stack three or four of them in the same area, you are looking at 12-18ms added, and that starts eating into framerate, especially on older hardware or lower-tick servers.
Practical Use Cases
I use it primarily for testing AI pathfinding under stress conditions. It gives me a quick way to observe how NPCs behave when their mental state collapses without scripting individual panic events. It also works fine for content creation — speed runs through horror maps with the Accelerant active generate genuinely unpredictable footage because the AI has no script to fall back on. If you are building your own map and want the Accelerant to trigger only in certain zones, the cleanest approach is using a brush entity with a trigger_multiple that spawns or despawns the Accelerant based on player position. It avoids having to manually place and remove it during testing. The addon is straightforward in concept but finicky in practice. The mechanics are simple enough that you do not need a tutorial to spawn it. The real work is in the tuning. Get the range, intensity, and decay right for your specific map, and it behaves exactly as intended. Miss one variable and you are debugging crashes instead of playing.
