gunzinputlab.github.io/research-notebook.html at main · GunzInputLab/gunzinputlab.github.io · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
<!doctype html>
<html lang="en" data-theme="dark">
<head>
  <meta charset="utf-8">
  <meta name="viewport" content="width=device-width, initial-scale=1">
  <link rel="canonical" href="https://gunzinputlab.github.io/research-notebook.html">
  <meta name="description" content="Research history, evidence boundaries, and the revised complete input tuning protocol for GunZ: The Duel.">
  <meta name="theme-color" content="#05080d">
  <meta name="author" content="HYPNATIQ">
  <link rel="icon" href="assets/notebook-favicon.png" type="image/png">
  <link rel="stylesheet" href="assets/site.css">
  <title>Rapid Trigger for GunZ — Research Notebook</title>
</head>
<body>
  <a class="skip-link" href="#notebook" data-i18n="skipNotebook">Skip to the research</a>
  <header class="site-header" id="top">
    <div class="header-inner">
      <a class="brand" href="index.html"><img src="assets/notebook-favicon.png" alt=""><span class="brand-copy"><strong data-i18n="notebookBrand">Research Notebook</strong><span>Rapid Trigger for GunZ · HYPNATIQ</span></span></a>
      <nav class="top-nav" id="topNav" aria-label="Primary navigation"><a href="index.html" data-i18n="publicGuide">Public guide</a><a href="#conclusion" data-i18n="nbConclusion">Conclusion</a><a href="#protocol" data-i18n="nbProtocol">Protocol</a><a href="#history" data-i18n="nbHistory">History</a><a href="#limits" data-i18n="nbLimits">Evidence</a></nav>
      <div class="header-tools">
        <div class="language-wrap"><label class="sr-only" for="languageSelect" data-i18n="languageLabel">Language</label><select class="language-select" id="languageSelect" aria-label="Language"><option value="en">English</option><option value="es">Español</option><option value="es-PE">Español (Perú)</option><option value="pt-BR">Português (Brasil)</option><option value="es-VE">Español (Venezuela)</option><option value="ko">한국어</option><option value="ja">日本語</option><option value="zh-CN">简体中文</option></select></div>
        <button class="icon-button" id="themeToggle" type="button" aria-label="Switch to light mode">◐</button><button class="icon-button menu-button" id="menuToggle" type="button" aria-label="Open navigation" aria-expanded="false">≡</button>
      </div>
    </div>
  </header>

  <main id="notebook">
    <div class="page-shell">
      <section class="hero notebook-hero">
        <div><span class="eyebrow" data-i18n="nbEye">Research Revision 2.2 · September 2026</span><h1 data-i18n-html="nbTitle">The keyboard was<br><span>only half the test.</span></h1><p class="hero-lead" data-i18n="nbLead">This notebook explains why the method changed, what each stage isolates, and what a passing result actually proves.</p><div class="hero-actions"><a class="button primary" href="index.html" data-i18n="openPublicMethod">Open the public method</a><button class="button no-print" type="button" id="printNotebook" data-i18n="printNotebook">Print / save as PDF</button></div><span class="revision-stamp" data-i18n="revisionStamp">Current revision · mouse verification before keyboard validation</span></div>
        <aside class="method-map"><div class="method-map-head" data-i18n="researchFinding">Primary research finding</div><div class="research-summary"><ul class="brief-list"><li data-i18n="finding1">Clean keyboard movement proves execution—not target coverage.</li><li data-i18n="finding2">Incorrect sensitivity can look like a Rapid Trigger pacing problem.</li><li data-i18n="finding3">Typing-safe actuation must be established before Rapid Trigger compensates for repeated movement.</li></ul><div class="callout good" data-i18n-html="findingRule"><strong>Revised rule:</strong> verify the mouse first, tune keyboard movement second, and validate the pair last.</div></div></aside>
      </section>

      <div class="notebook-layout">
        <aside class="notebook-nav" aria-label="Notebook sections"><div class="notebook-nav-title" data-i18n="contents">Notebook contents</div><a href="#conclusion"><span>01</span><b data-i18n="n1">Conclusion first</b></a><a href="#trigger"><span>02</span><b data-i18n="n2">What changed the method</b></a><a href="#model"><span>03</span><b data-i18n="n3">Revised variable model</b></a><a href="#protocol"><span>04</span><b data-i18n="n4">Mouse verification</b></a><a href="#typing-note"><span>05</span><b data-i18n="n5">Typing baseline</b></a><a href="#rapid-trigger"><span>06</span><b data-i18n="n6">Rapid Trigger protocol</b></a><a href="#combined"><span>07</span><b data-i18n="n7">Combined validation</b></a><a href="#profiles"><span>08</span><b data-i18n="n8">Profiles and checkpoints</b></a><a href="#history"><span>09</span><b data-i18n="n9">History retained</b></a><a href="#test-log"><span>10</span><b data-i18n="n10">Troubleshooting and test log</b></a><a href="#glossary"><span>11</span><b data-i18n="n11">Glossary</b></a><a href="#limits"><span>12</span><b data-i18n="n12">Evidence and limits</b></a></aside>

        <div>
          <section class="entry" id="conclusion">
            <header class="entry-head"><span class="entry-no">01</span><div><h2 data-i18n="c1Title">Conclusion first</h2><span class="entry-date" data-i18n="c1Date">Current interpretation · September 2026</span></div></header>
            <ul class="brief-list conclusion-list"><li data-i18n="c1Point1">The original research correctly separated actuation, RT D, and RT A.</li><li data-i18n="c1Point2">It did not verify mouse coverage early enough.</li><li data-i18n="c1Point3">That allowed a passing keyboard profile and an incorrect sensitivity to appear as one keyboard problem.</li></ul>
            <div class="reader-bridge compact" aria-labelledby="notebookReaderTitle">
              <h3 id="notebookReaderTitle" data-i18n="notebookReaderTitle">How to read these notes</h3>
              <div class="reader-grid">
                <article><b data-i18n="lensReader">First-time reader</b><p data-i18n="notebookReaderP">Read the conclusion and variable model first. They define the dependency order before the history introduces older numbers.</p></article>
                <article><b data-i18n="lensNewPlayer">New GunZ player</b><p data-i18n="notebookNewPlayerP">Treat movement names as test examples. You only need one familiar sequence before the input method becomes useful.</p></article>
                <article><b data-i18n="lensVeteran">Veteran GunZ player</b><p data-i18n="notebookVeteranP">Use the symptom-to-variable logic and checkpoints. The historical server results document my path, not your required destination.</p></article>
                <article><b data-i18n="lensKeyboard">Keyboard enthusiast</b><p data-i18n="notebookKeyboardP">Separate switch behavior from game application: actuation, RT D, and RT A describe input events; GunZ movement describes the test context.</p></article>
              </div>
            </div>
            <div class="note-block"><h3 data-i18n="c1H">The final dependency order</h3><div class="flow-strip"><div class="flow-node"><b>01</b><span data-i18n="flow1">Environment</span><small data-i18n="flow1s">Make the test repeatable</small></div><div class="flow-node"><b>02</b><span data-i18n="flow2">DPI + view</span><small data-i18n="flow2s">Match what you actually use</small></div><div class="flow-node"><b>03</b><span data-i18n="flow3">Base sens</span><small data-i18n="flow3s">Track while standing still</small></div><div class="flow-node"><b>04</b><span data-i18n="flow4">Actuation</span><small data-i18n="flow4s">Keep normal typing fluent</small></div><div class="flow-node"><b>05</b><span data-i18n="flow5">Rapid Trigger</span><small data-i18n="flow5s">Make movement repeatable</small></div><div class="flow-node"><b>06</b><span data-i18n="flow6">PvP</span><small data-i18n="flow6s">Verify the pair together</small></div></div></div>
          </section>

          <section class="entry" id="trigger">
            <header class="entry-head"><span class="entry-no">02</span><div><h2 data-i18n="c2Title">What changed the method</h2><span class="entry-date" data-i18n="c2Date">Real-world typing failure</span></div></header>
            <div class="evidence-bullets"><div><b data-i18n="observed">Observed</b><ul><li data-i18n="c2Observed1">0.60 mm caused too many errors during a real interview.</li><li data-i18n="c2Observed2">The setting did not preserve my normal typing fluency.</li></ul></div><div><b data-i18n="changed">Changed</b><ul><li data-i18n="c2Changed1">Regular keys returned to 1.50 mm to mirror my MCHOSE work keyboard.</li><li data-i18n="c2Changed2">Rapid Trigger stays off in the untouched typing profile.</li></ul></div><div><b data-i18n="meaning">Meaning</b><ul><li data-i18n="c2Meaning1">The keyboard must remain dependable for work, writing, and GunZ.</li><li data-i18n="c2Meaning2">The GunZ profile starts from the typing-safe baseline and adds RT only where movement needs it.</li></ul></div></div>
            <div class="callout" data-i18n-html="c2Rule"><strong>Changed question:</strong> not “How fast can I make the keyboard?” but “What is the shallowest actuation that preserves my normal typing, and how can Rapid Trigger help where that actuation falls short in GunZ?”</div>
          </section>

          <section class="entry" id="model">
            <header class="entry-head"><span class="entry-no">03</span><div><h2 data-i18n="c3Title">Revised variable model</h2><span class="entry-date" data-i18n="c3Date">One job per control</span></div></header>
            <div class="grid-2">
              <article class="note-block"><h3 data-i18n="modelView">View environment</h3><p data-i18n="modelViewP">Resolution, aspect ratio, FOV, camera distance, and crosshair define what the same motion looks like. They are controlled conditions, not tuning leftovers.</p></article>
              <article class="note-block"><h3 data-i18n="modelMouse">DPI + sensitivity</h3><p data-i18n="modelMouseP">DPI is the hardware count density. GunZ sensitivity scales it in the game. Cm/360 records the physical result. Together they determine whether the mouse can cover and place the target.</p></article>
              <article class="note-block"><h3 data-i18n="modelAct">Actuation</h3><p data-i18n="modelActP">The first ON from the released top. It must remain deliberate and fluent during normal typing before gaming adjustments begin.</p></article>
              <article class="note-block"><h3 data-i18n="modelRtd">RT D · release</h3><p data-i18n="modelRtdP">The upward distance required before OFF. It is adjusted when later releases repeatedly fail—not simply because an opponent is fast.</p></article>
              <article class="note-block"><h3 data-i18n="modelRta">RT A · reactivation</h3><p data-i18n="modelRtaP">The downward distance after reversal before the next ON. It is adjusted when movement is clean but repeatedly behind the pace.</p></article>
              <article class="note-block"><h3 data-i18n="modelPvp">PvP result</h3><p data-i18n="modelPvpP">The final system check. The movement must stay executable while the verified mouse keeps and places the opponent.</p></article>
            </div>
          </section>

          <section class="entry" id="protocol">
            <header class="entry-head"><span class="entry-no">04</span><div><h2 data-i18n="c4Title">Mouse verification protocol</h2><span class="entry-date" data-i18n="c4Date">Required before keyboard tuning</span></div></header>
            <div class="protocol-brief"><div><b data-i18n="protocolWhat">What this isolates</b><span data-i18n="mouseIsolates">Mouse coverage and aim distance without keyboard movement.</span></div><div><b data-i18n="protocolWhy">Why it comes first</b><span data-i18n="mouseWhyFirst">A keyboard cannot fix an opponent leaving the usable view.</span></div><div><b data-i18n="protocolPass">Passing evidence</b><span data-i18n="mousePassEvidence">Targets stay visible and tracking does not repeat one over- or undershoot direction.</span></div></div>
            <ol class="number-list"><li data-i18n="mp1">Choose one familiar hardware DPI and disable accidental DPI switching.</li><li data-i18n="mp2">Load your real GunZ resolution, aspect ratio, FOV, and camera settings.</li><li data-i18n="mp3">Stand still. Track moving players with the mouse only; do not judge keyboard timing yet.</li><li data-i18n="mp4">Measure the result in cm/360 with Mouse-Sensitivity.com or a physical 360° test.</li><li data-i18n="mp5">Work in 0.1 cm steps. Lower cm/360 is faster; higher cm/360 is slower.</li><li data-i18n="mp6">Freeze the first value that repeatedly keeps targets in view without repeated over- or undershoot.</li></ol>
            <div class="note-block"><h3 data-i18n="c4H">What eDPI can and cannot do</h3><span class="formula"><span data-i18n="formulaGunZEdpi">eDPI = DPI × GunZ sensitivity</span><br><span data-i18n="formulaGunZNewSens">equivalent GunZ sensitivity = eDPI ÷ new DPI</span></span><p data-i18n="c4P">This transfers a value between DPIs inside the same GunZ input setup. It does not guarantee the same feel across different games, FOV models, acceleration states, clients, or input APIs. Cm/360 is the physical verification.</p></div>
          </section>

          <section class="entry" id="typing-note">
            <header class="entry-head"><span class="entry-no">05</span><div><h2 data-i18n="c5Title">Typing baseline protocol</h2><span class="entry-date" data-i18n="c5Date">Rapid Trigger off</span></div></header>
            <div class="protocol-brief"><div><b data-i18n="protocolWhat">What this isolates</b><span data-i18n="typingIsolates">First-press sensitivity with Rapid Trigger disabled.</span></div><div><b data-i18n="protocolWhy">Why it comes first</b><span data-i18n="typingWhyFirst">Rapid Trigger should not hide an actuation value that harms normal use.</span></div><div><b data-i18n="protocolPass">Passing evidence</b><span data-i18n="typingPassEvidence">WPM, accuracy, and real-writing fluency remain near the normal range.</span></div></div>
            <ul class="brief-list"><li data-i18n="typingStep1">Run several familiar Monkeytype tests after warming up.</li><li data-i18n="typingStep2">Watch mistakes and corrections—not only the fastest WPM result.</li><li data-i18n="typingStep3">Confirm the same value in email, chat, editing, and real work.</li><li data-i18n="typingStep4">Save the shallowest passing value as the untouched typing profile.</li></ul>
            <div class="record-grid"><div class="record-item"><span data-i18n="profile">Profile</span><strong data-i18n="typing">Typing</strong><small data-i18n="baselineUntouched">Saved and left untouched</small></div><div class="record-item"><span data-i18n="regularKeys">Regular keys</span><strong>1.50 mm</strong><small data-i18n="personalCurrent">Current personal result</small></div><div class="record-item"><span data-i18n="spacebar">Spacebar</span><strong>0.80 mm</strong><small data-i18n="separateKey">Personal separate-key value</small></div><div class="record-item"><span>Rapid Trigger</span><strong>OFF</strong><small data-i18n="typingMode">Typing mode</small></div><div class="record-item"><span data-i18n="passCondition">Pass condition</span><strong data-i18n="normalFluency">Normal fluency</strong><small data-i18n="repeatTests">Repeated tests + real work</small></div></div>
          </section>

          <section class="entry" id="rapid-trigger">
            <header class="entry-head"><span class="entry-no">06</span><div><h2 data-i18n="c6Title">Rapid Trigger protocol</h2><span class="entry-date" data-i18n="c6Date">Keyboard movement only</span></div></header>
            <div class="protocol-brief"><div><b data-i18n="protocolWhat">What this isolates</b><span data-i18n="rtIsolates">Release-to-OFF and reactivation-to-ON during repeated movement.</span></div><div><b data-i18n="protocolWhy">Why it comes here</b><span data-i18n="rtWhyHere">The mouse, view, and typing-safe first press are already controlled.</span></div><div><b data-i18n="protocolPass">Passing evidence</b><span data-i18n="rtPassEvidence">One familiar sequence repeats cleanly without one recurring failure.</span></div></div>
            <ul class="brief-list"><li data-i18n="rtStep1">Duplicate the typing-safe base; never overwrite it.</li><li data-i18n="rtStep2">Enable Rapid Trigger only on keys that need repeated inputs.</li><li data-i18n="rtStep3">Establish an RT D release you can clearly clear and keep it fixed.</li><li data-i18n="rtStep4">Start RT A conservatively and lower it one small step only when clean movement repeatedly falls behind.</li></ul>
            <div class="cycle"><div class="cycle-step actuation"><b>01</b><strong data-i18n="cycle1">First ON</strong><small data-i18n="cycle1s">Fixed actuation from the released top.</small></div><div class="cycle-step"><b>02</b><strong data-i18n="cycle2">Continue down</strong><small data-i18n="cycle2s">The key stays ON toward bottom-out.</small></div><div class="cycle-step rt-d"><b>03 · RT D</b><strong data-i18n="cycle3">Release to OFF</strong><small data-i18n="cycle3s">Upward distance required before the key turns OFF.</small></div><div class="cycle-step"><b>04</b><strong data-i18n="cycle4">Reverse</strong><small data-i18n="cycle4s">Your finger stops rising and starts pressing again.</small></div><div class="cycle-step rt-a"><b>05 · RT A</b><strong data-i18n="cycle5">Next ON</strong><small data-i18n="cycle5s">Downward distance after reversal before reactivation.</small></div></div>
            <div class="callout warning" data-i18n-html="c6Warn"><strong>Diagnostic rule:</strong> RT A is the first pacing adjustment. RT D changes only when release clearance is the repeated failure. The labels may differ on other keyboards, so match the direction and event—not just the vendor’s name.</div>
          </section>

          <section class="entry" id="combined">
            <header class="entry-head"><span class="entry-no">07</span><div><h2 data-i18n="c7Title">Combined PvP validation</h2><span class="entry-date" data-i18n="c7Date">Two passes, never two live variables</span></div></header>
            <div class="split-test"><article class="test-lane"><span class="lane-label" data-i18n="movementPass">Pass A · Movement</span><h3 data-i18n="movementQuestion">Does the move stay clean and keep pace?</h3><p class="muted" data-i18n="movementP">Freeze DPI, cm/360, view settings, actuation, and RT D. Fight familiar opponents. If the character repeatedly arrives behind even though the sequence is clean, adjust RT A one step.</p></article><article class="test-lane"><span class="lane-label" data-i18n="aimPass">Pass B · Aim</span><h3 data-i18n="aimQuestion">Can the mouse keep and place the target?</h3><p class="muted" data-i18n="aimP">Freeze the passing keyboard. Use a visible center dot if your client has no crosshair. If opponents repeatedly leave the screen or the crosshair lands short/long, adjust cm/360 by 0.1 cm and retest.</p></article></div>
            <ul class="brief-list"><li data-i18n="combinedStep1">Run the movement pass first and keep the mouse fixed.</li><li data-i18n="combinedStep2">Freeze the passing keyboard before the aim pass.</li><li data-i18n="combinedStep3">Change RT A for repeated movement pacing; change cm/360 for repeated aim direction.</li><li data-i18n="combinedStep4">Keep the pair unchanged for several sessions before calling it preferred.</li></ul>
          </section>

          <section class="entry" id="profiles">
            <header class="entry-head"><span class="entry-no">08</span><div><h2 data-i18n="profilesTitle">Profiles and checkpoints</h2><span class="entry-date" data-i18n="profilesDate">Current starting records and historical results</span></div></header>
            <p data-i18n="profilesIntro">I keep the typing profile untouched, duplicate a GunZ base when I test, and save a server result only when it repeats. The older server profiles below were found before mouse verification became the first gate, so they remain historical keyboard checkpoints until the complete input chain is revalidated.</p>
            <div class="comparison"><table><thead><tr><th data-i18n="profile">Profile</th><th data-i18n="profileStatus">Status</th><th data-i18n="actuation">Actuation</th><th>RT A</th><th>RT D</th><th data-i18n="profileMeaning">What the record means</th></tr></thead><tbody>
              <tr><td data-i18n="typing">Typing</td><td data-i18n="statusCurrent">Current</td><td>1.50 mm</td><td>OFF</td><td>OFF</td><td data-i18n="typingRecordMeaning">Regular-key baseline that passed repeated typing and real work; spacebar remains a separate personal 0.80 mm value.</td></tr>
              <tr><td>GunZ Base</td><td data-i18n="statusStarting">Starting checkpoint</td><td>1.50 mm</td><td>1.75 mm</td><td>0.35 mm</td><td data-i18n="baseRecordMeaning">Conservative keyboard start to duplicate after the mouse and view are verified.</td></tr>
              <tr><td>iGunz</td><td data-i18n="statusHistorical">Historical</td><td>1.55 mm</td><td>0.10 mm</td><td>0.35 mm</td><td data-i18n="historicalRecordMeaning">A repeatable keyboard result from the earlier flow; not yet a complete mouse-verified result.</td></tr>
              <tr><td>FXP GunZ</td><td data-i18n="statusHistorical">Historical</td><td>1.55 mm</td><td>0.35 mm</td><td>0.35 mm</td><td data-i18n="historicalRecordMeaning">A repeatable keyboard result from the earlier flow; not yet a complete mouse-verified result.</td></tr>
              <tr><td>FGunZ</td><td data-i18n="statusHistorical">Historical</td><td>1.55 mm</td><td>1.15 mm</td><td>0.35 mm</td><td data-i18n="historicalRecordMeaning">A repeatable keyboard result from the earlier flow; not yet a complete mouse-verified result.</td></tr>
            </tbody></table></div>
            <div class="callout" data-i18n="profilesRule">The method should be reproducible; the final number does not have to match. A saved keyboard value becomes a current complete profile only after the mouse, movement, and aim passes all succeed together.</div>
          </section>

          <section class="entry" id="history">
            <header class="entry-head"><span class="entry-no">09</span><div><h2 data-i18n="c8Title">History retained, not discarded</h2><span class="entry-date" data-i18n="c8Date">Earlier results remain evidence</span></div></header>
            <p data-i18n="c8P">The earlier keyboard work remains useful because it established what each control changes. It is now archived below the final method so readers do not mistake a historical personal checkpoint for the required starting point.</p>
            <details><summary data-i18n="hist1">Original 0.20 mm WASD profile</summary><div data-i18n="hist1P">The first method pushed WASD actuation to 0.20 mm and tuned other action keys around it. It produced speed, but required a gaming-specific physical baseline that did not translate cleanly to everyday typing.</div></details>
            <details><summary data-i18n="hist2">1.75 / 0.65 first Rapid Trigger baseline</summary><div data-i18n="hist2P">With 0.20 mm WASD, RT A was lowered from 1.95 to 1.75 mm while RT D stayed at 0.65 mm. This identified a repeatable double-tap pace and clarified that reactivation and release were separate events.</div></details>
            <details><summary data-i18n="hist3">1.55 mm actuation discovery</summary><div data-i18n="hist3P">Using an approximately 3.30 mm calibrated bottom, 3.30 − 1.75 = 1.55 mm became a physical travel reference. It later passed a typing test with Rapid Trigger off. This was a valid personal result, but the newer real-world test now favors 1.50 mm for regular keys.</div></details>
            <details><summary data-i18n="hist4">Server-specific RT A checkpoints</summary><div data-i18n="hist4P">iGunz, FXP GunZ, and FGunZ produced different repeatable personal RT A values while other conditions were held still. Those results document the tuning path; they do not measure or rank server delay.</div></details>
          </section>

          <section class="entry" id="test-log">
            <header class="entry-head"><span class="entry-no">10</span><div><h2 data-i18n="testLogTitle">Troubleshooting and test log</h2><span class="entry-date" data-i18n="testLogDate">One repeated symptom, one changed variable</span></div></header>
            <ul class="brief-list"><li data-i18n="logRule1">Do not tune from one miss or one bad dash.</li><li data-i18n="logRule2">Record what stayed fixed before changing one value.</li><li data-i18n="logRule3">Look for the same result across a real session.</li><li data-i18n="logRule4">Return to the last passing checkpoint when the cause becomes unclear.</li></ul>
            <div class="comparison"><table><thead><tr><th data-i18n="symptom">Repeated symptom</th><th data-i18n="investigate">Investigate</th><th data-i18n="keepFixed">Keep fixed</th></tr></thead><tbody>
              <tr><td data-i18n="s1">Typing becomes error-prone</td><td data-i18n="actuation">Actuation</td><td data-i18n="s1f">Rapid Trigger off</td></tr>
              <tr><td data-i18n="s2">First move works; later releases fail</td><td>RT D</td><td data-i18n="s2f">Actuation, RT A, mouse</td></tr>
              <tr><td data-i18n="s3">Movement is clean but repeatedly behind</td><td>RT A</td><td data-i18n="s3f">RT D, actuation, mouse</td></tr>
              <tr><td data-i18n="s4">Movement is clean; target leaves the screen</td><td data-i18n="sensitivity">Sensitivity</td><td data-i18n="s4f">Complete keyboard profile</td></tr>
              <tr><td data-i18n="s6">One miss, one tumble, unclear cause</td><td data-i18n="checkpoint">Checkpoint</td><td data-i18n="s6f">Everything</td></tr>
            </tbody></table></div>
            <div class="note-block"><h3 data-i18n="blankLogTitle">Blank repeat-test record</h3><div class="blank-log">
              <div><b data-i18n="logCondition">Client, server, map, and test</b><span>________________________________</span></div>
              <div><b data-i18n="logHeld">What stayed fixed</b><span>________________________________</span></div>
              <div><b data-i18n="logChanged">The one value I changed</b><span>________________________________</span></div>
              <div><b data-i18n="logObserved">What repeatedly happened</b><span>________________________________</span></div>
              <div><b data-i18n="logDecision">Pass, fail, or return to checkpoint</b><span>________________________________</span></div>
            </div></div>
          </section>

          <section class="entry" id="glossary">
            <header class="entry-head"><span class="entry-no">11</span><div><h2 data-i18n="glossaryTitle">Glossary in the order it is used</h2><span class="entry-date" data-i18n="glossaryDate">Keyboard language translated into GunZ testing</span></div></header>
            <details><summary>DPI</summary><div data-i18n="glossaryDpi">The mouse sensor's count density. It is a hardware setting, not a measurement of how the game looks on screen.</div></details>
            <details><summary>cm/360</summary><div data-i18n="glossaryCm">The physical mouse distance needed to rotate the in-game view one full turn. Lower cm/360 is faster; higher cm/360 is slower.</div></details>
            <details><summary data-i18n="actuation">Actuation</summary><div data-i18n="modelActP">The first ON from the released top. It must remain deliberate and fluent during normal typing before gaming adjustments begin.</div></details>
            <details><summary data-i18n="rtdTitle">RT D · Deactivate</summary><div data-i18n="modelRtdP">The upward distance required before OFF. It is adjusted when later releases repeatedly fail—not simply because an opponent is fast.</div></details>
            <details><summary data-i18n="rtaTitle">RT A · Activate</summary><div data-i18n="modelRtaP">The downward distance after reversal before the next ON. It is adjusted when movement is clean but repeatedly behind the pace.</div></details>
            <details><summary data-i18n="checkpoint">Checkpoint</summary><div data-i18n="glossaryCheckpoint">A complete saved record of the settings and test conditions that passed. It is the rollback point before one value changes.</div></details>
            <details><summary data-i18n="gunzMovement">GunZ movement sequence</summary><div data-i18n="glossaryMovement">A repeatable in-game action such as Flash Step, PPQ, or GDHS. The site uses these as tests; it does not teach the movement itself.</div></details>
          </section>

          <section class="entry" id="limits">
            <header class="entry-head"><span class="entry-no">12</span><div><h2 data-i18n="c9Title">Evidence, limits, and next measurement</h2><span class="entry-date" data-i18n="c9Date">What is verified vs still open</span></div></header>
            <div class="comparison"><table><thead><tr><th data-i18n="evidenceType">Evidence type</th><th data-i18n="supports">Supports</th><th data-i18n="doesNot">Does not establish</th></tr></thead><tbody><tr><td data-i18n="manufacturerDocs">Manufacturer documentation</td><td data-i18n="docsSupport">Actuation and Rapid Trigger event behavior</td><td data-i18n="docsLimit">Universal GunZ settings</td></tr><tr><td data-i18n="microsoftDocs">Microsoft input documentation</td><td data-i18n="msSupport">Difference between raw and pointer-scaled input paths</td><td data-i18n="msLimit">Which path every GunZ client uses</td></tr><tr><td data-i18n="travelMath">Travel arithmetic</td><td data-i18n="mathSupport">Whether configured distances fit within calibrated travel</td><td data-i18n="mathLimit">Where the finger actually reverses</td></tr><tr><td data-i18n="personalTests">Repeated personal tests</td><td data-i18n="testSupport">The method, symptoms, and saved checkpoints reported here</td><td data-i18n="testLimit">A universal preset or measured server latency</td></tr></tbody></table></div>
            <div class="callout" data-i18n-html="nextMeasurement"><strong>Open measurement:</strong> the current cm/360 remains intentionally blank until the 850 DPI GunZ setup is re-measured through the revised standing-tracking and physical-turn protocol. The historical 5250 sensitivity is a starting record, not the final verified mouse result.</div>
            <div class="inline-links"><a href="https://www.mouse-sensitivity.com/" target="_blank" rel="noopener">Mouse-Sensitivity.com ↗</a><a href="https://monkeytype.com/" target="_blank" rel="noopener">Monkeytype ↗</a><a href="https://help.wooting.io/article/102-how-to-set-up-rapid-trigger" target="_blank" rel="noopener">Wooting Rapid Trigger ↗</a><a href="https://learn.microsoft.com/en-us/windows/win32/dxtecharts/taking-advantage-of-high-dpi-mouse-movement" target="_blank" rel="noopener">Microsoft mouse input ↗</a><a href="index.html" data-i18n="returnGuide">Return to the public guide →</a></div>
          </section>
        </div>
      </div>
    </div>
  </main>
  <footer class="site-footer"><div class="page-shell footer-inner"><span data-i18n="nbFooter">Rapid Trigger for GunZ · Research Revision 2.1 · HYPNATIQ</span><a href="#top" data-i18n="backTop">Back to top ↑</a></div></footer>
  <script src="assets/translations.js"></script>
  <script src="assets/revision-22-translations.js"></script>
  <script src="assets/site.js"></script>
</body>
</html>