Every feature in detail

Everything here comes from RaveM 1.7.1's own README and from RaveM.dll itself. Names like HostUploadMbps are settings in BepInEx\config\com.stixsworldhd.ravem.cfg; the numbers given are their defaults.

At a glance

Killcams

When someone kills you, you watch the last seconds before your death from your killer's side, then your fall. Killcams arrived in 1.6.0, built on Ultimate Replay 3.0 (UltimateReplay.dll).

Recording

• Every soldier and vehicle goes into a rolling memory buffer that always holds exactly KILLCAM LENGTH plus the delay. While a killcam plays, recording carries on into a second buffer.
• Soldiers are recorded bone by bone from whichever body is on screen, the animated one or the ragdoll. Since 1.6.3 that's every transform the soldier mesh depends on, 21 in all (the 19 skinned bones plus the armature and the weapon parent), with the hips' position stored in full precision. Falls replay exactly through Ravenfield's own animated-to-ragdoll bone pairing.
• Aim, health and shots are recorded too. Vehicles keep their turrets' bearing and pitch and, since 1.6.1, every moving part: wheels, rotors, propellers, turrets, control surfaces and suspension. Tank tracks scroll as well.
• Recording runs 20 times a second (RECORDING RATE, 10 to 30). Soldiers beyond 800 m keep their last recorded pose (RECORD SOLDIERS WITHIN). Ravenfield stops animating AI soldiers no camera can see, so within 250 m RaveM keeps them animating while recording and a killer behind you is never frozen (KEEP ANIMATING WITHIN).

Playback

• The replay plays on ghost copies (meshes and bones only, no gameplay). The live soldiers are only hidden on your screen, and the game keeps running.
• Since 1.6.4 each new snapshot starts from the previous one, so soldiers, vehicles and the camera move steadily instead of swinging back and forth, and every tracer is drawn once.
• The camera goes through Ravenfield's own override-camera API, so the game's post-processing look stays. Cameras: KILLER'S EYES, OVER THE SHOULDER (pulled in when a wall is close) or CINEMATIC (a sweeping side view of killer and victim).
• Since 1.6.6, KILLER'S EYES is a true first-person view: the camera sits at the killer's real eyes, looks exactly where they aimed, and the killer's own body isn't drawn. It uses the game's own first-person near clip and un-zoomed field of view, so dying while aiming down sights doesn't zoom the killcam. There's no weapon model in this view (the game draws first-person weapons with a separate camera), but their shots still draw tracers. Inside an enclosed vehicle seat the killcam shows CINEMATIC instead, and the panel always names the camera actually shown.
• A slow-motion finale plays around the kill, with bullet tracers for every gun, mortar and tank shot (melee fires no projectile).
• A panel on the right shows KILLCAM, the killer, the weapon, the distance, the killer's health at the kill and the camera, with a progress bar. Since 1.6.3 it no longer covers the game mode's score bar.
• Only soldiers and vehicles within 150 m of the killer or the victim appear (SHOW SOLDIERS WITHIN). Live explosions, impacts, muzzle flashes, blood, projectiles and trails are hidden during the replay, and since 1.6.2 map fires and smoke appear only for the moments they were really there. MUTE BATTLE SOUND (on) silences the live battle, while voice chat keeps playing.
• A FINAL KILLCAM shows the match's last kill to everyone when the match ends. Backspace skips a killcam when the host allows it; Fire never skips, because Ravenfield respawns you with it, and respawning ends the killcam.

Per-mode options and auto spawn

Since 1.6.0, MODE OPTIONS is never blank: after each game mode's own options, every mode gets options of RaveM's own, 25 in four groups as of 1.7.1. They're stored per game mode, saved as that mode's options and sent to every player with the match. Each option and its default is in Step 4.

• KILLCAM (12 options): killcams on or off, their length (6 s) and start delay (1.5 s), the slow-motion finale and its speed, one camera for everyone or the player's choice, killcams for bot and vehicle kills, skipping, the final killcam, the killer's health and bullet tracers.
• SPAWNING: AUTO SPAWN (off) presses DEPLOY for you once you've been dead for AUTO SPAWN AFTER (3 s) and, with WAIT FOR THE KILLCAM, once your killcam is over. That's exactly what Ravenfield's DEPLOY button does, so the game spawns you in its next spawn wave, which comes every RESPAWN TIME and only once you've been dead for more than 6 s. Since 1.6.5, auto spawn first makes sure a spawn point your team owns is selected: yours if it's still yours, otherwise the game's own fallback, otherwise your team's point nearest to where you fell. If your team owns none, it opens the deploy screen instead. Your first loadout of the match is still your choice, and USE AUTO SPAWN in PREFERENCES opts out.
• MATCH: HALLOWEEN MODE (off) switches on Ravenfield's own Halloween match parameter. Because it changes the whole match, 1.6.0 made everyone update (network protocol 7).
• BALLISTICS (9 options, since 1.7.1): air drag, wind and bot aim, decided by the host for everyone. See Ballistics.

Spec Ops and Haunted online

In single player, Spec Ops and Haunted end when you die. Online, that let one player's death end the mission for everyone, and in Haunted the match even got stuck until the host returned to the lobby. Since 1.6.1, in online matches:

• One player's death no longer ends the mission. The fallen stay down (no respawn, no auto spawn) and watch their killcam.
• When the last player is down, the host ends the mission as a defeat through the game's normal match result. Everyone sees the final killcam of that last death, and the map and mode vote starts right away (with VOTE AT MATCH END on).
• Surviving every Haunted wave ends the same way: the vote starts, and the final killcam shows the last kill.
• The host decides the last stand, so the host needs RaveM 1.6.1 or newer. Single player is unchanged.

RaveM's own README calls Haunted by the name RaveM's code uses for it, Spook Ops.

Steam P2P netcode

RaveM carries a whole Ravenfield match between PCs over Steam's peer-to-peer network, using FishNet (version string 4.7.3 in FishNet.Runtime.dll) and RaveM's own Steam transport. Traffic goes through Steam's relay, so home routers and NAT don't get in the way. Since 1.7.0 a match can also run directly over your network instead: see LAN play.

What stays in sync

Soldiers' movement, aim, stance, firing, reloads, weapon switches and health; spawns and loadouts; deaths and who gets the kill; vehicles, from spawning and driving to seats, damage and destruction; capture points; the game mode's scores and tickets; and the victory.

Who decides what

• The host runs the match: the game mode, the scores and every bot.
• Your own soldier is driven by your PC and sent to the host 30 times a second (ClientSendRate, 5 to 60; MOVE SEND RATE in PREFERENCES).
• The host sends each player a world snapshot 20 times a second (HostSnapshotRate), and flags, scores and match timers 4 times a second (GameStateRate). A vehicle's driver sends its position 20 times a second (VehicleSendRate).
• FishNet runs at 60 ticks a second (TickRate).

Smooth movement

• Other soldiers are drawn 100 ms in the past, so their movement can be smoothed between snapshots (InterpolationDelayMs; SMOOTHING DELAY in PREFERENCES).
• When packets stop, a soldier keeps moving on its last known speed for up to 250 ms (ExtrapolationLimitMs; EXTRAPOLATION), which hides short lag spikes.
• A soldier more than 6 m from where the network says it is gets placed there directly instead of sliding (SnapDistance); otherwise it's pulled toward that spot smoothly (PositionCorrectionGain).
• Soldiers within 150 m update at the full snapshot rate, out to 400 m at half rate, and beyond that on every 4th snapshot (NearDistance, MidDistance, FarSnapshotDivisor). When the host's upload runs short in a big lobby, the bandwidth budget decides instead.

Joining, loading and versions

• Join in progress: a late joiner loads the current map, receives every soldier, vehicle, flag, score and the match clock, then spawns normally.
• Starting together: everyone loads the map, and the match starts for all once every player has loaded, or after 120 s (LoadTimeoutSeconds).
• Version check: each lobby carries its network protocol (8 for RaveM 1.7.1). A player on another protocol is refused with a clear version message, and the server browser marks the lobby VERSION.
• Pausing doesn't freeze time online. If the host quits, the match ends for everyone.

LAN play

Since 1.7.0, RaveM games can run directly over your network (UDP), with no Steam lobby, no Steam relay and no internet connection. Only the transport underneath changes: lobbies, voting, READY, voice chat, killcams, auto spawn, join in progress, passwords, bans, kicks and every game mode work the same.

Hosting and joining

• Host with VISIBILITY set to LAN (NO STEAM LOBBY). The game listens on UDP port 48780 (LanPort, 1024 to 65535; every player needs the same port), and the lobby's LAN ADDRESS button, in place of INVITE FRIENDS, shows this PC's addresses.
• The first time, Windows may ask whether to allow Ravenfield through its firewall: allow it on private networks, or no one can join. If the prompt never appears, allow Ravenfield or UDP 48780 yourself.
• The server browser lists LAN games next to Steam lobbies, marked [LAN] with their ping. While it's open it probes every 3 seconds; hosts silent for 12 s disappear.
• Each probe goes out four ways: as a broadcast, as a broadcast on the subnet of every network adapter (virtual-LAN adapters such as ZeroTier, Hamachi or Radmin VPN included), to this PC so a second copy of the game is found, and straight to the addresses you joined before.
• DIRECT CONNECT at the bottom of the browser joins any address: an IP, a host name, ip:port or [IPv6]:port, plus the password if there is one. The last 8 addresses are remembered (LanRecent) and probed directly from then on. It also works over the internet to a host whose UDP port is forwarded, or across any VPN.

What LAN play still needs

• The Steam client must be running, but offline mode is enough: your Steam ID and name identify you, and voice chat uses Steam's voice codec, with the audio travelling over the LAN connection.
• Workshop downloads still need Steam online; without the map, the lobby shows GET THE MAP FIRST as usual.
• LAN games need RaveM 1.7.0 or newer on every PC, and 1.7.1's network protocol 8 means every PC needs 1.7.1 anyway.

Under the hood

• LAN games use LiteNetLib, the UDP library inside the FishNet already bundled with RaveM (the one FishNet's own Tugboat transport uses), built the same way Tugboat builds it.
• Reliable traffic is sent reliable-ordered and unreliable traffic unreliable, as over Steam; an unreliable packet larger than the connection's current packet size is sent reliably instead of being dropped.
• Ping is the round trip, as over Steam, and the network stats panel shows the transport and the measured packet loss.
• A connection is refused before it forms unless it carries RaveM's key, the same protocol and a Steam ID the host hasn't banned, and the player sees the exact reason.
• Discovery answers fit in one small datagram (99 bytes typical, never more than 1,000), and a host answers each sender at most 5 times a second.
• IPv4 is the default (LanIPv6 off); a LAN connection counts as lost after 10 s without a packet (LanTimeoutSeconds, 3 to 60).

Bots in online matches

Online matches have bots, just like Instant Action. The host's PC runs them with Ravenfield's own AI, and RaveM mirrors each one to every player.

• The host sets EAGLE BOTS and RAVEN BOTS on HOST GAME > GENERAL. New lobbies start at 20 per team (DefaultBotsPerTeam, 0 to 100).
• BOT SKILL can set every bot to beginner, normal or veteran; VANILLA MIX keeps Ravenfield's own mix.
• With ballistics on, bots work out the arc for weapons with bullet drop and lead moving targets (see Ballistics).
• Because the host's PC runs every bot and moves every player's soldier, a busy lobby needs a capable host PC as well as a fast upload.

Up to 250 players

A lobby holds up to 250 players, the most Steam allows in one lobby. Raising the number wasn't enough on its own: without a budget, 250 players and 40 bots would need about 40 MB/s of host upload. So RaveM shares out the host's upload.

The bandwidth budget

• Each player's share is HostUploadMbps (25 Mbit/s) divided by the number of players, capped at PlayerSnapshotKBps (128 KB/s).
• Each share is filled with the most important updates first: nearby soldiers and vehicles, far ones less often. Nobody is starved: every player gets at least 2 KB/s.
• Steam's own measurement of each connection counts too. RaveM stays under 80 % of Steam's estimated send rate, and halves a player's share while Steam reports a backlog.
• Vehicles share the same budget and are never sent back to their own driver.

Figures from RaveM's own budget formula. Each soldier update costs 30 bytes. In RaveM's scheduler test with 250 players and 40 bots on the default 25 Mbit/s, nearby soldiers updated 3.7 times a second, mid-range 1.8 and far 0.89, never over budget. Four times the upload gives about four times the rate.

Small messages, screens that scale

• Joins, leaves and team, READY and loading changes send one player's record (about 35 bytes) instead of the whole lobby. Pings go out in a batch of 6 bytes per player every 2 s, every 5 s in large lobbies.
• Scores, tickets and flags keep their rate up to 64 players, then scale down to at least once a second. Vote updates are spaced 0.2 s to 1 s apart, depending on lobby size.
• A joining player gets the smallest free player id, so ids never collide, even in long, busy sessions.
• Hold P: above 24 players the list goes full screen with up to 6 columns. The lobby's team lists only rebuild when someone joins, leaves or changes team or READY.

Fair hits: lag-compensated checks

Players report their own hits, so RaveM doesn't simply trust them: the host re-checks every hit before it counts (EnableHitValidation, on).

• Rewind: the host rewinds soldiers up to 400 ms back in time when checking a hit, so players with a high ping are treated fairly (LagCompensationWindowMs, 50 to 1000).
• Line of sight: SensorToolkit 2 ray sensors check that nothing solid was in the way, using the game's own sight layers, 0 and 23 (LineOfSightMask).
• Position: the hit must be within 3.5 m of where the target actually was (HitTolerance).
• Limits: at most 40 hits per second per player (MaxHitsPerSecond), at most 3 times the weapon's damage in a single hit (MaxDamagePerHitMultiplier), and nothing from beyond 2,500 m (MaxWeaponRange).
• Rejected hits count as violations for the anti-cheat.

Weapon mods with huge damage multipliers, miniguns or very long range? Raise the matching limit rather than switching validation off.

Ballistics: drag, wind, smarter bots

Projectile Factory adds air drag and wind to fast projectiles and gives bots a ballistic solver. Since 1.7.1 the host sets all of it per game mode in HOST GAME > MODE OPTIONS > BALLISTICS, and every PC in the match applies the host's rules. Every default equals the settings file's old default, so a game mode the host never touches plays exactly as before.

• Why the host decides: in a RaveM match the shooter's PC decides whether a shot hits and reports it to the host. Until 1.7.1 each player's own settings shaped their own bullets, so a player with ballistics switched off shot perfectly straight while everyone else fought drag and wind.
• Air drag: fast projectiles, anything above 120 m/s (bullets, not thrown objects), slow down over distance: each frame their speed is scaled by 1 − k × speed × frame time, never below 0.2. AIR DRAG 1.0x is k = 0.00012 per metre, adjustable from 0 to 5x; OFF gives vanilla projectiles.
• Wind: a 0.8 m/s crosswind toward 45 degrees with 35 % gusts. Since 1.7.1 the gusts follow FishNet's network tick, which every client keeps on the host's, so everyone feels the same gust at the same moment, including players who join mid-match. At long range, aim into the wind.
• Smarter bots: bots solve the ballistic arc for weapons with bullet drop, so they lob grenades and rockets and snipe with the right elevation (BOT AIM SKILL 85 %), and they lead moving targets by the projectile's travel time. These act on the host, where the bots run.
• Offline: in Instant Action and Campaign, with ApplyInSinglePlayer on, the settings file's section 5 still applies, as before: AirDragCoefficient 0.00012, DragMinSpeed 120, WindStrength 0.8, WindDirectionDegrees 45, WindGustiness 0.35, BotBallisticAim, BotBallisticSkill 0.85 and BotTargetLeading. Hosts who had changed these: set the same values in MODE OPTIONS > BALLISTICS.

Anti-cheat

Anti-Cheat Toolkit detectors run on every player's PC, and the host checks everything it receives (EnableAntiCheat, on).

• Speed hacks: ACTk's speed-hack detector checks the game clock every second and reports to the host after 3 suspicious readings in a row (SpeedHackInterval, SpeedHackMaxFalsePositives).
• Memory editors: ACTk flags tools that poke protected values, Cheat Engine style (ObscuredValueDetection).
• God mode: your health is mirrored in a protected value; edits that don't come from real game events are reverted and reported (HealthTamperProtection).
• Movement: the host checks every player's speed and teleports; faster than 18 m/s on foot counts as a violation (ServerMovementValidation, MaxOnFootSpeed).
• What happens: after 12 violations, counting bad hits, speed and reports, the host acts (MaxViolationsBeforeAction). The Action is Kick by default; LogOnly only writes to the log, and Ban also stores the player's SteamID in BepInEx\config\RaveM_bans.txt.

Other limits work the same way. A player's READY can change at most 6 times per 10 seconds, each player may send at most 6 chat messages per 10 seconds (AntiSpamMessagesPer10s), and the host decides who hears whom in voice chat, so a modified game can't listen in on voices the rules don't give it. ACTk's injection detector is deliberately left out: BepInEx itself injects assemblies, so it would always trigger.

READY checks and starting together

• Players press READY in the lobby; the host is always ready. A counter shows READY 3/5 and who's still missing.
• No READY for a map you can't play. If the lobby's map isn't installed or switched on, or was downloaded during this session, the button reads GET THE MAP FIRST. If the lobby switches to a map you lack while you're READY, you're un-readied automatically.
• READY resets when the match changes: map, game mode or its options, day or night, bots, bot skill, respawn, game length, ALL WEAPONS or the map cycle in use. Lobby-only changes (name, password, slots, join rules, ping limit, voice and vote rules) keep everyone's READY, and so does a lobby vote.
• REQUIRE READY holds START MATCH until everyone is READY. AUTO START WHEN READY starts the match 5 s after the last player readies; anyone un-readying or joining cancels it, and it never starts during a vote.
• After a lobby vote with START AFTER LOBBY VOTE and REQUIRE READY both on, the host tells everyone who's missing and starts 3 s after the last of them readies.
• The loading barrier re-checks every 0.25 s. Players who leave mid-load and the load time limit both release the match, and late loaders get the full match state and the start signal as they arrive.

Map and mode voting

• Three kinds of vote: in the lobby (the host's START VOTE), at the end of every match (VOTE AT MATCH END), and rock the vote during a match, which also offers KEEP PLAYING.
• On the ballot: maps, game modes, both on two ballots, or map and mode pairs on one; nominated maps first, plus RANDOM MAP and PLAY AGAIN options.
• Fair map choice: offered maps follow Ravenfield's own Instant Action map rules, so maps hidden from Instant Action never appear. LEAST PLAYED and SKIP RECENT MAPS use the host's play history in RaveM_VoteStats.txt (plays per map and the last 12 maps).
• Missing maps: every player's game checks the offered maps and reports the ones it lacks. Each option shows how many players are missing it, and with ONLY MAPS ALL HAVE those options can't win.
• Checked by the host: every vote must be a valid option, a permitted change and, in a runoff, on the runoff ballot. A player who leaves loses their vote, rock-the-vote request and nominations; a player who joins mid-vote can vote straight away.
• Ties and silence: a runoff re-votes only the tied ballot; the other ballot's result stays locked. A vote with no votes at all isn't a tie: the next map in the host's MAP CYCLE wins (how that works).
• Vote on the lobby's VOTE tab, with K in a match, or with chat commands such as !rtv and !nominate. Every rule and its default is in Step 4.

Proximity voice chat

How it sounds

• Direction: each voice comes from the talker's head (their ragdoll's head after death), panned in stereo relative to where you're listening.
• Distance: full volume up to 3 m, then a smooth fade to silence exactly at VOICE RANGE (60 m by default). Distant voices also lose treble, and voices behind you are a little quieter and darker.
• Walls and terrain: checked with the same collision layers Ravenfield uses for its own line of sight. A blocked voice is 55 % quieter and muffled to 700 Hz, and the change blends smoothly.
• Radio: 350 to 3,200 Hz with overdrive and static, plus crackle and squelch clicks. The vehicle intercom is lighter, and the dead sound duller. RADIO EFFECTS off gives clean audio.
• Crowds: a soft limiter prevents distortion, and MAX VOICES HEARD (8) plays radio, vehicle and lobby voices first, then the nearest.
• Bad connections: VOICE BUFFER (80 ms) smooths out jitter, and a voice never falls more than 300 ms behind.

Who hears whom

• The host relays every voice only to the players its rules allow (VOICE RANGE, TEAM RADIO, DEAD PLAYERS, ENEMIES HEAR YOU, LOBBY VOICE), at most 10 voices per listener, nearest first.
• Your own filters run on your PC before a voice is even decoded: HEAR ENEMIES, HEAR DEAD PLAYERS, ONLY STEAM FRIENDS and MUTE STEAM-BLOCKED (on by default).
• Mutes and each player's volume (0 to 200 %) are remembered by Steam account, so they apply again the next time you meet. The host's SILENCE mutes a player for everyone.

Talking

• Hold to talk, toggle to talk or open mic. Open mic stays open 0.4 s after you stop and also sends the moment just before it opened, so first syllables aren't cut; AUTO-SET picks its level from 4 seconds of your speech.
• KEY RELEASE DELAY (0 to 1000 ms) keeps you talking briefly after you let go, and TALK SOUNDS plays a click or beep that only you hear.
• Typing in chat never transmits. The Insert overlay adds voice KB/s sent, received and (on the host) relayed, how many are talking, and dropped chunks.

Workshop window

• Covers everything: the host's map and every Workshop mod the host is running, whether weapons, vehicles, skins, mutators or campaigns.
• Opens when it matters: when you press JOIN (before connecting), after joining (once for each newly missing item), when you join a match in progress whose map you lack, and any time from MISSING CONTENT in the lobby.
• Live status per item: what it provides (CURRENT MAP, MAP CYCLE, MAP, WEAPONS, VEHICLES, SKINS, MUTATORS or CAMPAIGN), its Workshop address, and whether it's not installed, subscribed, downloading, needs an update, downloaded, installed but turned off, or not on the Workshop at all.
• One-click fixes: GET subscribes and downloads at high priority (Steam suspends other Workshop downloads for it), UPDATE re-downloads an outdated copy, TURN ON switches on a mod you'd turned off, and GET ALL takes everything, current map first. OPEN PAGE and COPY LINK lead to the Workshop page.
• One restart: Ravenfield registers maps and loads weapons, vehicles, skins and mutators only when it starts, so after downloading you restart once and join again.
• The server list carries as many of the host's Workshop mods as fit in Steam's 8,191-byte limit (129 long titles fitted in RaveM's test); the rest are checked right after you join. Mods that aren't on the Workshop are named, but can't be linked or checked.

Your controls stay yours

• The chat and overlay defaults, U, J, hold P and Insert, appear in none of Ravenfield's keyboard presets and are never read by its code. (Older RaveM defaults, T, Tab, F10 and Y, each clashed with something in the game.)
• Every RaveM key, voice and killcam keys included, is compared with your Ravenfield bindings when the menu loads and whenever you save new controls in Ravenfield's options. Any key that clashes moves to the next free one, with a message on screen and in the log.
• Rebinding a RaveM key in PREFERENCES refuses keys Ravenfield uses, and names the game action that owns them.
• While you type in chat the game ignores the keyboard: every game control reads as zero, and in all 35 places where Ravenfield reads keys directly (among them the pause menu, map key triggers, Ravenscript mods, the spectator camera and dialogs) RaveM makes those reads skip your typing.

Text chat

• Chat to everyone or your team, in lobbies and matches, built on Ultimate Chat Box. If that can't start, RaveM falls back to a chat of its own.
• The chat stays hidden until you press a chat key, and pops up for 10 s for everyone who receives a message (ChatMessagePopupSeconds, 0 to 60).
• Anti-spam: each player may send 6 messages per 10 seconds, and the host drops the rest (AntiSpamMessagesPer10s). Messages are up to 160 characters long (MaxMessageLength).
• The send key has to be one that types nothing, such as Tab, Insert or F1 to F15. Enter is optional, because it's Ravenfield's Open Loadout key.
• Vote commands go to the host and don't appear as chat; voice commands like /mute and /volume never leave your PC.
• Position (nine presets plus fine placement) and size are previewed live, and text size applies immediately.

Under the hood

• No game files change. RaveM patches Ravenfield in memory through BepInEx's Harmony; the ONLINE tile is a copy of the game's own menu tile made at runtime.
• Coroutines: every loop (snapshots, vehicles, game state, pings, anti-cheat and the UI) runs on MEC Pro. Lobby pings, anti-cheat sweeps and UI refreshes run 7 times a second (SlowUpdateHz), and the lobby and player lists refresh 5 times a second (UiRefreshHz).
• Steam: lobbies, friends, matchmaking and profiles use Multiplayer Engine Pro's Steam providers. Its other providers (Unity Netcode, PlayFab, Unity Services) can't run in Ravenfield and aren't used. Voice calls Steam's own voice API directly.
• Diagnostics: VERBOSE LOG writes detailed network and sync information to BepInEx\LogOutput.log.
• Files in BepInEx\config: the settings file, saved map cycles, the vote play history, voice volumes and mutes, and the ban list. What each one keeps.

Design limits

• If the host quits, the match ends for everyone. There's no host migration.
• Voice goes through the host, so the host's upload grows with the number of people talking at once.
• Voice is stereo, not surround: on 5.1 or 7.1 it uses the front left and right speakers. It has its own VOICE VOLUME, which Ravenfield's sliders and deafness effects don't change, and it keeps playing while the game's audio is paused.
• Players who switch VOICE CHAT off neither send nor hear voice, but the host still sends them the voice the rules allow; their PC discards it.
• Big lobbies are limited by the host's upload. At 250 players on an ordinary connection, distant soldiers update about once a second.
• Events (spawns, deaths, seat changes, chat) go to every player the moment they happen. Each is small, but the total grows with the number of players.
• Workshop content downloaded while Ravenfield runs loads only at the next start.
• Votes run on the host. Missing-map reports arrive a moment after a vote opens; until then an option can still get votes, which are removed if it becomes unavailable.
• The NOMINATE list shows the maps the nominating player has installed; the host re-checks every nomination against its own pool.
• Scripted maps may replace the voted game mode with their own, which is why SCRIPTED MAPS is off by default.
• Killcams: vehicle parts move in the replay when something moves them or scrolls their texture; anything animated purely in a shader isn't recorded, and very fast rotors can look slower than they are at RECORDING RATE.
• Looping fires and smoke are recorded once a second: a new one's start is exact when its loop lasts at least a second, otherwise up to a second late, never early. Fires and smoke that aren't particle systems aren't recorded.
• Soldiers beyond RECORD SOLDIERS WITHIN keep their last recorded pose, those farther than SHOW SOLDIERS WITHIN from both killer and victim get no ghost, and tracers come from projectile weapons only.
• In Spec Ops and Haunted online, the fallen stay down until the mission ends; the mission fails when the last player is down.
• AUTO SPAWN presses DEPLOY; the game still decides the respawn wave and uses the spawn point selected on your map.
• On LAN, identities are self-reported: Steam proves every player's Steam ID over Steam networking, but on a LAN each PC states its own, so a ban by Steam ID can be dodged there by faking one. The network stats panel says so, and a LAN password keeps strangers out.
• LAN discovery reaches only directly connected networks, because broadcasts don't cross routers. Use DIRECT CONNECT there; from then on the address is probed directly.

All settings

All 157 settings in BepInEx\config\com.stixsworldhd.ravem.cfg, read from RaveM.dll 1.7.1 itself. The menus change many of them; the rest are here for hosts and tinkerers. Edit the file with the game closed: RaveM rewrites it whenever a setting changes in game.

Defaults and ranges are as RaveM states them in each setting's description. In the file, true and false are written in lowercase, as below.