-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathresearch-notebook.html
More file actions
261 lines (245 loc) · 26.4 KB
/
Copy pathresearch-notebook.html
File metadata and controls
261 lines (245 loc) · 26.4 KB
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
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
<!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="HYPNATIQ's concise research notes behind the Rapid Trigger for GunZ method.">
<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 class="notebook-page">
<a class="skip-link" href="#notebookMain" data-i18n="skipNotebook">Skip to the research notes</a>
<header class="site-header" id="top">
<a class="brand" href="#notebook-home" aria-label="Research Notebook home">
<img class="brand-mark" src="assets/research-logo.png" alt="">
<span><strong>Research Notebook</strong><small>Rapid Trigger for GunZ</small></span>
</a>
<div class="progress-track" aria-hidden="true"><span id="progressFill"></span></div>
<div class="header-tools">
<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>
<button class="theme-toggle" id="themeToggle" type="button" aria-label="Switch theme">Light</button>
<span class="page-indicator" id="pageIndicator">Page 01 / 11</span>
<button class="menu-button" id="menuToggle" type="button" aria-label="Open notebook contents" aria-expanded="false">☰</button>
</div>
</header>
<aside class="guide-nav notebook-guide-nav" id="notebookSidebar" aria-label="Notebook contents">
<p class="nav-title" data-i18n="notebookContents">Notebook contents</p>
<a href="#notebook-home"><span>01</span><b data-i18n="nbNavOverview">Overview</b></a>
<a href="#tldr"><span>02</span><b data-i18n="nbNavTldr">TL;DR</b></a>
<a href="#everyday"><span>03</span><b data-i18n="nbNavEveryday">Everyday profile</b></a>
<a href="#gunz-profile"><span>04</span><b data-i18n="nbNavGunz">GunZ-specific profile</b></a>
<a href="#controls"><span>05</span><b data-i18n="nbNavControls">What RT D and RT A mean</b></a>
<a href="#finding"><span>06</span><b data-i18n="nbNavFinding">What changed my thinking</b></a>
<a href="#method"><span>07</span><b data-i18n="nbNavMethod">My current method</b></a>
<a href="#screenshots"><span>08</span><b data-i18n="nbNavScreens">Wootility records</b></a>
<a href="#history"><span>09</span><b data-i18n="nbNavHistory">What I kept from V1</b></a>
<a href="#limits"><span>10</span><b data-i18n="nbNavLimits">Evidence & limits</b></a>
<a href="#help"><span>11</span><b data-i18n="nbNavHelp">Help & contact</b></a>
<a class="rail-page-link remember-position" href="index.html" data-i18n="publicGuide">Open RT for GunZ</a>
<div class="side-note">
<strong data-i18n="readColors">Read the colors.</strong>
<span class="side-note-intro" data-i18n="colorIntro">Select a colored term for a short definition without leaving your place.</span>
<div class="color-key">
<div class="color-key-item"><span class="term-link term-tech">Keyboard term</span><small>Switch motion or actuation</small></div>
<div class="color-key-item"><span class="term-link term-guide">Guide term</span><small>A practical label used here</small></div>
<div class="color-key-item"><span class="term-link term-a">RT A · Activate</span><small>Downward re-press travel</small></div>
<div class="color-key-item"><span class="term-link term-d">RT D · Deactivate</span><small>Upward release travel</small></div>
</div>
</div>
</aside>
<div class="section-banner" id="sectionBanner" aria-hidden="true">
<div class="section-banner-inner"><b id="bannerPage">Page 01</b><span id="bannerTitle">Overview</span><a href="#top">Section start ↑</a></div>
</div>
<main class="guide-main notebook-main" id="notebookMain">
<section class="hero notebook-hero tracked-section" id="notebook-home" data-page="01" data-title="Overview">
<div class="hero-inner notebook-hero-inner">
<span class="eyebrow" data-i18n="nbEye">Personal notes · Revision 2.4</span>
<h1 data-i18n-html="nbTitle">My findings.<br><span>In the order I found them.</span></h1>
<p class="lede" data-i18n="nbLead">This is the personal side of the project: what I noticed, what I changed, what happened, and what it taught me.</p>
<div class="notebook-snapshot"><strong>How to read this:</strong> the public guide explains Rapid Trigger for any GunZ player. These notes explain my process and why the guide changed.</div>
</div>
</section>
<div class="notebook-content">
<section class="notebook-entry tracked-section" id="tldr" data-page="02" data-title="TL;DR">
<header class="entry-head"><span class="entry-no">02</span><div><h2 data-i18n="nbTldrTitle">TL;DR</h2><span class="entry-date" data-i18n="nbTldrDate">The whole finding in one minute</span></div></header>
<article class="note-sheet tldr-box">
<ul class="note-list">
<li>I wanted one keyboard to stay comfortable for normal use and still feel fluent in GunZ.</li>
<li>I kept an everyday profile that still feels like a keyboard and lets me type at 100+ WPM.</li>
<li>I use Rapid Trigger to reduce the extra key travel between GunZ inputs—not to turn the keyboard into a different device.</li>
<li><button class="term-link term-d" type="button" data-term="rtd">RT D</button> reduces the upward release travel required before OFF. It does not remove all input or game delay.</li>
<li><button class="term-link term-a" type="button" data-term="rta">RT A</button> sets the downward re-press travel before the next ON. I use it to clean up the dash pace I am trying to perform.</li>
<li>I also keep a GunZ-specific profile when I want more intentional control over movement and timing.</li>
<li>I check the mouse and screen separately before blaming a clean keyboard result for an aim problem.</li>
</ul>
<p class="callout good"><strong>What I learned:</strong> keep the keyboard comfortable, let RT D clear the old input, let RT A shape the next re-press, and stop once the movement stays deliberate.</p>
</article>
</section>
<section class="notebook-entry tracked-section" id="everyday" data-page="03" data-title="Everyday profile">
<header class="entry-head"><span class="entry-no">03</span><div><h2 data-i18n="nbEverydayTitle">My everyday profile</h2><span class="entry-date" data-i18n="nbEverydayDate">Keeping my keyboard as a keyboard</span></div></header>
<article class="note-sheet">
<h3 class="note-heading">What I wanted</h3>
<ul class="note-list"><li>One profile I can trust for normal typing, work, and daily use.</li><li>Normal typing should not be sacrificed for one game.</li><li>My WPM should stay at 100+ without the keyboard feeling nervous.</li></ul>
<h3 class="note-heading">What Rapid Trigger adds for GunZ</h3>
<ul class="note-list"><li>RT D lets the active key turn OFF after a chosen amount of upward movement.</li><li>That reduces the required release travel between inputs; it does not remove every kind of delay.</li><li>RT A lets the next ON happen after a chosen amount of downward movement following reversal.</li><li>That gives me a way to clean up the pace between dashes without changing the first actuation just to chase speed.</li></ul>
<h3 class="note-heading">What it means to me</h3>
<ul class="note-list"><li>The keyboard keeps its normal everyday feel.</li><li>Rapid Trigger helps the same keyboard keep GunZ movement consistent and fluent.</li><li>I get the benefit of shorter OFF/ON travel while keeping the first press comfortable.</li></ul>
<p class="callout"><strong>My wording, fact-checked:</strong> RT D reduces required release travel. RT A reduces or increases required re-press travel. Neither setting promises a fixed time saving.</p>
</article>
</section>
<section class="notebook-entry tracked-section" id="gunz-profile" data-page="04" data-title="GunZ-specific profile">
<header class="entry-head"><span class="entry-no">04</span><div><h2 data-i18n="nbGunzTitle">My GunZ-specific profile</h2><span class="entry-date" data-i18n="nbGunzDate">A separate choice for more intentional movement</span></div></header>
<article class="note-sheet">
<h3 class="note-heading">Why I keep it</h3>
<ul class="note-list"><li>I do not always want the everyday profile to carry every GunZ experiment.</li><li>A separate copy lets me tune around movement and timing without losing the profile I trust for everything else.</li><li>It gives me a more direct, intentional feel over character movement when I choose to use it.</li></ul>
<h3 class="note-heading">The boundary</h3>
<ul class="note-list"><li>This is my personal profile decision, not a requirement for Rapid Trigger.</li><li>The public guide teaches the controls and method without asking anyone to copy my settings.</li><li>The only current configuration values recorded here are the keyboard values visible in my Wootility screenshots below.</li></ul>
</article>
</section>
<section class="notebook-entry tracked-section" id="controls" data-page="05" data-title="What RT D and RT A mean">
<header class="entry-head"><span class="entry-no">05</span><div><h2 data-i18n="nbControlsTitle">What RT D and RT A mean to me in GunZ</h2><span class="entry-date" data-i18n="nbControlsDate">Official behavior first · GunZ connection second</span></div></header>
<article class="note-sheet">
<h3 class="note-heading"><button class="term-link term-d" type="button" data-term="rtd">RT D · Deactivate</button></h3>
<ul class="note-list">
<li><strong>Official behavior:</strong> the upward distance an active key travels before the keyboard reports OFF.</li>
<li><strong>GunZ connection:</strong> how much I have to lift before the old direction or action clears.</li>
<li><strong>When it helps:</strong> the release happens with less upward travel, so the next part of my movement is not waiting on a deep reset.</li>
<li><strong>When it is too low:</strong> small pressure changes can report OFF earlier than I meant.</li>
<li><strong>When it is too high:</strong> the old input can stay active longer than my movement rhythm expects.</li>
</ul>
<h3 class="note-heading"><button class="term-link term-a" type="button" data-term="rta">RT A · Activate</button></h3>
<ul class="note-list">
<li><strong>Official behavior:</strong> the downward distance after reversal before the keyboard reports the next ON while Rapid Trigger is active.</li>
<li><strong>GunZ connection:</strong> how much I have to re-press before the next direction, dash, or repeated action begins.</li>
<li><strong>When it helps:</strong> I can match the re-press travel to the dash pace I am trying to perform.</li>
<li><strong>When it is too low:</strong> a small bounce or unfinished motion can start the next input early.</li>
<li><strong>When it is too high:</strong> the next input can feel late or fail to arrive before my finger reverses again.</li>
</ul>
<p class="callout amber"><strong>The part I had to correct:</strong> RT A does not directly set GunZ speed. It sets a re-press distance. My finger motion turns that distance into a real input pace.</p>
</article>
</section>
<section class="notebook-entry tracked-section" id="finding" data-page="06" data-title="What changed my thinking">
<header class="entry-head"><span class="entry-no">06</span><div><h2 data-i18n="nbFindingTitle">What changed my thinking</h2><span class="entry-date" data-i18n="nbFindingDate">From a gaming-only tune to a full input check</span></div></header>
<article class="note-sheet">
<h3 class="note-heading">What I saw</h3>
<ul class="note-list"><li>A very shallow actuation could feel quick in GunZ and still make normal typing harder.</li><li>A movement could become clean while my aim still landed short or long.</li><li>Changing the keyboard again could hide the aim problem instead of identifying it.</li></ul>
<h3 class="note-heading">What I changed</h3>
<ul class="note-list"><li>I stopped using “lowest possible” as the goal.</li><li>I checked that my everyday actuation still supported normal typing.</li><li>I separated keyboard movement from mouse coverage before making another keyboard change.</li></ul>
<h3 class="note-heading">What happened</h3>
<ul class="note-list"><li>The keyboard could stay comfortable while Rapid Trigger handled the extra release and re-press travel for GunZ.</li><li>I could tell whether a miss came from movement pacing or from where my aim landed.</li><li>The method became easier to repeat because each setting had one job.</li></ul>
<h3 class="note-heading">What it taught me</h3>
<ul class="note-list"><li>Clean movement comes before judging aim during movement.</li><li>A faster keyboard result is not automatically a better full-input result.</li><li>Verify the mouse before changing a keyboard setup that is already moving correctly.</li></ul>
</article>
</section>
<section class="notebook-entry tracked-section" id="method" data-page="07" data-title="My current method">
<header class="entry-head"><span class="entry-no">07</span><div><h2 data-i18n="nbMethodTitle">My current method</h2><span class="entry-date" data-i18n="nbMethodDate">The short version I can repeat</span></div></header>
<article class="note-sheet">
<ol class="steps">
<li><strong>Start with the keyboard I can live with.</strong> <span>I use typing practice to confirm that normal use still feels normal.</span></li>
<li><strong>Verify the mouse separately.</strong> <span>I check pointer control, the game view, and target tracking before I use movement to judge aim.</span></li>
<li><strong>Save a clean GunZ base.</strong> <span>I duplicate it before testing so I can always return.</span></li>
<li><strong>Tune RT D for deliberate OFF.</strong> <span>I want the old input to clear without tiny lifts cutting it off.</span></li>
<li><strong>Tune RT A for deliberate next ON.</strong> <span>I want the next dash to match my intended re-press pace.</span></li>
<li><strong>Test the move alone.</strong> <span>Training tells me whether the movement itself is clean.</span></li>
<li><strong>Test against players.</strong> <span>PvP tells me whether the result stays clean when the pace changes.</span></li>
<li><strong>Check aim only after movement is clean.</strong> <span>If aim still lands short or long, I check the mouse instead of making Rapid Trigger faster.</span></li>
<li><strong>Keep it over time.</strong> <span>I save the last repeatable result and change one cause only when a symptom repeats.</span></li>
</ol>
<p class="callout good"><strong>The order matters:</strong> comfortable keyboard → verified mouse → clean release → clean re-press → training → PvP → long-term check.</p>
</article>
</section>
<section class="notebook-entry tracked-section" id="screenshots" data-page="08" data-title="Wootility records">
<header class="entry-head"><span class="entry-no">08</span><div><h2 data-i18n="nbScreensTitle">My Wootility records</h2><span class="entry-date" data-i18n="nbScreensDate">The source of the configuration values shown here</span></div></header>
<article class="note-sheet">
<p class="note"><strong>How to read these:</strong> the profile names are personal labels. The comparison below uses regular-key values. The screenshots also show that I use separate values on some keys.</p>
<h3 class="note-heading">Standard / everyday record</h3>
<div class="settings-block">
<div class="setting-row"><span>Regular-key actuation</span><strong>1.50 mm</strong></div>
<div class="setting-row"><span>RT A · Activate</span><strong>0.30 mm</strong></div>
<div class="setting-row"><span>RT D · Deactivate</span><strong>0.15 mm</strong></div>
<div class="setting-row"><span>Visible key exceptions</span><strong>L-Shift 2.40 mm · Spacebar 0.70 mm</strong></div>
</div>
<div class="screenshot-grid">
<figure class="screenshot-card"><img src="assets/wootility-standard-actuation.png" alt="Wootility standard profile actuation screen"><figcaption>Actuation screen. Regular keys show 1.50 mm; the image also records per-key exceptions.</figcaption></figure>
<figure class="screenshot-card"><img src="assets/wootility-standard-rapid-trigger.png" alt="Wootility standard profile Rapid Trigger screen"><figcaption>Rapid Trigger screen. Split sensitivity shows 0.30 mm Activate and 0.15 mm Deactivate.</figcaption></figure>
</div>
<h3 class="note-heading">GunZ-specific record</h3>
<div class="settings-block">
<div class="setting-row"><span>Regular-key actuation</span><strong>0.60 mm</strong></div>
<div class="setting-row"><span>RT A · Activate</span><strong>0.35 mm</strong></div>
<div class="setting-row"><span>RT D · Deactivate</span><strong>0.25 mm</strong></div>
<div class="setting-row"><span>Visible key exceptions</span><strong>L-Shift 1.90 mm · Spacebar 0.40 mm</strong></div>
</div>
<div class="screenshot-grid">
<figure class="screenshot-card"><img src="assets/wootility-gunz-specific-actuation.png" alt="Wootility GunZ-specific profile actuation screen"><figcaption>Actuation screen. Regular keys show 0.60 mm; the image records the intentional per-key exceptions.</figcaption></figure>
<figure class="screenshot-card"><img src="assets/wootility-gunz-specific-rapid-trigger.png" alt="Wootility GunZ-specific Rapid Trigger screen"><figcaption>Rapid Trigger screen. Split sensitivity shows 0.35 mm Activate and 0.25 mm Deactivate.</figcaption></figure>
</div>
</article>
</section>
<section class="notebook-entry tracked-section" id="history" data-page="09" data-title="What I kept from V1">
<header class="entry-head"><span class="entry-no">09</span><div><h2 data-i18n="nbHistoryTitle">What I kept from V1</h2><span class="entry-date" data-i18n="nbHistoryDate">The findings that still matter</span></div></header>
<article class="note-sheet">
<ul class="note-list">
<li>Find one repeatable problem before changing a value.</li>
<li>Change one setting at a time.</li>
<li>Training and PvP answer different questions.</li>
<li>Save checkpoints so a test never destroys the last good result.</li>
<li>Copy the process, not someone else’s final numbers.</li>
<li>Keep definitions separate from personal conclusions.</li>
</ul>
<p class="callout"><strong>What changed:</strong> the public site now stays dedicated to Rapid Trigger. This notebook holds the personal full-input story.</p>
</article>
</section>
<section class="notebook-entry tracked-section" id="limits" data-page="10" data-title="Evidence & limits">
<header class="entry-head"><span class="entry-no">10</span><div><h2 data-i18n="nbLimitsTitle">Evidence and limits</h2><span class="entry-date" data-i18n="nbLimitsDate">What I know · what I observed · what I am not claiming</span></div></header>
<article class="note-sheet">
<h3 class="note-heading">Documented behavior</h3>
<ul class="note-list"><li>Rapid Trigger uses movement direction and distance for repeated OFF and ON states.</li><li>Split sensitivity provides separate deactivate/upstroke and activate/downstroke distances.</li><li>Smaller distances require less physical travel.</li></ul>
<h3 class="note-heading">My observations</h3>
<ul class="note-list"><li>A comfortable first actuation and useful Rapid Trigger distances can live in the same profile.</li><li>RT D and RT A feel different when I isolate the release and re-press.</li><li>Mouse verification prevents me from tuning clean keyboard movement around an aim problem.</li></ul>
<h3 class="note-heading">What I am not claiming</h3>
<ul class="note-list"><li>My profiles are correct for every player.</li><li>A millimeter value equals a fixed amount of time.</li><li>Every GunZ miss is caused by a keyboard or mouse setting.</li><li>Personal testing replaces measured game or server data.</li></ul>
<h3 class="note-heading">References · keyboard behavior</h3>
<ul class="note-list"><li>These helped me understand Rapid Trigger, the controls in Wootility, and the switch travel I was working with.</li><li>They do not tell me which values to use in GunZ.</li></ul>
<div class="resource-grid">
<a class="resource-link" href="https://help.wooting.io/article/102-how-to-set-up-rapid-trigger" target="_blank" rel="noopener">Wooting · How to Set Up Rapid Trigger <span>↗</span></a>
<a class="resource-link" href="https://wooting.io/rapid-trigger" target="_blank" rel="noopener">Wooting · Rapid Trigger <span>↗</span></a>
<a class="resource-link" href="https://wooting.io/wootility/changelogs/5.0.0" target="_blank" rel="noopener">Wooting · Wootility controls and terminology <span>↗</span></a>
<a class="resource-link" href="https://www.gateron.com/products/gateron-magic-jade-switch" target="_blank" rel="noopener">Gateron · Magnetic Jade specifications <span>↗</span></a>
</div>
<h3 class="note-heading">References · videos that helped me understand it</h3>
<ul class="note-list"><li>These are supporting keyboard references—not the source of my GunZ method.</li></ul>
<div class="resource-grid">
<a class="resource-link" href="https://www.youtube.com/watch?v=eZENx1T7OLw" target="_blank" rel="noopener">Wooting · What is Rapid Trigger & Actuation Point? <span>↗</span></a>
<a class="resource-link" href="https://www.youtube.com/watch?v=BSlKt7m7xXk" target="_blank" rel="noopener">Wooting · Rapid Trigger FPS demonstration <span>↗</span></a>
<a class="resource-link" href="https://www.youtube.com/watch?v=SsBYdyZPIy8" target="_blank" rel="noopener">Wooting · CS2 settings and profiles <span>↗</span></a>
<a class="resource-link" href="https://www.youtube.com/watch?v=kb0GxgNho3c" target="_blank" rel="noopener">Optimum · Independent Wooting 60HE v2 review <span>↗</span></a>
</div>
<h3 class="note-heading">References · GunZ movement</h3>
<ul class="note-list"><li>These helped me check the movement I was tuning. They are not sources for my Rapid Trigger values.</li></ul>
<div class="resource-grid">
<a class="resource-link" href="https://www.youtube.com/watch?v=OOZllmjE8RM" target="_blank" rel="noopener">GunZ Academy · Beginner's Guide to GunZ: The Duel <span>↗</span></a>
<a class="resource-link" href="https://www.youtube.com/watch?v=FxlyAiZUvzY" target="_blank" rel="noopener">GunZ Academy · Comprehensive K-Style Guide <span>↗</span></a>
</div>
<p class="callout"><strong>Source line:</strong> Wooting, Gateron, GunZ Academy, and Optimum helped me understand the keyboard and movement. The GunZ tuning method, checkpoints, and results come from my own testing.</p>
</article>
</section>
<section class="notebook-entry tracked-section" id="help" data-page="11" data-title="Help & contact">
<header class="entry-head"><span class="entry-no">11</span><div><h2 data-i18n="nbHelpTitle">Questions are welcome.</h2><span class="entry-date" data-i18n="nbHelpDate">Best way to reach me</span></div></header>
<article class="note-sheet"><ul class="note-list"><li>If a step does not make sense, ask.</li><li>If your result does not match mine, that is useful information—not a failure.</li><li>Tell me the repeated symptom, which setting you changed, and what happened after the change.</li></ul><p class="callout good"><strong>Alpha Discord:</strong> <a href="https://discord.gg/tKZ5mjnEpj" target="_blank" rel="noopener">Join the server and ask me directly ↗</a></p><a class="button primary remember-position" href="index.html">Return to the Rapid Trigger guide</a></article>
</section>
</div>
</main>
<aside class="term-panel" id="termPanel" role="dialog" aria-labelledby="termPanelTitle" aria-hidden="true"><div class="term-panel-head"><span class="term-panel-label">Guide term</span><button class="term-panel-close" id="termPanelClose" type="button" aria-label="Close definition">×</button></div><h2 id="termPanelTitle"></h2><div id="termPanelBody"></div><a class="term-panel-glossary remember-position" id="termPanelLink" href="index.html#glossary">Open the full glossary entry →</a></aside>
<footer class="site-footer"><div class="help-strip"><span>Need help with the method?</span><a href="https://discord.gg/tKZ5mjnEpj" target="_blank" rel="noopener">Join Alpha on Discord ↗</a></div><span>Personal research notes by HYPNATIQ</span></footer>
<a class="back-to-top" id="backToTop" href="#top" aria-label="Back to top">↑</a>
<button class="return-to-reading" id="returnToReading" type="button">← Back to where I was reading</button>
<script src="assets/revision-24-translations.js"></script>
<script src="assets/site.js"></script>
</body>
</html>