Skip to content

README.md

Latest commit

 

History

History
70 lines (55 loc) · 3.54 KB

README.md

File metadata and controls

70 lines (55 loc) · 3.54 KB
Raw

Rapid Trigger for GunZ

Public GunZ guide and personal research notebook by HYPNATIQ.

Revision 2.4 direction

The public guide is dedicated to Rapid Trigger in GunZ: what RT D and RT A officially do, what each control changes inside GunZ, what good tuning may help, what poor tuning can hurt, and how to test one distance without confusing it with another.

Hanz's wider workflow remains personal and lives in the Research Notebook. It uses short notes to explain the everyday-profile goal, the separate GunZ-specific profile, mouse verification, the Wootility records, and the reasoning behind the public order.

Pages

  • index.html — Rapid Trigger behavior, immediate GunZ correlation, benefits and tradeoffs, RT D/RT A tuning, Cycle Tester, troubleshooting, the restored two-column glossary, and evidence. Colored terms open the matching quick-definition window.
  • research-notebook.html — bullet-first personal findings, two-profile reasoning, full-input workflow, Wootility records, and evidence limits inside the same header, progress, numbered rail, section banner, and mobile-navigation shell as the guide.
  • assets/rapid-trigger-cycle-tester.html — preserved interactive tester, sized to its real content height so the guide does not leave a large empty area below it.
  • assets/site.css and assets/site.js — shared presentation and behavior.
  • assets/revision-24-translations.js — current translation structure and working translations. English remains the approved source voice pending fluent review.

Public guide order

  1. Understand Rapid Trigger in plain language.
  2. Read one complete first-ON → OFF → reversal → next-ON cycle.
  3. Connect RT D and RT A to GunZ movement.
  4. Understand the benefits and costs of smaller travel.
  5. Begin from a repeatable GunZ base.
  6. Tune RT D for a deliberate OFF.
  7. Tune RT A for a deliberate next ON.
  8. Validate the result in training and PvP.
  9. Use the preserved three-profile Cycle Tester.
  10. Troubleshoot by repeated symptom, then use the glossary and evidence boundaries.

The public guide links to the Research Notebook from the left contents rail. The Research Notebook links back with its left-side Open RT for GunZ button. The existing return-to-reading control preserves the reader's place between pages. Both pages now use the same 1-to-1 navigation behavior, including active-section tracking, page count, progress, Back to top, mobile contents, and colored definition windows.

Both Evidence sections restore the full approved reference set: Wooting and Gateron documentation, Wooting and Optimum keyboard videos, and GunZ Academy movement guides. The labels keep keyboard behavior, GunZ movement, and Hanz's own testing separate.

Evidence boundary

  • Manufacturer sources explain Hall-effect and Rapid Trigger control behavior.
  • GunZ application, tuning order, symptom model, and pass conditions are a personal testing method that readers may adapt.
  • The profile values shown are recorded comparisons, not universal presets.
  • Personal mouse values are intentionally absent. The notebook explains the check without publishing Hanz's numbers.
  • Local translation drafts still require fluent and regional review.

GitHub Pages

The repository is a static site. .nojekyll keeps GitHub Pages from processing the files through Jekyll. Both pages use relative links and work locally or at https://gunzinputlab.github.io/ after deployment.

Nothing in Revision 2.4 should be described as live until the source is committed, pushed, GitHub Pages finishes, and the live domain is checked.