Fix: RTV (Rock the Vote) Not Triggering

Players type rtv and nothing happens — no vote, no chat confirmation, no error. Rock the Vote is gated by several conditions on purpose (a minimum number of players must agree, a delay after map start must pass, a map list must exist), and any one of them unmet makes the command silently do nothing. That silence is what makes it hard to debug. Here is how to find which gate is closed.

1. Confirm the plugin is loaded and named

First rule out that RTV is not running at all. In the server console:

amxx plugins

Find the RTV plugin in the list; it must read running, not bad load or absent. If it is missing, its line is not in plugins.ini; if it is bad load, a required module is missing. No running RTV plugin means rtv is an unknown command and will always do nothing.

2. Check the required ratio of voters

RTV does not start a vote on one person's request — it needs a fraction of the server to type rtv first. That threshold is a cvar, commonly a ratio like 0.60 meaning 60% of players must ask. On a server with ten players that is six requests; with two players it is two. The relevant cvar in most RTV builds:

rtv_ratio 0.60

If one player types rtv and the ratio needs six, nothing visibly happens — the plugin is silently counting. Lower the ratio for a small server, or tell players the vote needs multiple requests. A ratio the current population can never reach is the number-one reason RTV "does not work" on a quiet server.

3. Check the start delay

Most RTV plugins block voting for the first few minutes of a map so people cannot skip a map the instant it loads. If the delay cvar is high, early rtv requests are ignored:

rtv_delay 120

With rtv_delay 120, requests in the first two minutes do nothing. Either wait out the delay or lower it. This is deliberate design, not a fault — but it looks identical to a broken plugin if you are testing right after a map change.

4. Provide a map list to vote on

RTV needs a pool of maps to offer. Depending on the build it reads from its own maps.ini (often in addons/amxmodx/configs/) or falls back to mapcycle.txt. If that list is empty, missing, or lists maps the server does not have, the vote either never builds a menu or offers nothing valid. Confirm the map list file exists, is non-empty, and contains maps present in cstrike/maps/. A vote with no candidate maps cannot appear.

5. Resolve nextmap and vote conflicts

RTV usually pairs with a nextmap/vote plugin, and two plugins both trying to own the end-of-map vote can deadlock — each waiting for the other, so no vote fires. Run one coherent set: either the RTV plugin plus a matching nextmap plugin from the same suite, or a single combined plugin. Also confirm the end-of-map vote is scheduled off a non-zero mp_timelimit; a purely round-based flow (mp_timelimit 0) gives the timed vote nothing to hook onto, as explained in the map flow guide. A well-integrated admin suite like the CSB Admin Menu avoids the duplicate-vote deadlock.

Troubleshooting

• rtv is an unknown command — the plugin is not loaded. Check amxx plugins and plugins.ini.
• One player types rtv, nothing happens — the required ratio is not met; the plugin is counting silently. Lower rtv_ratio or get more requests.
• rtv ignored early in the map — rtv_delay has not elapsed. Wait or lower it.
• Vote menu is empty or never appears — the map list is missing or lists absent maps. Fix maps.ini/mapcycle.
• Vote starts but never changes map — a nextmap plugin conflict, or the winning map is not installed. Run one coherent vote set.
• End-of-map vote never fires — mp_timelimit 0. Keep a non-zero time limit as the vote's schedule.

Verification

On a test server, set rtv_ratio low and rtv_delay to a few seconds, load a map, wait out the delay, and type rtv. The plugin should acknowledge the request in chat and, once the ratio is met, open the map vote menu. Cast votes and confirm the server changes to the winning map. If the request is acknowledged and the menu appears, RTV is functioning and your live problem was one of the gates — usually the ratio being unreachable at your real population. Restore sensible values (a reasonable ratio and a short protective delay) once it works, and advertise the command in your MOTD so players know it needs several requests.