https://victorromeosierra.com/index.php?action=history&feed=atom&title=Player_Guide%2FReporting_a_Bug 2026-06-05T20:14:29Z Revision history for this page on the wiki MediaWiki 1.45.3 https://victorromeosierra.com/index.php?title=Player_Guide/Reporting_a_Bug&diff=270&oldid=prev 2026-05-17T21:59:47Z

<p>Player Guide import 2026-05-17 (VRSWiki repo, content/pages/)</p> <p><b>New page</b></p><div>« [[Player Guide]]<br /> <br /> If something looks wrong mid-mission -- a stuck AI, a missing menu, a CSAR pickup that won&#039;t trigger -- you can flag it without leaving DCS.<br /> <br /> <br /> : 1. Personal Menu -&gt; Report a bug.<br /> <br /> : 2. In chat you will see: &quot;Bug #XXXXXX captured. Type details in chat; report submits 120s after your last message. Stay quiet to submit as-is.&quot;<br /> <br /> : 3. Type whatever&#039;s useful: what you were doing, what happened, callsigns and times if relevant. Every message you send resets the 120-second timer, so you can keep adding context over several minutes.<br /> <br /> : 4. When you stop typing for 120 seconds straight, the report posts to the #bug-report channel on Discord and you get a confirmation in chat with a short summary.<br /> <br /> The report automatically captures your name, aircraft, position (described as &quot;3 mi NE of Aleppo airport&quot;), recent VRS log warnings and errors, mission time, module versions, and the current server git HEAD. You don&#039;t need to repeat any of that -- just describe the player-visible symptom.<br /> <br /> What it does<br /> <br /> <br /> * Captures your current state and recent in-game errors automatically.<br /> <br /> * Opens a 120-second chat window. Type any extra detail you want included, or let it time out.<br /> <br /> * Posts to the dedicated bug-report Discord channel with everything attached.<br /> <br /> When to use<br /> <br /> <br /> * Something didn&#039;t work as expected.<br /> <br /> * You got an error message in-game.<br /> <br /> * F10 menu missing a command.<br /> <br /> * AI behaving strangely.<br /> <br /> * Anything that looks off, even subtly.<br /> <br /> What to include<br /> <br /> <br /> * What you were trying to do.<br /> <br /> * What happened instead.<br /> <br /> * Roughly when (mission time is captured automatically).<br /> <br /> The more context, the faster it gets fixed.<br /> <br /> Notes<br /> <br /> <br /> * One report per pilot every 5 minutes. Trigger again inside the window and chat will tell you when you can retry.<br /> <br /> * Your chat broadcasts normally while the capture window is open -- other players can still see what you type.<br /> <br /> * Use this for things that look broken. Balance feedback and feature requests still belong in Discord.</div>

Shifty