+
+
+
+# Asphyxia
+
+!!! danger "Existing save data"
+
+ If you have previously used Asphyxia, be sure to backup your **savedata** folder located next to the `plugins` directory.
+ This folder contains important data including your game profiles and scores that you may want to keep.
+
+## What is Asphyxia?
+
+!!! tip ""
+
+ Asphyxia is a tool that handles online services for BEMANI games by simulating an e-amusement network, enabling features like score saving, profile management, game events and other online functionality.
+
+ It consists of two main components:
+
+ - Asphyxia **CORE**: The foundational framework that provides the base functionality but no game support by itself
+ - Asphyxia **PLUGINS**: Community-developed modules that implement game-specific features and support
+
+## Downloading Asphyxia
+
+!!! tip ""
+
+ - Head to [Asphyxia CORE's releases](https://github.com/asphyxia-core/asphyxia-core.github.io/releases) page
+ - Download the latest `asphyxia-core-win-x64.zip` archive
+ - Prepare a permanent place for your Asphyxia files, **preferably an empty folder away from your game data**
+ - Extract the archive inside of it
+
+ You should end up with a structure as follows:
+
+ ```
+ 📂 asphyxia
+ ┣━ 📂 plugins
+ ┃ ┣━ 📂 _example@identifier
+ ┃ ┃ ┗━ ...
+ ┃ ┣━ 📄 asphyxia-core.d.ts
+ ┃ ┣━ 📄 package.json
+ ┃ ┗━ 📄 tsconfig.json
+ ┗━ ▶️ asphyxia-core-x64.exe
+ ```
+
+!!! info "You can delete the `_example@identifier` folder, it serves as an example plugin layout for developers"
+
+## Installing Plugins
+
+!!! info "Asphyxia requires a specific plugin for each game you want to use it with"
+
+!!! tip ""
+
+ To get started with Asphyxia for your specific game(s), you'll need to install the appropriate plugin(s).
+
+ While **we maintain a collection of plugins in our Discord server, we may not have support for every game and version**.
+ In such cases, **you will need to search for community-developed plugins online yourself**.
+
+ To install plugins from our Discord:
+
+ - Join our Discord server using the logo in the bottom right of the page
+ - Navigate to your game's channel
+ - Check the pinned `Resources` message for potential plugin links
+ - Download and extract the plugin
+ - Place the extracted folders (like `sdvx@asphyxia`) into your `plugins` directory
+
+ If plugin files are scattered across multiple files/folders, create a single directory for them and move everything inside, following the `game@asphyxia` naming scheme.
+
+ ```
+ 📂 asphyxia
+ ┣━ 📂 plugins
+ ┃ ┣━ 📂 sdvx@asphyxia
+ ┃ ┣━ 📂 iidx@asphyxia
+ ┃ ┣━ 📂 etc.
+ ┃ ┣━ 📄 asphyxia-core.d.ts
+ ┃ ┣━ 📄 package.json
+ ┃ ┗━ 📄 tsconfig.json
+ ┗━ ▶️ asphyxia-core-x64.exe
+ ```
+
+## Starting and Configuring Asphyxia
+
+!!! tip ""
+
+ Launch `asphyxia-core-x64.exe` to start the server.
+ A browser window will automatically open with the Asphyxia WebUI interface.
+
+### Configuring Service URL
+
+!!! tip ""
+
+ To configure the service URL for your BEMANI game:
+
+ - Open `spicecfg.exe`
+ - Navigate to the `Options` tab
+ - Locate the `EA Service URL` field
+ - Enter the URL shown in Asphyxia WebUI's Dashboard (typically `localhost:8083`)
+
+### Game-specific configuration
+
+!!! info "Each tab corresponds to steps you need to follow for various games"
+
+=== "SDVX"
+
+ !!! tip "Settings and WebUI Assets"
+
+ - In the WebUI, select `SDVX` in the left sidebar
+ - Under `Plugin Settings`, find `Exceed Gear Data Directory`
+ - Enter the full path to your game's data folder (the folder containing `data`, `modules`, `prop`, etc.)
+ - (Optional) Toggle all four `Unlock` switches to unlock all game content by default
+ - Click `Apply` to save your changes
+ - Close Asphyxia by selecting `Process` > `Shutdown CORE` in the top-right corner of the WebUI
+
+ Next, update the WebUI assets:
+
+ - Launch `asphyxia-core-x64.exe` again
+ - Click `Update Webui Assets` in the left sidebar
+ - Click `Update` and confirm the datacode update in `ea3-config.xml`
+ - Wait for the console to show "Done" at the top
+
+ !!! warning "About expected errors"
+
+ While importing WebUI assets you may see errors like:
+ `- [ifs] MD5 mismatch - /data/graphics/ver06/psd_level.ifs`
+
+ If you're using the correct plugin and game data, these can usually be ignored.
+
+ !!! tip "Final setup"
+
+ - Launch SDVX and create a new profile
+ - Close the game
+ - In the WebUI, navigate to `SDVX` → `Profiles` making sure your new profile appears
+ - Customize additional settings through the WebUI interface and make sure everything works as intended
+
+=== "IIDX"
+
+ !!! tip ""
+
+ IIDX setup is straightforward:
+
+ - Launch the game with Asphyxia running
+ - Create a new profile in-game
+ - The profile will automatically appear in the WebUI
+ - You can customize additional settings through the WebUI interface and make sure everything works as intended
+
+## Final words
+
+!!! success "Setup Complete!"
+
+ Remember to always make sure Asphyxia is running **before** starting your game!
+
+ If you were following a guide, you can now return to it and proceed with the next steps.
+
+## Help
+
+--8<-- "docs/snippets/common/help.md"
\ No newline at end of file
diff --git a/docs/extras/audio.md b/docs/extras/audio.md
new file mode 100644
index 0000000..417d6df
--- /dev/null
+++ b/docs/extras/audio.md
@@ -0,0 +1,228 @@
+!!! info "Synopsis"
+
+ This guide explains the different audio modes commonly found in arcade games and their pros and cons, helping you choose the best option for your setup.
+
+!!! danger "Important notice"
+
+ **Recordings and streams must only be shared privately:**
+
+ - Through unlisted videos
+ - In private streams with friends
+ - Within trusted data communities
+
+ Sharing content publicly puts you at serious risk of getting banned from arcade venues and communities. Please respect these guidelines.
+
+
+## Audio modes
+
+### TL;DR
+
+| Mode | DirectSound | WASAPI Shared | WASAPI Exclusive | ASIO |
+| ---------------------- | :----------------: | :----------------: | :---------------: | :--------------------------: |
+| Latency | Highest | Medium | Low | Lowest when setup correctly |
+| Compatibility | Highest | High | High | Low |
+| Multiple audio streams | :material-check: | :material-check: | :material-close: | with extra steps |
+| Audio capture | :material-check: | :material-check: | :material-close: | with extra steps |
+| Recommended for | Legacy games | Most users | Low latency needs | Lower latency needs |
+
+### DirectSound
+
+!!! tip ""
+
+ The legacy Windows audio system, still used by older games.
+
+ ✔️ **Pros**:
+
+ - Extremely high compatibility, especially with older games
+ - Multiple audio sources can play simultaneously
+ - Easy audio capture with OBS, Discord etc.
+ - Simple to set up and use
+
+ ❌ **Cons**:
+
+ - Highest latency of all modes
+ - Being phased out in favor of WASAPI
+ - Limited audio quality compared to modern modes
+
+ 💡 **Pro tip**: Use spice2x's `-lowlatencysharedaudio` setting to reduce latency.
+
+### WASAPI Shared
+
+!!! tip ""
+
+ The modern Windows standard audio mode. Recommended for most users.
+
+ ✔️ **Pros**:
+
+ - Works with most modern games and applications
+ - Multiple audio sources can play simultaneously
+ - Easy audio capture with OBS, Discord etc.
+ - Good balance of latency and compatibility
+
+ ❌ **Cons**:
+
+ - Higher latency than Exclusive mode
+ - Some games may require patches/configuration for Shared mode
+
+ 💡 **Pro tip**: Use spice2x's `-lowlatencysharedaudio` setting to reduce latency.
+
+### WASAPI Exclusive
+
+??? warning "Hardware compatibility notice"
+
+ Your audio device must explicitly support exclusive mode. Check your audio settings:
+
+ 
+
+!!! tip ""
+
+ Gives one application complete control over the audio device.
+
+ ✔️ **Pros**:
+
+ - Significantly lower latency than Shared mode
+ - More consistent audio processing than Shared mode
+ - Better for rhythm games if you don't mind the cons
+
+ ❌ **Cons**:
+
+ - Only one application can output audio at a time
+ - No audio capture without special hardware/software
+ - Can cause system-wide audio interruptions
+
+### ASIO
+
+!!! warning "Hardware requirements"
+
+ For optimal results, use a dedicated ASIO-compatible audio interface. Software solutions like [ASIO4ALL](https://asio4all.org/) or [FlexASIO](https://github.com/dechamps/FlexASIO) exist but have limitations:
+
+ - Added processing overhead
+ - May not improve latency over WASAPI Exclusive
+ - Mostly useful when:
+ - Games are incompatible with your audio device
+ - ASIO is the only supported mode
+ - You need specific ASIO features
+
+!!! tip ""
+
+ Professional audio standard designed for audio interfaces and music production.
+
+ ✔️ **Pros**:
+
+ - Lowest possible latency when properly configured
+ - Direct hardware control
+ - Precise buffer size adjustment
+ - Professional-grade audio quality
+ - Bypass Windows audio stack
+ - Capture is possible when routed through Voicemeeter at the cost of very little added latency
+
+ ❌ **Cons**:
+
+ - Requires specialized hardware for best results
+ - Complex setup process
+ - Usually limited to one application at a time
+ - No direct audio capture support
+ - System performance heavily impacts stability
+ - May require significant tweaking
+
+## ASIO Recording/Streaming
+
+!!! info "This guide assumes your game already uses ASIO and you want to record/stream with audio"
+
+### Required software
+
+!!! tip ""
+
+ ASIO bypasses the Windows audio system that recording/streaming applications use, so you'll need additional software to route the audio:
+
+ - [Voicemeeter Banana](https://vb-audio.com/Voicemeeter/banana.htm) - For audio routing
+ - [OBS Studio](https://obsproject.com/) - For recording and streaming
+
+ Install both applications before continuing.
+
+### Game configuration
+
+!!! tip ""
+
+ Set your game's ASIO output device to `Voicemeeter Virtual ASIO`:
+
+ - For spice2x games: Look for settings like `-iidxasio` or `-sdvxasio` at the top of spicecfg's `Options` tab
+ - For other games: The location depends on your setup, but look for ASIO device selection
+
+### Voicemeeter configuration
+
+!!! tip ""
+
+ First, configure recommended settings:
+
+ 1. Click `Menu` in the top right
+ 2. Enable settings shown below to ensure Voicemeeter:
+ - Starts with Windows
+ - Auto-recovers from audio issues
+
+ 
+
+ Next, set up ASIO output:
+
+ 1. Click the `A1` button in the top right
+ 2. Select the `ASIO (Steinberg)` tab
+ 3. Choose your ASIO device
+
+ Finally, configure audio routing:
+
+ 1. Locate the 4th column in the interface
+ 2. Enable only the `A1` and `B1` toggles as shown:
+
+ 
+
+### OBS Studio Configuration
+
+!!! tip ""
+
+ 1. Run OBS Studio's initial configuration wizard if you haven't already
+
+ 2. Set up audio capture:
+ - In the Sources panel, click `+` and select `Audio Input Capture`
+ 
+ - For the Device, select `VoiceMeeter Output (B1)`
+ 
+
+ 3. Enable audio monitoring:
+ - Click the gear icon in the Audio Mixer panel
+ - Find your Audio Input Capture source
+ - Change `Audio Monitoring` to `Monitor and Output`
+ 
+
+ 4. Configure OBS audio settings:
+ - Go to `File` > `Settings`
+ 
+ - In the `Audio` tab:
+ - Set `Sample Rate` to match your ASIO/game settings
+ - For `Monitoring Device`, select any unused input such as a `VoiceMeeter In`
+ 
+ - Save changes with `Apply` and `OK`
+
+ 5. Add video capture:
+ - In Sources, add either `Display Capture` or `Game Capture`
+ - Adjust OBS video and output settings as needed
+
+### Using this setup
+
+!!! tip ""
+
+ First, ensure Voicemeeter and OBS Studio are running.
+
+ Next, configure your desired OBS output and video settings.
+
+ - For streaming and recording, now use OBS as normal.
+
+ - For Discord sharing:
+ - Right-click the OBS preview window
+ - Select `Fullscreen Projector (Preview)`
+ - Choose which monitor to show the projector on
+ - Press Alt+Tab to switch away from the projector window
+ - In Discord, share the projector window
+
+### Further reading
+
+* [spice2x wiki](https://github.com/spice2x/spice2x.github.io/wiki/Audio-modes-demystified)
diff --git a/docs/extras/controllers.md b/docs/extras/controllers.md
new file mode 100644
index 0000000..1d47452
--- /dev/null
+++ b/docs/extras/controllers.md
@@ -0,0 +1,375 @@
+!!! info "Synopsis"
+
+ This guide provides an overview of popular arcade-style rhythm game controllers currently available to buy.
+ Controllers are ranked based on their popularity within the rhythm game community.
+
+## KONAMI
+
+### beatmania IIDX
+
+!!! info "Lightning cabinets typically use Sanwa buttons, 50g springs, 50g microswitches"
+
+??? tip "PHOENIXWAN+ LMT"
+
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+
+ - Place your mod files inside data_mods in a way that respects the following structure
+ `data_mods/mod_folder/`
+
+ You can think of the mod folder coming to overwrite your game's data folder at runtime.
+ If you're confused, the following may help you understand what we mean.
+
+ ``` hl_lines="6-11"
+ 📂data
+ ┣━📂graphic
+ ┣━📂info
+ ┣━📂movie
+ ┗━📂sound
+ 📂data_mods
+ ┗━📂mod_folder
+ ┣━📂graphic - Files that modify data/graphic go here
+ ┣━📂info - Files that modify data/info go here
+ ┣━📂movie - Files that modify data/movie go here
+ ┗━📂sound - Files that modify data/sound go here
+ 📂dev
+ 📂modules
+ 📂prop
+ ```
+
+!!! info "Example: Omnimix for beatmania IIDX 31 EPOLIS"
+
+ **Directory**: `contents/data_mods/`
+ 
+
+ **Directory**: `contents/data_mods/omnimix_31`
+ 
+
+## Loading mods data files (ifs_layeredfs)
+
+!!! tip ""
+
+ Overwriting game files with mods is heavily discouraged, as there is no clean way of undoing that.
+ This is where ifs_layeredfs comes in, to load modded data files without permanently modifying your game data.
+
+ - Download the most recent release of [ifs_layeredfs](https://github.com/mon/ifs_layeredfs/releases/)
+
+ 
+
+ - Open the archive
+
+ 
+
+ - Your game is 32bit *(spice.exe to launch)*: go in the `32bit` folder
+ - Your game is 64bit *(spice64.exe to launch)*: go in the `64bit` folder
+
+ 
+
+ - Copy the `ifs_hook.dll` file to your game's `modules` folder
+
+ 
+
+ Follow the [Injecting DLL Hooks](#injecting-dll-hooks) section to load this DLL.
+
+## Installing Omnifix (for IIDX Omnimix only)
+
+!!! info "Compatibility"
+
+ [Supported game versions](https://github.com/aixxe/omnifix?tab=readme-ov-file#compatibility)
+ For unsupported game versions, you'll have to patch Omnimix with [spice2x](patchsp2x.md) or [web](patchweb.md) patching.
+
+!!! tip ""
+
+ Omnimix files require modification of your game DLL which can't be handled by ifs_layeredfs.
+ This is where Omnifix comes in, as a commonly agreed upon way of loading Omnimix for beatmania IIDX.
+
+ - Download the latest release archive for [omnifix](https://github.com/aixxe/omnifix/releases/) much like you did with ifs_layeredfs
+ - Extract the `omnifix.dll` file contained in the archive to your game's `modules` folder
+
+ Follow the [Injecting DLL Hooks](#injecting-dll-hooks) section to load this DLL.
+
+ Note that Omnifix also offers optional [launch parameters](https://github.com/aixxe/omnifix?tab=readme-ov-file#options) you may want to consider.
+
+## Injecting DLL Hooks
+
+!!! tip ""
+
+ Adding DLL files to your modules folder won't necessarily make them load automatically.
+ You sometimes need to tell spice2x to load each file individually, like with the DLLs mentioned in this guide.
+
+ - Open your game's `spicecfg.exe`
+ - Head to the `options` tab
+ - Find the `Inject DLL Hooks` option under `Common`
+ - Add the name of the DLL file(s) you want to load inside the text box
+
+ Example: `ifs_hook.dll omnifix.dll`
+
+ You may list one or multiple DLL files separated by a space.
+ The order does matter, as it dictates in which order the DLL files are loaded.
+ **We recommend loading `ifs_hook.dll` before all else**.
+
+ 
diff --git a/docs/extras/hexguide.md b/docs/extras/hexguide.md
new file mode 100644
index 0000000..fa01b2f
--- /dev/null
+++ b/docs/extras/hexguide.md
@@ -0,0 +1,85 @@
+# Game Patching (hex editing)
+
+!!! danger "Before proceeding"
+
+ **This guide should ONLY be used as a last resort if all other methods fail.**
+ **It has a high chance of breaking your game, make backups.**
+
+## Preamble
+
+!!! tip ""
+
+ We're going to patch Beatmania IIDX 25 CANNON BALLERS, however the process is similar for other BEMANI games.
+
+ Here's what you'll need:
+
+ - Your favorite hex editor, here we'll be using [HxD](https://mh-nexus.de/en/hxd/).
+ - A clean copy of your desired BEMANI game.
+ - A backup of your original `.dll` before editing.
+
+## Getting Started
+
+!!! tip ""
+
+ Decide on what hex edits you want to apply, you may find that information from the community or our [Resources](/resources.md).
+
+ It's time to open our hex editor. If you're using HxD, you'll be greeted with the screen below.
+
+
+
+!!! tip ""
+
+ Open your game's `.dll` file in the hex editor.
+
+ For the grand majority of hex edits, this is the main game file, such as `bm2dx.dll`, `soundvoltex.dll`, etc.
+
+ Pictured below, we've opened up `bm2dx.dll` inside HxD.
+
+
+
+!!! danger "Attention"
+
+ The edit we'll be applying is **EXCLUSIVE to this version of the game** and serves as an example.
+
+ This means it will not work on any other version of the game, nor any other game!
+ Hex edits modify specific memory addresses that only apply to very specific game versions.
+
+!!! tip ""
+
+ We'll be editing our game to `Unlock All Songs` and its edit is:
+
+ - **Offset**: `0xB60B2`
+ - **Original**: `74 10`
+ - **Modified**: `90 90`
+
+ In HxD we're going to hit `Ctrl+G` to open the `Goto` window.
+
+ From here, we'll input the offset `B60B2` in the `Offset` section as shown below, and hit `OK`.
+
+
+
+!!! tip ""
+
+ Our cursor should be taken to the offset at the exact location you want to edit.
+
+ As you can see, the numbers in front of the cursor are `74` and `10` which corresponds to what we need to replace.
+
+ **If there's a mismatch, it's likely the offset you've put in was wrong, so be sure to double check!**
+
+
+
+!!! tip ""
+
+ Now all we need to do is select `74 10` and replace it with `90 90`.
+
+ You can do this by either manually typing `90 90` or by copy and pasting.
+
+ It should now look as shown below.
+
+
+
+!!! tip ""
+
+ Lastly, simply save your file and repeat these steps for any other edits you want to apply!
+
+ If at any point your game has issues due to your edits, restore your backup.
\ No newline at end of file
diff --git a/docs/extras/linux_konami.md b/docs/extras/linux_konami.md
new file mode 100644
index 0000000..b0db4e2
--- /dev/null
+++ b/docs/extras/linux_konami.md
@@ -0,0 +1,333 @@
+!!! info "Synopsis"
+
+ Konami arcade games and associated community tooling are built to run on Windows.
+ This guide will document the best currently known ways to get games working on Linux systems.
+
+!!! warning "Compatibility"
+
+ **ONLY** the following game and versions are confirmed to work with the process described in this guide.
+
+ | Game | Version(s) | Caveats (if any) |
+ |------|:----------:|:----------------:|
+ | Sound Voltex | `Exceed Gear` | Subscreen clicks don't work |
+ | DanceDanceRevolution | `World` | |
+ | Mahjong Fight Girl | | |
+
+ This guide was primarily written targetting arch-based systems running KDE and pipewire.
+ **Instructions should still be distro and DE agnostic, but your mileage may vary.**
+
+## Pre-requisites
+
+!!! tip ""
+
+ - A Linux system with:
+ - `pipewire` as an audio backend
+ - `wine` with wow64 included (default on arch since June 2025)
+ - `winetricks curl unzip` installed
+ - `gstreamer gst-plugins-good gst-plugins-ugly gst-libav` for codecs (package names may vary)
+ - Compatible game data placed inside a `📂contents` directory
+ - Your game's regular setup guide opened in another tab
+
+??? tip "Extra requirements for NixOS"
+
+ `spice2x` requires an optional wine feature which NixOS does not enable by default.
+ Apart from that, a patch for `winetricks` is needed due to [weirdness with winetricks on NixOS with WoW64 wine](https://github.com/NixOS/nixpkgs/issues/338367).
+
+ To fix this, copy this to your confiuration:
+ ```nix
+ environment.systemPackages = [
+ (
+ pkgs.wine-with-pcsclite.override {
+ wineBuild = "wineWow64";
+ }
+ )
+ ];
+
+ nixpkgs.overlays = [
+ (
+ final: prev: {
+ wine-with-pcsclite = prev.wine.overrideAttrs (old: {
+ buildInputs = old.buildInputs ++ [final.pcsclite];
+ configureFlags = old.configureFlags ++ ["--with-pcsclite"];
+ });
+ winetricks = prev.winetricks.overrideAttrs (old: {
+ patches = [
+ (final.fetchpatch {
+ # make WINE_BIN and WINESERVER_BIN overridable
+ # see https://github.com/NixOS/nixpkgs/issues/338367
+ url = "https://github.com/Winetricks/winetricks/commit/1d441b422d9a9cc8b0a53fa203557957ca1adc44.patch";
+ hash = "sha256-AYXV2qLHlxuyHC5VqUjDu4qi1TcAl2pMSAi8TEp8db4=";
+ })
+ ];
+ postInstall =
+ old.postInstall
+ + ''
+ sed -i \
+ -e '2i : "''${WINESERVER_BIN:=/run/current-system/sw/bin/wineserver}"' \
+ -e '2i : "''${WINE_BIN:=/run/current-system/sw/bin/.wine}"' \
+ "$out/bin/winetricks"
+ '';
+ });
+ }
+ )
+ ];
+ ```
+
+## Automated setup (for spice2x compatible games)
+
+!!! tip ""
+
+ - Download the `sp2x-linux-setup.sh` script from [NotAkitake/sp2x-linux-setup](https://github.com/NotAkitake/sp2x-linux-setup/)
+ - Place it next to your `📂contents` directory contaning compatible game files
+ - Make the script executable `chmod +x sp2x-linux-setup.sh`
+ - Run the script and follow instructions
+
+## Manual setup
+
+!!! info "This section will mostly describe what the automated process above achieves"
+
+### Installing spice2x
+
+!!! tip ""
+
+ This process is largely the **same as windows** and can be found in your game's setup guide.
+ Simply place the `spice.exe` or `spice64.exe` executable inside `📂contents`.
+
+ We won't need `spicecfg.exe` however.
+ Instead we will later pass `-cfg` as a launch argument to the main spice2x executable later.
+
+!!! warning "NVIDIA Stubs"
+
+ **For ALL graphics cards:** If your game's setup guide has a `Additional steps for AMD and Intel graphics cards` warning in its **Installing spice2x** section, **do what it says**.
+
+### Wine prefix
+
+!!! danger "Double check commands"
+
+ We provide ready-made command for simplicity, however **don't blindy copy and execute them**.
+ **ALWAYS** double check command before running them, and substitute `REPLACE_THIS_PATH` with your own location.
+
+#### Initializing
+
+!!! tip ""
+
+ - Create an empty `📂prefix` directory in the location of your choosing
+ **We advise creating a new prefix for every game and placing it next to `📂contents`**.
+
+ - Run the following command to initialize a new wine prefix without being prompted for mono or gecko.
+
+ ```sh
+ WINEARCH=win64 WINEPREFIX=REPLACE_THIS_PATH/prefix WINEDLLOVERRIDES="mscoree=d;mshtml=d" wineboot --init
+ ```
+
+#### Common dependencies
+
+!!! tip ""
+
+ Some dependencies are required across most games, install them to your prefix using winetricks as follows:
+
+ ```sh
+ WINEARCH=win64 WINEPREFIX=REPLACE_THIS_PATH/prefix winetricks -q dxvk d3dcompiler_42 d3dcompiler_43 d3dcompiler_46 d3dcompiler_47
+ ```
+
+#### Game-specific dependencies
+
+!!! info "If there is no tab for your game, you may skip this step"
+
+!!! tip ""
+
+ === "Default (none)"
+
+ === "DDR"
+
+ Install these to your prefix for background movies to play, otherwise the game will crash.
+
+ ```sh
+ WINEARCH=win64 WINEPREFIX=REPLACE_THIS_PATH/prefix winetricks -q quartz devenum amstream windowscodecs
+ ```
+
+### (optional) PipeWire audio sink
+
+!!! info "You can create an audio device games will accept that routes audio to your desired hardware"
+
+ It **may not be necessary** for all games as it depends on your specific setup and game.
+ You could try following the rest of the guide without this virtual sink first to see whether you need it or not.
+
+!!! tip ""
+
+ - Create the `.config/pipewire/pipewire.conf.d` directory in your home directory if it doesn't already exist
+
+ ```sh
+ mkdir -p "$HOME/.config/pipewire/pipewire.conf.d"
+ ```
+
+ - Create a `spice2x-sink.conf` file in that directory containing:
+
+ ```sh
+ context.modules = [
+ {
+ name = libpipewire-module-loopback
+ args = {
+ audio.position = [ FL FR ]
+ capture.props = {
+ media.class = Audio/Sink
+ audio.format = S16LE
+ audio.rate = 44100
+ audio.channels = 2
+ node.name = spice2x41
+ node.description = "spice2x @ 44100Hz"
+ }
+ playback.props = {
+ node.passive = true
+ node.name = spice2x41.output
+ node.description = "SPICE2X 44100Hz OUTPUT"
+ target.object = "alsa_output.pci-0000_04_00.6.HiFi__hw_Generic_1__sink"
+ audio.format = S16LE
+ }
+ }
+ }
+ ]
+ ```
+
+ The `audio.rate` may need to be set to 48000 on a per game-basis, but for the games covered here, 44100 is fine.
+
+ The `target.object` set above means audio will be routed the first audio device it finds.
+ If you have multiple audio devices available and want to make sure it outputs to a specific one, run:
+
+ ```sh
+ pw-cli list-objects | awk '/node.name/ {name=$0} /media.class/ && /Audio\/Sink/ {gsub(/.*= "|"/,"",name); print name}'
+ ```
+
+ Replace the `target.object` device with the output line corresponding to your desired output device.
+ For example:
+
+ ```sh
+ target.object = "alsa_output.usb-Focusrite_Scarlett_Solo_4th_Gen_S1APY0Z3611B4E-00.HiFi__Line1__sink"
+ ```
+
+ - **Finally**, save and exit then restart pipewire. On systemd distros you may do it by running:
+
+ ```sh
+ systemctl --user restart pipewire.service pipewire-pulse.socket
+ ```
+
+### (optional) Launcher scripts
+
+!!! info "This section will help you create two bash scripts you may use to start and configure your game"
+
+ They are not mandatory but very handy to have, rather than remembering commands to run spice executables with the right prefix, paths, arguments, etc..
+
+!!! tip "Game start"
+
+ Let's create the main launch script first, which will also be used by our second script.
+
+ - Next to your contents directory, create a `launch.sh` file containing:
+
+ ```bash hl_lines="6 19"
+ #!/usr/bin/env bash
+ # Game Launcher
+
+ SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
+ export WINEARCH=win64
+ export WINEPREFIX="REPLACE_THIS_PATH/prefix"
+
+ # Default arguments
+ ARGS=""
+
+ # Optional: Add arguments per line
+ # ARGS="$ARGS -url localhost:8083" # Network URL
+ # ARGS="$ARGS -p 01FXXXXXXXXXXXXXXXXX" # PCBID
+
+ # Append args to this script
+ ARGS="$ARGS $*"
+
+ cd "$SCRIPT_DIR/contents" || exit
+ wine "spice64.exe" $ARGS
+ ```
+
+ - On the first highlighted line: make sure `WINEPREFIX` points to your game prefix created earlier
+
+ - On the second highlighted line: replace `spice64.exe` with `spice.exe` if necessary
+
+ - Make the script executable by running `chmod +x launch.sh`
+
+!!! tip "Game config"
+
+ To get a graphical interface replicating what `spicecfg.exe` does, we can simply call our previous script and pass `-cfg` as an argument.
+
+ - Next to your previous script, create a `config.sh` file containing:
+
+ ```bash
+ #!/usr/bin/env bash
+ # Config Launcher
+
+ SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
+ "$SCRIPT_DIR/launch.sh" -cfg
+ ```
+
+ - On the last line, make sure the file name matches the previous script
+
+ - Make the script executable by running `chmod +x config.sh`
+
+!!! warning "Try executing `config.sh`"
+
+ The spice2x configuration window for your game should appear.
+ Your game should also be detected and show in the top right!
+
+ If your game isn't detected, it's highly likely paths are wrong somewhere in your scripts.
+
+### Game-specific last steps
+
+!!! info "If there is no tab for your game, you may skip this step"
+
+!!! tip ""
+
+ === "Default (none)"
+
+ === "SDVX"
+
+ - You need to patch `Shared Mode WASAPI` to ensure audio comes through wine.
+ Either use the previously created `config.sh` to start spicecfg, or use the command in the next section.
+ If you don't know how patches work, follow instructions in our [spice2x patching](./patchsp2x.md) guide.
+
+ ---
+
+ - You need to set your monitor orientation to portait before playing
+
+ - **OR** If you want to play the game windowed and keep your display in landscape orientation:
+
+ - Create a `wine_desktop.reg` file containing:
+
+ ```reg
+ Windows Registry Editor Version 5.00
+
+ [HKEY_CURRENT_USER\Software\Wine\Explorer]
+ "Desktop"="Default"
+
+ [HKEY_CURRENT_USER\Software\Wine\Explorer\Desktops]
+ "Default"="1080x1920"
+ ```
+
+ - Fix the paths in the command below and run it. Then feel free to delete the `.reg` file:
+
+ ```sh
+ WINEARCH=win64 WINEPREFIX=REPLACE_THIS_PATH/prefix wine regedit REPLACE_THIS_PATH/wine_desktop.reg
+ ```
+
+### What's next?
+
+!!! success "Linux-specific instructions are over"
+
+ Head to your game's setup guide, straight to the "Configuring spice2x" section.
+
+ - **IF** you opted to use the PipeWire audio sink, set it as your default audio device before starting the game
+ - Skip the `Configuring audio` section
+ - Skip any section asking you to install VCRedist and/or DirectX, our prefix takes care of that
+ - Use the previously created `config.sh` instead of spicecfg, and `launch.sh` to start the game
+ **OR** If you opted not to create scripts, instead use this, fixing the paths and spice executable name:
+
+ ```sh
+ cd REPLACE_THIS_PATH/contents && WINEARCH=win64 WINEPREFIX=REPLACE_THIS_PATH/prefix wine "spice64.exe" -cfg
+ ```
+
+ And use the same command without the `-cfg` argument to start the game.
diff --git a/docs/extras/patchsp2x.md b/docs/extras/patchsp2x.md
new file mode 100644
index 0000000..669a2da
--- /dev/null
+++ b/docs/extras/patchsp2x.md
@@ -0,0 +1,89 @@
+# Game Patching (spice2x)
+
+!!! info "TWO-TORIAL Patcher"
+
+ URL: `https://sp2x.two-torial.xyz`
+
+ [Known spice2x patchers](/resources.md#spice2x-patchers)
+
+!!! warning "Compatibility"
+
+ This patching method only is for [spice2x supported games](https://github.com/spice2x/spice2x.github.io/wiki/List-of-supported-games).
+
+ **Please make sure you're using the latest release for [spice2x](https://spice2x.github.io/) as the feature is fairly new.**
+
+!!! danger "Before proceeding"
+
+ **It is highly recommended to use an unpatched DLL as your base!**
+
+ If you've already patched your game through other methods *([web patching](patchweb.md) or [hex editing](hexguide.md))*,
+ **Please replace your game's DLL with the original**.
+
+## Getting Started
+
+!!! tip ""
+
+ **The following guide works the same regardless of which spice2x compatible game you're using.**
+
+ In this case we will be using a clean SDVX installation as a reference, with the following folder structure.
+
+
+
+#### Importing Patches from URL
+
+!!! tip ""
+
+ Open `spicecfg.exe` and head to the `Patches` tab.
+
+
+
+!!! tip ""
+
+ By default no patches will be available, we need to import some.
+
+ - Click on `Import from URL`.
+ - Paste your preferred patcher's URL.
+
+ **Note**: Check the [Resources](/resources.md) page for a list of recommended patchers.
+
+ - Click on `Import`.
+
+ ^^**If patching fails, it most likely is because the URL you provided doesn't support your game's version.**^^
+
+
+
+### Picking Patches
+
+!!! danger "Important"
+
+ **As a general rule of thumb, if you're not sure what a patch does or you're not absolutely certain you need it, leave it alone**.
+
+!!! tip ""
+
+ After a successful import, your patches should now show up inside spice2x.
+
+ A new `Patches` folder has also been created, containing a `.json` file with your available patches for offline use.
+
+
+
+!!! tip ""
+
+ Now you may pick and choose desired patches!
+
+ For game-specific instructions, refer to their respective dedicated pages.
+
+### Auto apply / Overwrite game files
+
+!!! tip "Auto apply (recommended)"
+
+ After picking your patches, it is **strongly recommended** to tick the `Auto apply patches on game start` box.
+
+ Doing so will keep your game files intact until you start it, at which point your selected patches will apply.
+ Upon closing the game your game's files will be restored.
+
+!!! warning "Overwrite game files"
+
+ You also have the option to `Overwrite game files`, which will **permanently modify your game files**.
+
+ This is **NOT** recommended unless you have a good reason to do so.
+ A backup of your original dll will be created, however it is recommended to make your own!
\ No newline at end of file
diff --git a/docs/extras/patchweb.md b/docs/extras/patchweb.md
new file mode 100644
index 0000000..19a2568
--- /dev/null
+++ b/docs/extras/patchweb.md
@@ -0,0 +1,76 @@
+# Game Patching (web)
+
+!!! info "Known web patchers: [Resources](/resources.md#web-patchers)"
+
+!!! warning "For BEMANI games consider [spice2x Patching](patchsp2x.md)"
+
+ **This patching method is outdated for BEMANI games.**
+
+ However if your game isn't supported, follow this guide.
+
+!!! danger "Before proceeding"
+
+ **It is highly recommended to use an unpatched DLL or EXE as your base!**
+
+ If you've already patched your game through other methods *([spice2x patching](patchsp2x.md) or [hex editing](hexguide.md))*,
+ **Please replace your game's DLL or EXE with the original**.
+
+### Getting started
+
+!!! tip ""
+
+ For this example, we'll be using our [web patcher](https://patcher.two-torial.xyz).
+ Almost every other patcher looks and functions exactly the same as this one.
+
+ **If your game is not supported by our web patcher, please check [Resources](/resources.md#web-patchers) and use another web patcher.**
+
+ Go to your chosen patcher's website, you'll get something similar to this:
+
+
+
+!!! tip ""
+
+ Click on any game you'd like the patches for. In this case, we'll use CHUNITHM VERSE.
+
+
+
+
+
+!!! tip ""
+
+ Here, either:
+
+ - Drag and drop the `.dll` or `.exe` file the site prompts you to use.
+ - **OR** click on `Choose a file` and select it that way.
+
+ If you've used the correct file and the site is compatible, it will tell you.
+
+ `X of X patches matched (100%)` means the patcher is compatible with your game.
+ **If this shows any less than 100%, DO NOT use it. Your `.dll` or `.exe` file might not be clean. Only proceed with a clean one.**
+
+ **Please keep in mind that some patchers may not support the most recent versions of your game right away.**
+
+
+
+!!! tip ""
+
+ Now, you can select the patches you'd like to apply.
+
+ If you're unsure on what to do, refer to your specific game's guide as it might have more information there.
+ Otherwise feel free to join our Discord server, the link is at the top of the [home page](/index.md), and ask the community!
+
+
+
+!!! tip ""
+
+ When you're done selecting patches, click on `Save Patched File` and your new file will start downloading.
+
+
+
+!!! danger "Backup your original `.dll` or `.exe` file first!"
+
+!!! tip ""
+
+ Now you may replace your data's file with the patched one you just downloaded.
+
+ Once you've done that, you're done. Enjoy!
diff --git a/docs/extras/unity.md b/docs/extras/unity.md
new file mode 100644
index 0000000..0d33dd7
--- /dev/null
+++ b/docs/extras/unity.md
@@ -0,0 +1,59 @@
+!!! danger "Before proceeding"
+
+ This guide applies to games made in the Unity engine, such as maimai DX, O.N.G.E.K.I. and Card Maker.
+
+ **It is highly recommended to use an unpatched Assembly DLL as your base!**
+
+!!! info "Patches have historically been hardcoded into the unprotected `Assembly-CSharp.dll`"
+
+ The modern approach is to use BepInEx to load custom patches without tampering with Assembly-CSharp.
+
+# ZeroTier for Cabinet-to-Cabinet Play
+
+!!! danger "Warning for CHUNITHM"
+
+ CHUNITHM has stricter network requirements than other SEGA games and needs a specific subnet. In this guide, we will use the subnet `192.168.196.0` as an example. However, to run CHUNITHM, you must change it to the subnet `192.168.139.0`. If you don't, cabinets set to "FOLLOW THE STANDARD" will fail to connect. You will also need to adjust the `IPv4 Auto-Assign` setting of your Zerotier network accordingly by changing `196` to `139`.
+
+## Installing
+
+!!! tip ""
+
+ Go to the [ZeroTier download page](https://www.zerotier.com/download/). Download and run the Windows installer.
+ After installation, the program will open automatically in your taskbar.
+
+## Joining a network
+
+!!! tip "Connecting to a network"
+
+ To join a network on ZeroTier, you will need its **16-digit Network ID**.
+
+ - Start ZeroTier if it's not already running
+ - Right click on the ZeroTier icon in your taskbar
+ - Click on "Join New Network"
+ - Enter the Network ID
+ - Click on "Join"
+
+ That's it!
+
+!!! info "Checking your connection"
+
+ Open your Command Prompt, and run the command `ipconfig`
+ Your IP address will appear under `Ethernet adapter ZeroTier One [NETWORK ID]` next to `IPv4 Address`
+
+ 
+
+ To check if you can successfully reach another computer on the network, run the command `ping [IPv4 Address]` replacing `[IPv4 Address]` with the IP address of the other computer, *not your own*.
+
+!!! tip "Configuration for segatools"
+
+ Edit `segatools.ini` with the following content:
+
+ ```
+ [netnev]
+ enable=1
+ addrSuffix= The last segment of your ZeroTier IP address (e.g., if your IP is 192.168.196.5, set addrSuffix = 5)
+
+ [keychip]
+ subnet=192.168.196.0
+
+ [system]
+ dipsw1=1 ;Set this to 1 on the host machine and set this to 0 on all others
+ ```
+
+ !!! warning "Each person must have their own keychip"
+
+ If you play on a remote network, you likely already have your own keychip.
+ If not, you can use these example keychips: `A61E-01D02321145` ; `A61E-01A30831145` ; `A61E-01E38091145` ; `A61E-01E46241145`
+
+ When starting your game, make sure to allow any Windows Firewall pop-ups (such as for `amdaemon.exe`, `mu3.exe`, `chusanApp.exe`...)
+
+ ??? info "If you didn't see a pop-up"
+
+ This could mean one of two things.
+
+ Either you have already allowed it, and cab-to-cab is working successfully. That's great! No need to change anything.
+ Or, you denied access, and cab-to-cab isn't working. In that case follow these steps:
+
+ - Open the Windows Control Panel
+ - Click on `System and Security`
+ - Click on `Windows Defender Firewall`
+ - On the left side, click on `Advanced settings`
+ - In the new window, click on `Inbound Rules` and look for your game's executables
+ - Right click on one of them, then click on `Properties`
+ - Select `Allow the connection` then press `OK`
+ - Repeat this for all game executables
+
+ Alternatively, you can disable your firewall for both *public* and *private networks*. Please note that this should only be a **temporary measure** for testing, as it poses a **^^security risk^^** to your computer.
+
+!!! tip "Configuration for spice2x"
+
+ - Open `spicecfg.exe`
+ - Navigate to the `Development` tab
+ - Enter your ZeroTier IP in the `Preferred NetAdapter IP` field
+ - Enter `255.255.255.0` in the `Preferred NetAdapter Subnet` field
+
+## Creating a network
+
+!!! tip ""
+
+ - Go to [my.zerotier.com](https://my.zerotier.com/) and create an account
+ - Create a network
+ - Click on its name in the list to configure it
+
+!!! info "About your Network ID"
+
+ Your *Network ID* is displayed on your account's homepage, and in the configuration menu.
+ This allows you and others to [join your network](#joining-a-network).
+
+ If your network is set to `Public` then **anyone** with it can join it. Treat it like a password.
+
+### Network configuration
+
+!!! info "Following tabs correspond to the ones found in the configuration menu, follow both "Basics" and "Advanced""
+
+=== "Basics"
+
+ !!! info "Name"
+
+ Either keep the default random name, or rename it to your liking.
+
+ !!! tip "Access Control"
+
+ - **Private**: This is the default option and will require you to accept people who want to join your network
+ - **Public**: ^^Recommended^^, anyone with the *Network ID* can join without authorization
+
+=== "Advanced"
+
+ !!! tip "Managed Routes"
+
+ Delete the already existing entry.
+ Under "Add Routes", set "Destination" as `192.168.196.0/24` then press "Submit".
+
+ !!! tip "IPv4 Auto-Assign"
+
+ Delete the already existing entry.
+ Under "Add IPv4 Address Pools" set "Range Start" as `192.168.196.1` and "Range End" as `192.168.196.254` then press "Submit".
+
+ !!! info ""
+
+ You should end up with this:
+
+ 
\ No newline at end of file
diff --git a/docs/games/konami/beatstream/animutribe/setup.md b/docs/games/konami/beatstream/animutribe/setup.md
new file mode 100644
index 0000000..ea7063e
--- /dev/null
+++ b/docs/games/konami/beatstream/animutribe/setup.md
@@ -0,0 +1,61 @@
+
+# Game Setup
+
+--8<-- "docs/snippets/common/old_guide.md"
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+### Getting Started
+
+!!! tip ""
+ Before we even touch the game, let's fiddle with our audio settings to minimize any potential audio issues on startup. In Windows, go to `Playback Devices` and then right click on your default device and go to `Properties`. From there, hit the `Advanced` tab and set your `Default Format` to `44100 Hz` and check both of the options inside `Exclusive Mode` as pictured.
+
+
+
+!!! tip ""
+
+ Once that's done,, it's time to work on setting up your data.
+
+ After downloading your data, the first thing to do is make sure your files aren't set to READ ONLY, make sure to uncheck it from the main folder in the Windows Properties tab if so. Then, put your desired 64-bit tools inside the game's `contents` folder, and to create a `.bat` file. Pictured below is what your folder should look like, feel free to name your `.bat` file whatever you desire, for the sake of convenience we've named ours `gamestart.bat`.
+
+
+
+### Configuring Your Tools
+
+!!! tip ""
+ Now that you have your files ready, open up your `.bat` file in your desired text editor (we're using [Notepad++](https://notepad-plus-plus.org/)) and edit it with your desired parameters, for the purpose of this guide we will demonstrate both a local network configuration and an online example below with SpiceTools, skip to whichever you're in need of accordingly and please keep in mind you can add whatever additional parameters you desire.
+
+!!! warning "If you're not using SpiceTools:"
+ The overall structure of your .bat file will differ from the guide, namely the initialization of SpiceTools won't be present and potential parameters may differ. As stated above, make sure to check the documentation of your tools to ensure you're using the correct parameters for your needs.
+
+### Configuring for a Local Network
+
+!!! tip ""
+ For our local network configuration example, on a single line in the `.bat` file we're going to type `spice64.exe -ea -w` and save the file.
+
+ What do these different parameters do?
+
+ - `-ea` enables an integrated e-amusement server within SpiceTools.
+ - `-w` will boot the game in windowed mode which will ease our initial setup and testing later, make sure to remove `-w` to run the game fullscreen once you're done setting up!
+
+### Configuring for an Online Network
+
+!!! tip ""
+ For our online network example we're simply doing the above but with different parameters! On our single line, we're going to type `spice64.exe -p XXXXXXXXXXXXXXXXXXXX -url http://yoururlhere.com/ -w` and save the file.
+
+ What do these different parameters do?
+
+ - `-p` takes your PCBID on your network of choice, simply replace `XXXXXXXXXXXXXXXXXXXX` with your PCBID.
+ - `-url` allows you to specify a custom service URL to connect with, simply replace `http://yoururlhere.com/` with your chosen network's URL.
+ - `-w` will boot the game in windowed mode which will ease our initial setup and testing later, make sure to remove `-w` to run the game fullscreen once you're done setting up!
+
+### Final Steps and Setting up the Game
+
+!!! tip ""
+ The last steps you'll have to do with your chosen tools is simply setting up your desired keybinds! Make sure you setup the `Test` keybind as it will be critical for setting up the game. Once you've done that, launch your game for the first time by double clicking the `.bat` you setup and the game should load.
+
+!!! tip ""
+ You're all done! If you have a touchscreen monitor make sure it's plugged in, it should work automatically, if it doesn't check out the advertised `Troubleshooting` section at the link below.
+
+!!! warning "Have any other errors?"
+ Check out the [Troubleshooting](troubleshooting.md) section and [Error Code](/errorcodes/konami.md) section to resolve any issues not seen in this guide to greater depth.
diff --git a/docs/games/konami/beatstream/animutribe/troubleshooting.md b/docs/games/konami/beatstream/animutribe/troubleshooting.md
new file mode 100644
index 0000000..c8f0c1d
--- /dev/null
+++ b/docs/games/konami/beatstream/animutribe/troubleshooting.md
@@ -0,0 +1,44 @@
+
+# Troubleshooting
+
+--8<-- "docs/snippets/common/old_guide.md"
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+### Hardware Specs
+
+!!! tip ""
+ Bemani PC Type 6 (ADE-704A)
+
+ Based on an AMD Embedded R Series SoC.
+
+ CPU: Intel Celeron B810
+
+ GPU: AMD Radeon E4690
+
+ OS: Windows 7 Embedded
+
+### My Game Doesn't Boot After Following the Guide!
+
+!!! tip ""
+ The most common problem present here is if you do not have an E:/ drive. To resolve this issue, you must modify your game with the `E:/drive fix` patch.
+
+### My Touchscreen Monitor Isn't Working
+
+!!! tip ""
+ Try adding the `-wintouch` parameter to your `.bat` file, if that doesn't work, check the log and make sure it works with windows. SpiceTools at this point works with the grand majority of touchscreen monitors but no doubt some outliers are out there!
+
+### My Game Is Running Slow/Lagging
+
+!!! tip ""
+ Make sure you at least meet the above hardware requirements, try to eliminate any unnecessary background processes during play as well.
+
+### My Game Is Running Crazy Fast!
+
+!!! tip ""
+ The most common reason for this is the game is running over its required 60 Hz, the game is hardcoded to run at 60 Hz and this cannot be changed. To solve this, set your monitor's refresh rate to 60 Hz. You can always check on the game's monitor check if the game is fluctuating around 59.94hz, the NTSC standard. If it's not around there and your monitor is indeed set to 60 Hz, consider trying a different panel or forcing vsync on in your GPU's graphics settings.
+
+### Which Offset Is Which?
+
+!!! tip ""
+ If you're getting too many fasts, increase your offset (+). If you're getting too many slows, decrease your offset (-).
\ No newline at end of file
diff --git a/docs/games/konami/ddr/a20/setup.md b/docs/games/konami/ddr/a20/setup.md
new file mode 100644
index 0000000..c55f489
--- /dev/null
+++ b/docs/games/konami/ddr/a20/setup.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/konami/ddr/common/setup.md"
\ No newline at end of file
diff --git a/docs/games/konami/ddr/a20/troubleshooting.md b/docs/games/konami/ddr/a20/troubleshooting.md
new file mode 100644
index 0000000..1db23cf
--- /dev/null
+++ b/docs/games/konami/ddr/a20/troubleshooting.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/konami/ddr/common/troubleshooting.md"
\ No newline at end of file
diff --git a/docs/games/konami/ddr/a20plus/setup.md b/docs/games/konami/ddr/a20plus/setup.md
new file mode 100644
index 0000000..3799d19
--- /dev/null
+++ b/docs/games/konami/ddr/a20plus/setup.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/konami/ddr/common/setup.md"
\ No newline at end of file
diff --git a/docs/games/konami/ddr/a20plus/troubleshooting.md b/docs/games/konami/ddr/a20plus/troubleshooting.md
new file mode 100644
index 0000000..cc4adb5
--- /dev/null
+++ b/docs/games/konami/ddr/a20plus/troubleshooting.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/konami/ddr/common/troubleshooting.md"
\ No newline at end of file
diff --git a/docs/games/konami/ddr/a3/setup.md b/docs/games/konami/ddr/a3/setup.md
new file mode 100644
index 0000000..3a8d6be
--- /dev/null
+++ b/docs/games/konami/ddr/a3/setup.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/konami/ddr/common/setup.md"
\ No newline at end of file
diff --git a/docs/games/konami/ddr/a3/troubleshooting.md b/docs/games/konami/ddr/a3/troubleshooting.md
new file mode 100644
index 0000000..1fc9911
--- /dev/null
+++ b/docs/games/konami/ddr/a3/troubleshooting.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/konami/ddr/common/troubleshooting.md"
\ No newline at end of file
diff --git a/docs/games/konami/ddr/common/setup.md b/docs/games/konami/ddr/common/setup.md
new file mode 100644
index 0000000..8f3dbd2
--- /dev/null
+++ b/docs/games/konami/ddr/common/setup.md
@@ -0,0 +1,162 @@
+# Game Setup
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+## About data
+
+!!! note ""
+
+ Please keep the following in mind as you're going through this guide.
+
+ DDR's codename is `MDX`. Starting with `DDR A20` this would be either:
+
+ - `MDX-001` *(Other cabs, 32 bits)*
+ - `MDX-003` *(Gold cab, 64 bits)*
+
+ The gold cab version contains more features, such as exclusive songs or the "GOLDEN LEAGUE" mode.
+
+## Preparing data
+
+--8<-- "docs/snippets/common/data_readonly.md"
+
+ The **complete game data** should be approximately **20 GB or larger**.
+ If your data is significantly smaller, you likely have an update archive instead of the full game data.
+
+ Here's what the expected data structure should look like:
+
+ ```
+ 📂arkdata
+ 📂com
+ 📂data
+ 📂modules
+ 📂prop
+ ```
+
+--8<-- "docs/snippets/konami/common/data_bad.md"
+
+!!! info "If your data is already up-to-date, you can skip ahead to the [Installing spice2x](#installing-spice2x) section"
+
+## Updating data
+
+!!! danger "Please make sure you're using the right update for your current data."
+
+ DDR updates have `MDX` and one or two datecodes in their archive names.
+
+ **Single datecode:** Contains one update (e.g., `MDX_NewDateCode.7z`)
+ **Two datecodes:** Updates from the older to newer version (e.g., `MDX_OldDateCode-NewDateCode.rar`)
+
+ A date code should look something like this: `YYYYMMDDXX`
+
+ In the two-datecode example:
+
+ - `OldDateCode` is the older date, the game version required to apply this update
+ - `NewDateCode` is the newer date, and is the version you'll arrive at after applying the update
+
+--8<-- "docs/snippets/konami/common/data_update.md"
+
+## Installing spice2x
+
+!!! info "If you already have spice2x installed, ensure you're using the latest version"
+
+??? tip "For MDX-001 (32 bits)"
+
+ - Visit [spice2x.github.io](https://spice2x.github.io) to download the latest release
+ - Extract both `spice.exe` and `spicecfg.exe` from the archive into your game's directory
+
+ ``` hl_lines="6-7"
+ 📂arkdata
+ 📂com
+ 📂data
+ 📂modules
+ 📂prop
+ 🌶️spice.exe
+ 🌶️spicecfg.exe
+ ```
+
+??? tip "For MDX-003 (64 bits)"
+
+ - Visit [spice2x.github.io](https://spice2x.github.io) to download the latest release
+ - Extract both `spice64.exe` and `spicecfg.exe` from the archive into your game's directory
+
+ ``` hl_lines="6-7"
+ 📂arkdata
+ 📂com
+ 📂data
+ 📂modules
+ 📂prop
+ 🌶️spice64.exe
+ 🌶️spicecfg.exe
+ ```
+
+## Configuring spice2x
+
+--8<-- "docs/snippets/konami/common/spicecfg_preamble.md"
+
+=== "Buttons"
+
+--8<-- "docs/snippets/konami/common/spicecfg_buttons.md"
+
+ !!! tip "Binding your buttons"
+
+ Click on `Bind` or `Naive` then press the key you want associated with the action.
+
+ With your controller and/or keyboard plugged in, configure your keys for P1 and/or P2:
+
+ - **Maintenance**: `Service, Test`
+ - **Game buttons**: `Up, Down, Left, Right`
+ - **Menu buttons**: ` Start, Up, Down, Left, Right`
+ - **Keypad**: `Keypad Insert Card`, `1 to 9`
+
+--8<-- "docs/snippets/konami/common/spicecfg_buttons_additionalinfo.md"
+
+=== "Analogs"
+
+--8<-- "docs/snippets/konami/common/spicecfg_nochange.md"
+
+=== "Overlay"
+
+--8<-- "docs/snippets/konami/common/spicecfg_overlay.md"
+
+=== "Lights"
+
+--8<-- "docs/snippets/konami/common/spicecfg_lights.md"
+
+=== "Cards"
+
+--8<-- "docs/snippets/konami/common/spicecfg_cards.md"
+
+=== "Patches"
+
+--8<-- "docs/snippets/konami/common/spicecfg_patches.md"
+
+=== "API"
+
+--8<-- "docs/snippets/konami/common/spicecfg_nochange.md"
+
+=== "Options"
+
+--8<-- "docs/snippets/konami/common/spicecfg_options_nvprofile.md"
+
+=== "Advanced"
+
+--8<-- "docs/snippets/konami/common/spicecfg_nochange.md"
+
+=== "Development"
+
+--8<-- "docs/snippets/konami/common/spicecfg_nochange.md"
+
+## Connecting to a network
+
+--8<-- "docs/snippets/konami/common/setup_network.md"
+
+## Installing VCRedist & DirectX
+
+--8<-- "docs/snippets/common/setup_vcredist_directx.md"
+
+## Before playing
+
+--8<-- "docs/snippets/common/before_playing.md"
+
+## Help
+
+--8<-- "docs/snippets/common/help.md"
\ No newline at end of file
diff --git a/docs/games/konami/ddr/common/troubleshooting.md b/docs/games/konami/ddr/common/troubleshooting.md
new file mode 100644
index 0000000..050c438
--- /dev/null
+++ b/docs/games/konami/ddr/common/troubleshooting.md
@@ -0,0 +1,27 @@
+# Troubleshooting
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+!!! info "For any issues not covered here, spice2x's [Known issues](https://github.com/spice2x/spice2x.github.io/wiki/Known-issues) page might prove useful"
+
+## Technical problems
+
+### Crashes
+
+??? tip "Game crashes on startup or when starting a song / No background and no music video"
+
+ This is probably due to missing or incorrectly registered codecs. From version 25-08-17 of spice2x onwards, the codecs will be registered automatically when you launch the game, so please update your installation. If this does not resolve the issue, or if you do not wish to update, please follow the DDR section on the [spice2x wiki](https://github.com/spice2x/spice2x.github.io/wiki/DLL-Dependencies#ddr).
+
+### Performance
+
+!!! info "Check out spice2x's [PC optimization](https://github.com/spice2x/spice2x.github.io/wiki/PC-optimization) guide"
+
+??? tip "Game is running too slow/fast"
+
+ Try to eliminate any unnecessary background processes during play and ensure your screen's framerate is set to 60 FPS.
+
+## Other
+
+??? tip "Where are the option for Dancers/Shading/Measure lines/Fast-Slow/Layering?"
+
+ These options are locked behind network requirements and will not be displayed unless you are connected to a network that has written support for these options. Patches are available to mitigate this, see our [spice2x Patching guide](/extras/patchsp2x.md).
\ No newline at end of file
diff --git a/docs/games/konami/ddr/world/setup.md b/docs/games/konami/ddr/world/setup.md
new file mode 100644
index 0000000..d987fee
--- /dev/null
+++ b/docs/games/konami/ddr/world/setup.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/konami/ddr/common/setup.md"
\ No newline at end of file
diff --git a/docs/games/konami/ddr/world/troubleshooting.md b/docs/games/konami/ddr/world/troubleshooting.md
new file mode 100644
index 0000000..e4c12dc
--- /dev/null
+++ b/docs/games/konami/ddr/world/troubleshooting.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/konami/ddr/common/troubleshooting.md"
\ No newline at end of file
diff --git a/docs/games/konami/gitadora/exchain/setup.md b/docs/games/konami/gitadora/exchain/setup.md
new file mode 100644
index 0000000..6866b0f
--- /dev/null
+++ b/docs/games/konami/gitadora/exchain/setup.md
@@ -0,0 +1,147 @@
+
+# Game Setup
+
+--8<-- "docs/snippets/common/old_guide.md"
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+!!! danger "Warning:"
+ Please make sure your data is from an appropriate source and unmodified before proceeding, this guide is unable to troubleshoot any problems related to bad or poorly managed data.
+
+ If you obtained data from a torrent file, make sure you're not seeding the data before proceeding as well.
+
+ Lastly, for demonstrative purposes, this guide uses SpiceTools, you should consult appropriate documentation and requirements of your desired tools as the setup process is likely to be extremely similar.
+
+### Getting Started.
+
+!!! tip ""
+ Before we even touch the game, let's fiddle with our audio settings to minimize any potential audio issues on startup. In Windows, go to `Playback Devices` and then right click on your default device and go to `Properties`. From there, hit the `Advanced` tab and set your `Default Format` to `44100 Hz` and check both of the options inside `Exclusive Mode` as pictured.
+
+
+
+!!! tip ""
+ Once that's done, it's time to work on setting up your data.
+
+ After downloading your data, the first thing to do is make sure your files aren't set to READ ONLY, make sure to uncheck it from the main folder in the Windows Properties tab if so. Then, the first thing to do is put your desired 64-bit tools inside the game's `contents` folder, and to create a `.bat` file. Pictured below is what your folder should look like, feel free to name your `.bat` file whatever you desire, for the sake of convenience we've named ours `gamestart.bat`.
+
+
+
+!!! tip ""
+ Why does this look different than the usual? This installation includes a `modules` folder that Spice automatically detects, keeping things clean and simple.
+
+### Configuring Your Tools
+
+!!! tip ""
+ Now that you have your files ready, open up your `.bat` file in your desired text editor (we're using [Notepad++](https://notepad-plus-plus.org/)) and edit it with your desired parameters, for the purpose of this guide we will demonstrate both a local network configuration and an online example below for both launching the guitar version and drum version using SpiceTools, skip to whichever you're in need of accordingly and please keep in mind you can add whatever additional parameters you desire.
+
+!!! warning "If you're not using SpiceTools:"
+ The overall structure of your .bat file will differ from the guide, namely the initialization of SpiceTools won't be present and potential parameters may differ. As stated above, make sure to check the documentation of your tools to ensure you're using the correct parameters for your needs.
+
+### Configuring for a Local Network
+
+!!! tip ""
+ **FOR GUITAR**
+
+ For our guitar local network configuration example, on a single line in the `.bat` file we're going to type `spice64.exe -e prop\eamuse-config2.xml -2ch -ea -w` and save the file.
+
+ What do these different parameters do?
+ - `-e` sets a custom path for the eamuse config to boot the proper one (in this case, guitar via `prop\eamuse-config2.xml`)
+ - `-2ch` enables 2-channel audio for GITADORA
+ - `-ea` enables an integrated e-amusement server within SpiceTools.
+ - `-w` will boot the game in windowed mode which will ease our initial setup and testing later, make sure to remove `-w` to run the game fullscreen once you're done setting up!
+
+ Pictured below, the contents of our `gamestart.bat` file in Notepad++.
+
+
+
+!!! tip ""
+ **FOR DRUM**
+
+ For our drum local network configuration example, on a single line in the `.bat` file we're going to type `spice64.exe -2ch -ea -w` and save the file.
+
+ What do these different parameters do?
+ - `-2ch` enables 2-channel audio for GITADORA
+ - `-ea` enables an integrated e-amusement server within SpiceTools.
+ - `-w` will boot the game in windowed mode which will ease our initial setup and testing later, make sure to remove `-w` to run the game fullscreen once you're done setting up!
+
+ Pictured below, the contents of our `gamestart.bat` file in Notepad++.
+
+
+
+### Configuring for an Online Network
+
+!!! tip ""
+ **FOR GUITAR**
+
+ For our guitar online network example we're simply doing the above but with different parameters! On our single line, we're going to type `spice64.exe -e prop\eamuse-config2.xml -2ch -p XXXXXXXXXXXXXXXXXXXX -url http://yoururlhere.com/ -w` and save the file.
+
+ What do these different parameters do?
+
+ - `-e` sets a custom path for the eamuse config to boot the proper one (in this case, guitar via `prop\eamuse-config2.xml`)
+ - `-2ch` enables 2-channel audio for GITADORA
+ - `-p` takes your PCBID on your network of choice, simply replace `XXXXXXXXXXXXXXXXXXXX` with your PCBID.
+ - `-url` allows you to specify a custom service URL to connect with, simply replace `http://yoururlhere.com/` with your chosen network's URL.
+ - `-w` will boot the game in windowed mode which will ease our initial setup and testing later, make sure to remove `-w` to run the game fullscreen once you're done setting up!
+
+ Pictured below, the contents of our `gamestart.bat` file in Notepad++.
+
+
+
+!!! tip ""
+ **FOR DRUM**
+
+ For our drum online network example we're simply doing the above but with different parameters! On our single line, we're going to type `spice64.exe -2ch -p XXXXXXXXXXXXXXXXXXXX -url http://yoururlhere.com/ -w` and save the file.
+
+ What do these different parameters do?
+
+ - `-2ch` enables 2-channel audio for GITADORA
+ - `-p` takes your PCBID on your network of choice, simply replace `XXXXXXXXXXXXXXXXXXXX` with your PCBID.
+ - `-url` allows you to specify a custom service URL to connect with, simply replace `http://yoururlhere.com/` with your chosen network's URL.
+ - `-w` will boot the game in windowed mode which will ease our initial setup and testing later, make sure to remove `-w` to run the game fullscreen once you're done setting up!
+
+ Pictured below, the contents of our `gamestart.bat` file in Notepad++.
+
+
+
+!!! tip ""
+ One final note, since you're playing on a network, you will have one additional step of setting up your card file within your chosen tools, make sure to check your server's information on how to setup a card file.
+
+### Final Steps and Setting up the Game
+
+!!! tip ""
+ The last steps you'll have to do with your chosen tools is simply setting up your desired keybinds! Make sure you setup the `Test` keybind as it will be critical for setting up the game. Once you've done that, launch your game for the first time by double clicking the `.bat` you setup and the game should load.
+
+ If it's your first time running the game, you'll immediately be greeted with this screen, oh no!
+
+
+
+!!! tip ""
+ This is normal, simply hit your `Test` keybind and continue on to this.
+
+
+
+!!! tip ""
+ From here, we will need to set a shop name to play, so select the `GAME OPTIONS` option.
+
+
+
+!!! tip ""
+ Then, select `SHOP SETTINGS`.
+
+
+
+!!! tip ""
+ Once inside, select `SHOP NAME SETTINGS` and name your shop whatever you desire! For the purpose of the guide, we named it `Guide` but highly encourage fun and/or lazy names. Once that's done, go down to `PREFECTURE` and set it to whatever you desire as well. Finally, go to `SAVE AND EXIT` to get back to the main menu.
+
+
+
+!!! tip ""
+ The last menu we'll go inside from the service menu is the clock menu. Go inside `CLOCK` and simply set the clock by hitting `SAVE AND EXIT` as pictured below.
+
+
+
+!!! tip ""
+ You're all done! From the service menu select `GAME MODE` and the game should load ready to be played! Have fun!
+
+!!! warning "Have any other errors?"
+ Check out the [Troubleshooting](troubleshooting.md) section and [Error Code](/errorcodes/konami.md) section to resolve any issues not seen in this guide to greater depth.
diff --git a/docs/games/konami/gitadora/exchain/troubleshooting.md b/docs/games/konami/gitadora/exchain/troubleshooting.md
new file mode 100644
index 0000000..cb6e823
--- /dev/null
+++ b/docs/games/konami/gitadora/exchain/troubleshooting.md
@@ -0,0 +1,74 @@
+
+# Troubleshooting
+
+--8<-- "docs/snippets/common/old_guide.md"
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+## Hardware Specs
+
+!!! tip ""
+ Bemani PC Type 4
+
+ CPU: AMD Athlon 64 X2 4400
+
+ GPU: ATI Radeon HD 2400
+
+ RAM: 1 GB
+
+ OS: Windows 7 Embedded
+
+### My Game Is Running Slow/Lagging
+
+!!! tip ""
+ Make sure you at least meet the above hardware requirements, try to eliminate any unnecessary background processes during play as well.
+
+### My Game Is Running Crazy Fast!
+
+!!! tip ""
+ The most common reason for this is the game is running over its required 60 Hz, the game is hardcoded to run at 60 Hz and this cannot be changed. To solve this, set your monitor's refresh rate to 60 Hz. You can always check on the game's monitor check if the game is fluctuating around 59.94hz, the NTSC standard. If it's not around there and your monitor is indeed set to 60 Hz, consider trying a different panel or forcing vsync on in your GPU's graphics settings.
+
+### Game Stuck On Title Screen (AMD Ryzen 3900X)
+
+!!! tip ""
+ If you have AMD Ryzen 3900X-series processor and the game gets stuck on the title screen (or a black screen) you are running into a known processor bug for games using Media Foundation to play videos. The workaround is to disable simultaneous multithreading (SMT) in the system's BIOS settings. See [this GitHub issue for Proton](https://github.com/ValveSoftware/Proton/issues/838#issuecomment-557081962)
+
+### Occasional Graphical Stuttering During Gameplay
+
+!!! tip ""
+ Disable fullscreen optimizations for spice64.exe instance. Right click on spice64.exe, click on Properties. Click on Compatibility tab, "Change settings for all users", and check "Disable fullscreen optimizations".
+
+### I get an IP Change Error!
+
+!!! tip ""
+ Apply the `Fix IP Change Error` patch.
+
+### Which Offset Is Which?
+
+!!! tip ""
+ If you're getting too many fasts, increase your offset (+). If you're getting too many slows, decrease your offset (-). Gitadora features BOTH a visual offset and an audio based one, so experiment accordingly.
+
+### Why Are My Videos Freezing (Usually Towards the End of the Song)?
+
+!!! tip ""
+ If you're using Windows 10, there is a bug that is caused by the difference between the ASF stream decoder between Windows 7 and Windows 10 wherein it fails to properly detect the end of file of the video stream which causes the video decoder to throw an exception, which is why the video freezes. At the time of writing, SpiceTools does not have a fix for this, but there are hooks available to resolve this issue.
+
+### I Tried Switching to SpiceTools to Follow the Guide and It Crashes!
+
+!!! tip ""
+ This is a known issue, make sure to replace all of the `.dll` files from the ``contents`` folder of the game with ones from a fresh install, other tools currently modify these files in a way that SpiceTools cannot deal with.
+
+### My Drum Pedal Isn't Working!
+
+!!! tip ""
+ Some drum kits utilize hi-hat control with the pedal resulting in different MIDI addresses that require additional bindings, make sure to follow your drum kit's manual to see these other bindings and bind them in your desired tool's accordingly. Gitadora does not do this, so the game utilizes just 1 binding for every level of sensitivity on the pedal and multiple bindings are typically required with most drum kits.
+
+### When I Run This Game All Other Background Audio Is Gone! What's Going On?
+
+!!! tip ""
+ Gitadora is a 64-bit game that utilizes a feature in Windows called [WASAPI exclusive mode](https://docs.microsoft.com/en-us/windows/win32/coreaudio/exclusive-mode-streams) to obtain less audio latency than the former 32-bit versions of BEMANI games which used [DirectSound](https://en.wikipedia.org/wiki/DirectSound). Unfortunately, this cannot be changed.
+
+### Note on 2-channel and 4-channel Audio
+
+!!! tip ""
+ For most setups, the `-2ch` parameter will be mandatory to hear any functional audio. 4-channel setups aren't really working in general and there's buffer issues, please avoid using it.
diff --git a/docs/games/konami/gitadora/fuzzup/setup.md b/docs/games/konami/gitadora/fuzzup/setup.md
new file mode 100644
index 0000000..a817d53
--- /dev/null
+++ b/docs/games/konami/gitadora/fuzzup/setup.md
@@ -0,0 +1,253 @@
+
+# Game Setup
+
+--8<-- "docs/snippets/common/old_guide.md"
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+## Installing spice2x
+
+!!! info ""
+
+ If you already have spice2x installed, make sure it is up to date!
+
+!!! tip ""
+
+ - Head over to [spice2x.github.io](https://spice2x.github.io) and download the latest release.
+ - Extract the `spice64.exe` and `spicecfg.exe` files from the archive to your game's directory.
+
+ 
+
+## General Configuration
+
+!!! info ""
+
+ Since GITADORA has a separate mode for both Guitar and Drums, the configuration will be split into three sections.
+
+ Next you need a card number.
+ If you don't already have one, generate one in the `Cards` tab.
+ To keep your card number safe, create a new `.txt` file with ONLY it inside.
+
+ Once that's done, head to the `Cards` tab, for `Player 1` click `Open...` and point to your text file.
+
+ 
+
+??? tip "Local e-amuse Emulator (Asphyxia)"
+
+ This is covered in the [Asphyxia CORE](/extras/asphyxia.md) page.
+
+## Pre-launch Requirements
+
+!!! info "These steps are required, otherwise your game won't run"
+
+### VCRedist & DirectX
+
+!!! tip ""
+
+ - Download and install the latest [VCRedist](https://www.techpowerup.com/download/visual-c-redistributable-runtime-package-all-in-one/)
+ - Download and install the [DirectX End-User Runtimes](https://www.microsoft.com/en-us/download/details.aspx?id=8109)
+
+### Audio
+
+!!! info "GITADORA FUZZ-UP currently only supports WASAPI exclusive mode"
+
+!!! tip ""
+
+ - Open `spicecfg.exe`.
+ - At the very top, click on `Shortcuts` then `Audio Playback Devices`.
+ - In the popup window, right click on your default audio device, and click on `Properties`.
+ - Go to the `Advanced` tab.
+ - Check both boxes under `Exclusive Mode`.
+ - Open the `Default Format` dropdown.
+ - Pick the `24 bit, 44100 Hz (Studio Quality)` option and click `Apply` then `OK`.
+
+
+
+## First Launch
+
+!!! danger "If you have any issues running the game at this point, refer to the [Troubleshooting](troubleshooting.md) page"
+
+!!! tip ""
+
+ If you've followed all instructions correctly, you're finally ready to launch the game!
+
+ First, ensure your guitar or drumkit is connected and run `spice64.exe`. Press `Yes` when it asks for elevated privileges.
+
+ Upon launching your game, you will be greeted with this `BACKUP DATA ERROR` screen.
+
+
+
+!!! tip ""
+
+ This is normal, simply hit your `Test` keybind to enter test mode.
+
+
+
+!!! tip ""
+
+ From here, we will need to set a shop name to play, so select the `GAME OPTIONS` option.
+
+
+
+!!! tip ""
+
+ Then, select `SHOP SETTINGS`.
+
+
+
+!!! tip ""
+
+ Once inside, select `SHOP NAME SETTINGS` and name your shop whatever you desire! Once that's done, go down to `PREFECTURE` and set it to whatever you desire as well. Finally, go to `SAVE AND EXIT` to get back to the test menu.
+
+
+
+!!! tip ""
+
+ The last menu we'll go inside from the test menu is the clock menu. Go inside `CLOCK` and simply set the clock by hitting `SAVE AND EXIT` as pictured below.
+
+
+
+!!! tip ""
+
+ You're all done! From the test menu, select `GAME MODE` and the game should boot up!
+
+## Carding In
+
+!!! tip ""
+
+ Once the game is done loading, you need to card in.
+
+ - Press your `Keypad Insert Card` button.
+ - Enter your code using your keypad binds.
+
+## Troubleshooting
+
+!!! warning "Have any other issue?"
+
+ Check out the [Troubleshooting](troubleshooting.md) and [Error Codes](/errorcodes/konami.md) pages.
diff --git a/docs/games/konami/gitadora/fuzzup/troubleshooting.md b/docs/games/konami/gitadora/fuzzup/troubleshooting.md
new file mode 100644
index 0000000..01433e9
--- /dev/null
+++ b/docs/games/konami/gitadora/fuzzup/troubleshooting.md
@@ -0,0 +1,61 @@
+
+# Troubleshooting
+
+--8<-- "docs/snippets/common/old_guide.md"
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+### I'm having performance issues!
+
+!!! tip ""
+
+ If you're having performance issues of some kind, spice2x's [PC optimization](https://github.com/spice2x/spice2x.github.io/wiki/PC-optimization) guide is worth looking at.
+
+### My game is running too fast!
+
+!!! tip ""
+
+ The most common reason for this is the game is running over its required refresh rate.
+
+ To solve this, ensure the monitor running GITADORA FUZZ-UP is set to 60 Hz. This is a requirement for the game to run at the correct speed. The game is hardcoded to run at 60 Hz and there is no way to change this.
+
+ In addition, make sure v-sync isn't disabled in your graphics card's settings.
+
+ For NVIDIA users, enable `NVIDIA profile optimization (-nvprofile)` in the `Options` tab.
+
+### There's occasional graphical stuttering during gameplay!
+
+!!! tip ""
+
+ To fix this, you need to disable fullscreen optimizations for `spice64.exe`.
+
+ 1. Right click on `spice64.exe` and select `Properties`.
+ 2. Go to the `Compatibility` tab.
+ 3. Click the box at the bottom that says `Change settings for all users`.
+ 4. Check the box that says `Disable fullscreen optimizations`.
+ 5. Click `Apply` and then `OK`.
+
+### How do I adjust my offset?
+
+!!! tip ""
+
+ Play through a chart you're comfortable with.
+
+ If you're getting too many `Fast`, increase your offset `(+)`.
+ If you're getting too many `Slow`, decrease your offset `(-)`.
+
+ GITADORA FUZZ-UP has two types of offset adjustments, visual and audio based, so be sure to fiddle with both to find desirable settings.
+
+### When I run the game, all other audio is gone!
+
+!!! tip ""
+
+ GITADORA FUZZ-UP uses [WASAPI exclusive mode](https://docs.microsoft.com/en-us/windows/win32/coreaudio/exclusive-mode-streams) for better audio latency.
+
+ There is currently no patch available to run the game in shared mode, so you will need to use a separate audio device for the game if you want to hear other audio sources while playing.
+
+### I want to use 4-channel audio! Why isn't it working?
+
+!!! tip ""
+
+ Unfortunately, most setups do not properly function with GITADORA FUZZ-UP's 4-channel audio, and the `-2ch` parameter will be mandatory to hear any audio. There are not many setups working with 4-channel audio, and there are buffer issues related to it. Please avoid using it.
\ No newline at end of file
diff --git a/docs/games/konami/gitadora/matixx/setup.md b/docs/games/konami/gitadora/matixx/setup.md
new file mode 100644
index 0000000..56940d5
--- /dev/null
+++ b/docs/games/konami/gitadora/matixx/setup.md
@@ -0,0 +1,137 @@
+
+# Game Setup
+
+--8<-- "docs/snippets/common/old_guide.md"
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+### Getting Started.
+
+!!! tip ""
+ Before we even touch the game, let's fiddle with our audio settings to minimize any potential audio issues on startup. In Windows, go to `Playback Devices` and then right click on your default device and go to `Properties`. From there, hit the `Advanced` tab and set your `Default Format` to `44100 Hz` and check both of the options inside `Exclusive Mode` as pictured.
+
+
+
+!!! tip ""
+ Once that's done, it's time to work on setting up your data.
+
+ After downloading your data, the first thing to do is make sure your files aren't set to READ ONLY, make sure to uncheck it from the main folder in the Windows Properties tab if so. Then, the first thing to do is put your desired 64-bit tools inside the game's `contents` folder, and to create a `.bat` file. Pictured below is what your folder should look like, feel free to name your `.bat` file whatever you desire, for the sake of convenience we've named ours `gamestart.bat`.
+
+
+
+### Configuring Your Tools
+
+!!! tip ""
+ Now that you have your files ready, open up your `.bat` file in your desired text editor (we're using [Notepad++](https://notepad-plus-plus.org/)) and edit it with your desired parameters, for the purpose of this guide we will demonstrate both a local network configuration and an online example below for both launching the guitar version and drum version using SpiceTools, skip to whichever you're in need of accordingly and please keep in mind you can add whatever additional parameters you desire.
+
+!!! warning "If you're not using SpiceTools:"
+ The overall structure of your .bat file will differ from the guide, namely the initialization of SpiceTools won't be present and potential parameters may differ. As stated above, make sure to check the documentation of your tools to ensure you're using the correct parameters for your needs.
+
+### Configuring for a Local Network
+
+!!! tip ""
+ **FOR GUITAR**
+
+ For our guitar local network configuration example, on a single line in the `.bat` file we're going to type `spice64.exe -e prop\eamuse-config2.xml -2ch -ea -w` and save the file.
+
+ What do these different parameters do?
+ - `-e` sets a custom path for the eamuse config to boot the proper one (in this case, guitar via `prop\eamuse-config2.xml`)
+ - `-2ch` enables 2-channel audio for GITADORA
+ - `-ea` enables an integrated e-amusement server within SpiceTools.
+ - `-w` will boot the game in windowed mode which will ease our initial setup and testing later, make sure to remove `-w` to run the game fullscreen once you're done setting up!
+
+ Pictured below, the contents of our `gamestart.bat` file in Notepad++.
+
+
+
+!!! tip ""
+ **FOR DRUM**
+
+ For our drum local network configuration example, on a single line in the `.bat` file we're going to type `spice64.exe -2ch -ea -w` and save the file.
+
+ What do these different parameters do?
+ - `-2ch` enables 2-channel audio for GITADORA
+ - `-ea` enables an integrated e-amusement server within SpiceTools.
+ - `-w` will boot the game in windowed mode which will ease our initial setup and testing later, make sure to remove `-w` to run the game fullscreen once you're done setting up!
+
+ Pictured below, the contents of our `gamestart.bat` file in Notepad++.
+
+
+
+### Configuring for an Online Network
+
+!!! tip ""
+ **FOR GUITAR**
+
+ For our guitar online network example we're simply doing the above but with different parameters! On our single line, we're going to type `spice64.exe -e prop\eamuse-config2.xml -2ch -p XXXXXXXXXXXXXXXXXXXX -url http://yoururlhere.com/ -w` and save the file.
+
+ What do these different parameters do?
+
+ - `-e` sets a custom path for the eamuse config to boot the proper one (in this case, guitar via `prop\eamuse-config2.xml`)
+ - `-2ch` enables 2-channel audio for GITADORA
+ - `-p` takes your PCBID on your network of choice, simply replace `XXXXXXXXXXXXXXXXXXXX` with your PCBID.
+ - `-url` allows you to specify a custom service URL to connect with, simply replace `http://yoururlhere.com/` with your chosen network's URL.
+ - `-w` will boot the game in windowed mode which will ease our initial setup and testing later, make sure to remove `-w` to run the game fullscreen once you're done setting up!
+
+ Pictured below, the contents of our `gamestart.bat` file in Notepad++.
+
+
+
+!!! tip ""
+ **FOR DRUM**
+
+ For our drum online network example we're simply doing the above but with different parameters! On our single line, we're going to type `spice64.exe -2ch -p XXXXXXXXXXXXXXXXXXXX -url http://yoururlhere.com/ -w` and save the file.
+
+ What do these different parameters do?
+
+ - `-2ch` enables 2-channel audio for GITADORA
+ - `-p` takes your PCBID on your network of choice, simply replace `XXXXXXXXXXXXXXXXXXXX` with your PCBID.
+ - `-url` allows you to specify a custom service URL to connect with, simply replace `http://yoururlhere.com/` with your chosen network's URL.
+ - `-w` will boot the game in windowed mode which will ease our initial setup and testing later, make sure to remove `-w` to run the game fullscreen once you're done setting up!
+
+ Pictured below, the contents of our `gamestart.bat` file in Notepad++.
+
+
+
+!!! tip ""
+ One final note, since you're playing on a network, you will have one additional step of setting up your card file within your chosen tools, make sure to check your server's information on how to setup a card file.
+
+### Final Steps and Setting up the Game
+
+!!! tip ""
+ The last steps you'll have to do with your chosen tools is simply setting up your desired keybinds! Make sure you setup the `Test` keybind as it will be critical for setting up the game. Once you've done that, launch your game for the first time by double clicking the `.bat` you setup and the game should load.
+
+ If it's your first time running the game, you'll immediately be greeted with this screen, oh no!
+
+
+
+!!! tip ""
+ This is normal, simply hit your `Test` keybind and continue on to this.
+
+
+
+!!! tip ""
+ From here, we will need to set a shop name to play, so select the `GAME OPTIONS` option.
+
+
+
+!!! tip ""
+ Then, select `SHOP SETTINGS`.
+
+
+
+!!! tip ""
+ Once inside, select `SHOP NAME SETTINGS` and name your shop whatever you desire! For the purpose of the guide, we named it `Guide` but highly encourage fun and/or lazy names. Once that's done, go down to `PREFECTURE` and set it to whatever you desire as well. Finally, go to `SAVE AND EXIT` to get back to the main menu.
+
+
+
+!!! tip ""
+ The last menu we'll go inside from the service menu is the clock menu. Go inside `CLOCK` and simply set the clock by hitting `SAVE AND EXIT` as pictured below.
+
+
+
+!!! tip ""
+ You're all done! From the service menu select `GAME MODE` and the game should load ready to be played! Have fun!
+
+!!! warning "Have any other errors?"
+ Check out the [Troubleshooting](troubleshooting.md) section and [Error Code](/errorcodes/konami.md) section to resolve any issues not seen in this guide to greater depth.
diff --git a/docs/games/konami/gitadora/matixx/troubleshooting.md b/docs/games/konami/gitadora/matixx/troubleshooting.md
new file mode 100644
index 0000000..fd4d7c4
--- /dev/null
+++ b/docs/games/konami/gitadora/matixx/troubleshooting.md
@@ -0,0 +1,74 @@
+
+# Troubleshooting
+
+--8<-- "docs/snippets/common/old_guide.md"
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+## Hardware Specs
+
+!!! tip ""
+ Bemani PC Type 4
+
+ CPU: AMD Athlon 64 X2 4400
+
+ GPU: ATI Radeon HD 2400
+
+ RAM: 1 GB
+
+ OS: Windows 7 Embedded
+
+### My Game Is Running Slow/Lagging
+
+!!! tip ""
+ Make sure you at least meet the above hardware requirements, try to eliminate any unnecessary background processes during play as well.
+
+### My Game Is Running Crazy Fast!
+
+!!! tip ""
+ The most common reason for this is the game is running over its required 60 Hz, the game is hardcoded to run at 60 Hz and this cannot be changed. To solve this, set your monitor's refresh rate to 60 Hz. You can always check on the game's monitor check if the game is fluctuating around 59.94hz, the NTSC standard. If it's not around there and your monitor is indeed set to 60 Hz, consider trying a different panel or forcing vsync on in your GPU's graphics settings.
+
+### Game Stuck On Title Screen (AMD Ryzen 3900X)
+
+!!! tip ""
+ If you have AMD Ryzen 3900X-series processor and the game gets stuck on the title screen (or a black screen) you are running into a known processor bug for games using Media Foundation to play videos. The workaround is to disable simultaneous multithreading (SMT) in the system's BIOS settings. See [this GitHub issue for Proton](https://github.com/ValveSoftware/Proton/issues/838#issuecomment-557081962)
+
+### Occasional Graphical Stuttering During Gameplay
+
+!!! tip ""
+ Disable fullscreen optimizations for spice64.exe instance. Right click on spice64.exe, click on Properties. Click on Compatibility tab, "Change settings for all users", and check "Disable fullscreen optimizations".
+
+### I get an IP Change Error!
+
+!!! tip ""
+ Apply the `Fix IP Change Error` patch.
+
+### Which Offset Is Which?
+
+!!! tip ""
+ If you're getting too many fasts, increase your offset (+). If you're getting too many slows, decrease your offset (-). Gitadora features BOTH a visual offset and an audio based one, so experiment accordingly.
+
+### Why Are My Videos Freezing (Usually Towards the End of the Song)?
+
+!!! tip ""
+ If you're using Windows 10, there is a bug that is caused by the difference between the ASF stream decoder between Windows 7 and Windows 10 wherein it fails to properly detect the end of file of the video stream which causes the video decoder to throw an exception, which is why the video freezes. At the time of writing, SpiceTools does not have a fix for this, but there are hooks available to resolve this issue.
+
+### I Tried Switching to SpiceTools to Follow the Guide and It Crashes!
+
+!!! tip ""
+ This is a known issue, make sure to replace all of the `.dll` files from the ``contents`` folder of the game with ones from a fresh install, other tools currently modify these files in a way that SpiceTools cannot deal with.
+
+### My Drum Pedal Isn't Working!
+
+!!! tip ""
+ Some drum kits utilize hi-hat control with the pedal resulting in different MIDI addresses that require additional bindings, make sure to follow your drum kit's manual to see these other bindings and bind them in your desired tool's accordingly. Gitadora does not do this, so the game utilizes just 1 binding for every level of sensitivity on the pedal and multiple bindings are typically required with most drum kits.
+
+### When I Run This Game All Other Background Audio Is Gone! What's Going On?
+
+!!! tip ""
+ Gitadora is a 64-bit game that utilizes a feature in Windows called [WASAPI exclusive mode](https://docs.microsoft.com/en-us/windows/win32/coreaudio/exclusive-mode-streams) to obtain less audio latency than the former 32-bit versions of BEMANI games which used [DirectSound](https://en.wikipedia.org/wiki/DirectSound). Unfortunately, this cannot be changed.
+
+### Note on 2-channel and 4-channel Audio
+
+!!! tip ""
+ For most setups, the `-2ch` parameter will be mandatory to hear any functional audio. 4-channel setups aren't really working in general and there's buffer issues, please avoid using it.
diff --git a/docs/games/konami/iidx/10thstyle/setup.md b/docs/games/konami/iidx/10thstyle/setup.md
new file mode 100644
index 0000000..946f649
--- /dev/null
+++ b/docs/games/konami/iidx/10thstyle/setup.md
@@ -0,0 +1,295 @@
+
+# Game Setup
+
+--8<-- "docs/snippets/common/old_guide.md"
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+## Preparing data
+
+!!! tip ""
+
+ After downloading and extracting your data, we need to make sure your files aren't set to `Read-only`.
+
+ - Right click the folder containing your data, then click on `Properties`.
+ - In the `General` tab go down to `Attributes`, untick `Read-only` and click `Apply`.
+ - A popup will appear, select `Apply changes to this folder, subfolder and files` and press `OK`.
+ - Finally, click `OK` again to exit out of properties.
+
+## Installing Bemanitools
+
+!!! tip ""
+
+ - Download :material-package-down:[Bemanitools](https://github.com/djhackersdev/bemanitools/releases/download/5.48/bemanitools-5.48.zip).
+
+ - Inside :material-zip-box:`bemanitools-5.48.zip` locate :material-zip-box:`iidx-09-to-12.zip`.
+
+ - Extract everything inside the folder that contains the :material-file:`bm2dx.exe` which is located in :material-folder:`\D01\JAE`.
+
+ Pictured below is what your folder should look like. We've removed any files not necessary for **10th style**.
+
+
+
+### Using iidxhook-10.conf & RtEffect.dll
+
+!!! tip ""
+
+ - Download the :material-package-down:[Bemanitools supplements](https://github.com/djhackersdev/bemanitools-supplement/releases/download/1.6/bemanitools-supplement-1.6.zip)
+
+ - Open :material-zip-box:`bemanitools-supplement-v1.6.zip` and navigate inside :material-zip-box:`misc.zip`
+
+ - Inside :material-folder:`misc\d3d8to9`, extract :material-file-cog-outline:`d3d8.dll` to :material-folder:`\D01\JAE`.
+
+ This enables us to use the graphic options inside :material-file-code:`iidxhook-10.conf` which we will take advantage of.
+
+ - Open :material-zip-box:`bemanitools-supplement-v1.6.zip` and navigate inside :material-zip-box:`iidx.zip`
+
+ - Inside :material-folder:`iidx/misc`, extract :material-file-cog-outline:`RtEffect_stub.dll` to :material-folder:`\D01\JAE`.
+
+ - Delete the already existing :material-file-remove-outline:`RtEffect.dll` and rename :material-file-edit-outline:`RtEffect_stub.dll` to :material-file-cog-outline:`RtEffect.dll`.
+
+ This will eliminate any immediate crashes relating to needing specific old hardware.
+
+### Replacing bm2dx.exe
+
+!!! tip ""
+
+ - Go to :material-folder:`D01\util` and copy :material-clipboard-file:`bm2dx_D01_JAE_no_checksum.exe` to `D01\JAE`
+
+ - Delete the original :material-file-remove:`bm2dx.exe`
+
+ - Rename :material-file-edit:`bm2dx_D01_JAE_no_checksum.exe` to :material-file:`bm2dx.exe`
+
+ If you don't do this, you will end up getting a `HDD DATA ERROR (PROG CHKSUM)` which will result in the game not being able to run.
+
+## Configuring Bemanitools
+
+!!! info "To configure your keybinds, open your :material-file:`config.bat` file"
+
+### Buttons
+
+!!! tip ""
+
+ Double click on the right on a button that you wish to bind, then press the key you want associated with the action.
+
+ With your controller and/or keyboard plugged in, configure your keys for:
+
+ - **Maintenance**: `Service, Test`
+ - **P1 Game buttons**: `1 to 7, Start, EFFECT, VEFX`
+ - **P1 Keypad**: `Keypad Insert Card`
+
+ **Only if** you're playing using a keyboard:
+
+ - **Turntable**: `TT+, TT-` **and optionally** `TT+/-` which alternates between `TT+` and `TT-` on each press.
+
+### Analogs (controller/cab only)
+
+!!! tip ""
+
+ With a controller rather than binding buttons to `TT+` and `TT-`, you need to:
+
+ - Head to the `Analogs` tab at the top.
+ - In `Device`, pick your controller.
+ - In `Control`, pick whichever one corresponds to the turntable.
+ - Turn your turntable ensuring that the preview turns along with it.
+ - Click `OK`, leaving the rest of the settings alone.
+
+### Lights (controller/cab only)
+
+!!! tip ""
+
+ Your controller might support having its lights controlled by the game through bemanitools.
+
+ If it does, here's how you may link different actions to your lights:
+
+ - In `Device`, pick your controller.
+ - In `Game Light`, select the corresponding button that will be used for that light.
+ - Repeat for your other lights.
+
+### Configuring Bemanitools for a network
+
+!!! tip "Head over to the `Network` tab"
+
+!!! tip ""
+ Now we will set up our PIN pad and card.
+
+ - Click on `Keyboard device`
+ - You may or may not have more than one option. To figure out which one is your actual keyboard, select a device inside that list and press a button on the numpad.
+ - Once you have found your correct device, the `Keyboard status` will change **(the number and location of the number does not matter, it only matters that it changed)**.
+ - Grab your card, create a :material-file-document-edit:`.txt` and name it however you like. In this example it's called :material-file-document-edit:`card.txt`
+ - Place the file in a location that is easily accessible and you won't forget. In this case it's in a seperate folder.
+
+!!! info "If you don't have a numpad, make sure to tick `Use top keyboard row for PIN pad input`. This will also change the `Card In` button to `Backspace`"
+
+
+
+## Connecting to a network
+
+!!! tip ""
+
+ - Locate your :material-file-code:`iidxhook-10.conf`
+
+ - Open it with your desired text editor (we're using [Notepad++](https://notepad-plus-plus.org/))
+
+ - Replace the `eamuse.server=localhost:80` with your desired network URL
+
+ - Replace `eamuse.pcbid=XXXXXXXXXXXXXXXXXXXX` **and** `eamuse.eamid=XXXXXXXXXXXXXXXXXXXX` with your PCBID of your network of choice.
+
+ ```
+ # URL (e.g. http://my.eamuse.server:80/whatever) or IPV4 (e.g. 127.0.0.1:80) of the target eamuse server. The port is optional but defaults to 80.
+ eamuse.server=localhost:80
+
+ # PCBID
+ eamuse.pcbid=XXXXXXXXXXXXXXXXXXXX
+
+ # EAMID
+ eamuse.eamid=XXXXXXXXXXXXXXXXXXXX
+ ```
+
+## Game resolution and locking FPS
+
+!!! tip ""
+ We'd like to mention that there are two options when it comes to how the game renders. You can choose between `Linear` and `Point`.
+
+ Below is an example of how both look like.
+
+ ??? info "Linear"
+ 
+
+ ??? info "Point"
+ 
+
+ It comes down to your own prefrence what you decide on, `Linear` is less sharp but doesn't have pixel perfect edges. `Point` is sharp and is pixel perfect.
+
+!!! tip ""
+ Next up, we'll setup borderless window and configure the proper resolution. We're using a `1920x1080` monitor so we will use that.
+
+ Repeat the previous step and open your :material-file-code:`iidxhook-10.conf`. We want to find these lines:
+
+ ```
+ # Run the game windowed
+ gfx.windowed=false
+
+ # Windowed width, 0 for default size
+ gfx.window_width=0
+
+ # Windowed height, 0 for default size
+ gfx.window_height=0
+
+ # Up-/downscale the back buffer's width. This does not change the game's rendering resolution but scales the final frame. Use this to target the native resolution of your monitor/TV, e.g. to avoid over-/underscan, bad image quality or latency caused by the monitors internal upscaler. 0 to disable this feature. Must be set in combination with the corresponding height parameter.
+ gfx.scale_back_buffer_width=0
+
+ # Up-/downscale the back buffer's height. This does not change the game's rendering resolution but scales the final frame. Use this to target the native resolution of your monitor/TV, e.g. to avoid over-/underscan, bad image quality or latency caused by the monitors internal upscaler. 0 to disable this feature. Must be set in combination with the corresponding width parameter.
+ gfx.scale_back_buffer_height=0
+
+ # Filter type to use for up-/downscaling the back buffer. Only used if scaling feature was enabled by setting the scaling width and height parameters. Available types: none, linear, point (refer to D3DTEXTUREFILTERTYPE for explanation).
+ gfx.scale_back_buffer_filter=none
+ ```
+
+ If you can't seem to find them, press `CTRL` + `F` and search for `gfx.frame_rate_limit=0.0`. This will bring you to the first line we want to edit.
+
+!!! tip ""
+ Listed below are the values we want to change them to.
+
+ ```
+ gfx.frame_rate_limit=59.95
+ gfx.windowed=true
+ gfx.window_width=1920
+ gfx.window_height=1080
+ gfx.scale_back_buffer_width=1920
+ gfx.scale_back_buffer_height=1080
+ gfx.scale_back_buffer_filter=point
+ ```
+ Unless you'd like to have the game properly windowed you can safely ignore `gfx.framed=false`.
+
+ Make sure to decide on whether you want `Linear` or `Point` rendering.
+
+ ```
+ gfx.scale_back_buffer_filter=linear
+ gfx.scale_back_buffer_filter=point
+ ```
+
+## First launch
+
+!!! danger "If you have any issues running the game, refer to the [Troubleshooting](troubleshooting.md) page"
+
+### BACKUP DATA
+
+!!! tip ""
+
+ If you've followed all instructions correctly, you're now finally ready to launch the game!
+
+ **First plug your controller if you have one** and run :material-file:`gamestart.bat`.
+
+ If it's your first time running the game, you'll immediately be greeted with this screen.
+
+
+
+
+
+!!! tip ""
+ Press your `Start` key to confirm to get to the next error message.
+
+### CLOCK ERROR
+
+
+
+!!! tip ""
+ Press your `Start` key to confirm. This will bring you into it's service menu.
+
+
+
+!!! tip ""
+ Instructions on how to navigate the menu are shown at the bottom of the screen.
+
+ - Press `1` and `2` to go up and down.
+ - Press `6` to select/execute.
+
+ Navigate to `CLOCK`. You do not need to manually change it. Navigate to `SAVE AND EXIT`.
+
+
+
+### Enabling e-AMUSEMENT for Online Play
+
+!!! tip ""
+ From the service menu, go to `e-AMUSEMENT OPTIONS` then `e-AMUSEMENT SETTINGS`.
+
+
+
+
+
+!!! tip ""
+ It'll bring you to this screen, change it so that `e-AMUSEMENT` switches to `ON` and it will look like this:
+
+
+
+
+
+!!! tip ""
+ We will need to set a `SHOP NAME SETTING` and change our `PREFECTURE` otherwise the game will throw errors at us.
+
+
+
+!!! tip ""
+
+ - Name your shop to whatever you'd like. Instructions on how to navigate are at the bottom of the screen.
+ - Navigate to `EXIT` and select it.
+ - Change your prefecture once or how many times you'd like, it doesn't matter as long as it's not the default one.
+
+
+
+!!! tip ""
+ Select `SAVE AND EXIT`. The game will now give you a message, which translated means:
+
+ `e-AMUSEMENT settings have been changed. Please turn the power off and on again.`
+
+ So, close the game and open it again.
+
+
+
+## Final Notes
+
+!!! success "You're all done! Make sure to insert two credits by pressing your `SERVICE` key. Have fun!"
+
+!!! warning "Have any other errors?"
+ Check out the [Troubleshooting](troubleshooting.md) section.
\ No newline at end of file
diff --git a/docs/games/konami/iidx/10thstyle/troubleshooting.md b/docs/games/konami/iidx/10thstyle/troubleshooting.md
new file mode 100644
index 0000000..4d0374c
--- /dev/null
+++ b/docs/games/konami/iidx/10thstyle/troubleshooting.md
@@ -0,0 +1,62 @@
+
+# Troubleshooting
+
+--8<-- "docs/snippets/common/old_guide.md"
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+### My Game Is Running Crazy Fast!
+
+!!! tip ""
+ The most common reason for this is the game is running over its required 59.95hz, the game is hardcoded to run at 59.95hz and this cannot be changed. To solve this, check [Game resolution and locking FPS](setup.md#game-resolution-and-locking-fps) again.
+
+### I'm getting "NETWORK WARNING" instead of "NETWORK OK"
+
+!!! tip ""
+ This can be caused by:
+
+ - Invalid PCBID
+ - Firewall blocking connections
+ - Invalid eamuse url or port specified
+ - Game is not run using the Administrator account
+
+### My background videos aren't working!
+
+!!! tip ""
+
+ You need to install a codec.
+
+ - Open :material-zip-box:`bemanitools-supplement-v1.6.zip` and navigate to :material-folder:`\iidx.zip\iidx\misc\` where :material-file:`CLVSD.ax` is located.
+
+ - Extract :material-file:`CLVSD.ax` inside a :material-folder: folder that you know won't be moved or renamed.
+
+ - Open the :material-console:command prompt as ***administrator***. Now type `regsvr32 "
+# Game Setup
+
+--8<-- "docs/snippets/common/old_guide.md"
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+## Preparing data
+
+!!! tip ""
+
+ After downloading and extracting your data, we need to make sure your files aren't set to `Read-only`.
+
+ - Right click the folder containing your data, then click on `Properties`.
+ - In the `General` tab go down to `Attributes`, untick `Read-only` and click `Apply`.
+ - A popup will appear, select `Apply changes to this folder, subfolder and files` and press `OK`.
+ - Finally, click `OK` again to exit out of properties.
+
+## Installing Bemanitools
+
+!!! tip ""
+
+ - Download :material-package-down:[Bemanitools](https://github.com/djhackersdev/bemanitools/releases/download/5.48/bemanitools-5.48.zip).
+
+ - Inside :material-zip-box:`bemanitools-5.48.zip` locate :material-zip-box:`iidx-09-to-12.zip`.
+
+ - Extract everything inside the folder that contains the :material-file:`bm2dx.exe` which is located in :material-folder:`\E11\JAA`.
+
+ Pictured below is what your folder should look like. We've removed any files not necessary for **IIDX RED**.
+
+
+
+### Using iidxhook-11.conf & RtEffect.dll
+
+!!! tip ""
+
+ - Download the :material-package-down:[Bemanitools supplements](https://github.com/djhackersdev/bemanitools-supplement/releases/download/1.6/bemanitools-supplement-1.6.zip)
+
+ - Open :material-zip-box:`bemanitools-supplement-v1.6.zip` and navigate inside :material-zip-box:`misc.zip`
+
+ - Inside :material-folder:`misc\d3d8to9`, extract :material-file-cog-outline:`d3d8.dll` to :material-folder:`\E11\JAA`.
+
+ This enables us to use the graphic options inside :material-file-code:`iidxhook-11.conf` which we will take advantage of.
+
+ - Open :material-zip-box:`bemanitools-supplement-v1.6.zip` and navigate inside :material-zip-box:`iidx.zip`
+
+ - Inside :material-folder:`iidx/misc`, extract :material-file-cog-outline:`RtEffect_stub.dll` to :material-folder:`\E11\JAA`.
+
+ - Delete the already existing :material-file-remove-outline:`RtEffect.dll` and rename :material-file-edit-outline:`RtEffect_stub.dll` to :material-file-cog-outline:`RtEffect.dll`.
+
+ This will eliminate any immediate crashes relating to needing specific old hardware.
+
+## Configuring Bemanitools
+
+!!! info "To configure your keybinds, open your :material-file:`config.bat` file"
+
+### Buttons
+
+!!! tip ""
+
+ Double click on the right on a button that you wish to bind, then press the key you want associated with the action.
+
+ With your controller and/or keyboard plugged in, configure your keys for:
+
+ - **Maintenance**: `Service, Test`
+ - **P1 Game buttons**: `1 to 7, Start, EFFECT, VEFX`
+ - **P1 Keypad**: `Keypad Insert Card`
+
+ **Only if** you're playing using a keyboard:
+
+ - **Turntable**: `TT+, TT-` **and optionally** `TT+/-` which alternates between `TT+` and `TT-` on each press.
+
+### Analogs (controller/cab only)
+
+!!! tip ""
+
+ With a controller rather than binding buttons to `TT+` and `TT-`, you need to:
+
+ - Head to the `Analogs` tab at the top.
+ - In `Device`, pick your controller.
+ - In `Control`, pick whichever one corresponds to the turntable.
+ - Turn your turntable ensuring that the preview turns along with it.
+ - Click `OK`, leaving the rest of the settings alone.
+
+### Lights (controller/cab only)
+
+!!! tip ""
+
+ Your controller might support having its lights controlled by the game through bemanitools.
+
+ If it does, here's how you may link different actions to your lights:
+
+ - In `Device`, pick your controller.
+ - In `Game Light`, select the corresponding button that will be used for that light.
+ - Repeat for your other lights.
+
+### Configuring Bemanitools for a network
+
+!!! tip "Head over to the `Network` tab"
+
+!!! tip ""
+ Now we will set up our PIN pad and card.
+
+ - Click on `Keyboard device`
+ - You may or may not have more than one option. To figure out which one is your actual keyboard, select a device inside that list and press a button on the numpad.
+ - Once you have found your correct device, the `Keyboard status` will change **(the number and location of the number does not matter, it only matters that it changed)**.
+ - Grab your card, create a :material-file-document-edit:`.txt` and name it however you like. In this example it's called :material-file-document-edit:`card.txt`
+ - Place the file in a location that is easily accessible and you won't forget. In this case it's in a seperate folder.
+
+!!! info "If you don't have a numpad, make sure to tick `Use top keyboard row for PIN pad input`. This will also change the `Card In` button to `Backspace`"
+
+
+
+## Connecting to a network
+
+!!! tip ""
+
+ - Locate your :material-file-code:`iidxhook-11.conf`
+
+ - Open it with your desired text editor (we're using [Notepad++](https://notepad-plus-plus.org/))
+
+ - Replace the `eamuse.server=localhost:80` with your desired network URL
+
+ - Replace `eamuse.pcbid=XXXXXXXXXXXXXXXXXXXX` **and** `eamuse.eamid=XXXXXXXXXXXXXXXXXXXX` with your PCBID of your network of choice.
+
+ ```
+ # URL (e.g. http://my.eamuse.server:80/whatever) or IPV4 (e.g. 127.0.0.1:80) of the target eamuse server. The port is optional but defaults to 80.
+ eamuse.server=localhost:80
+
+ # PCBID
+ eamuse.pcbid=XXXXXXXXXXXXXXXXXXXX
+
+ # EAMID
+ eamuse.eamid=XXXXXXXXXXXXXXXXXXXX
+ ```
+
+## Game resolution and locking FPS
+
+!!! tip ""
+ We'd like to mention that there are two options when it comes to how the game renders. You can choose between `Linear` and `Point`.
+
+ Below is an example of how both look like.
+
+ ??? info "Linear"
+ 
+
+ ??? info "Point"
+ 
+
+ It comes down to your own prefrence what you decide on, `Linear` is less sharp but doesn't have pixel perfect edges. `Point` is sharp and is pixel perfect.
+
+!!! tip ""
+ Next up, we'll setup borderless window and configure the proper resolution. We're using a `1920x1080` monitor so we will use that.
+
+ Repeat the previous step and open your :material-file-code:`iidxhook-11.conf`. We want to find these lines:
+
+ ```
+ # Software limit the frame rate of the rendering loop in hz, e.g. 60 or 59.95 (0.0 = no software limit)
+ gfx.frame_rate_limit=0.0
+
+ # Run the game windowed
+ gfx.windowed=false
+
+ # Windowed width, 0 for default size
+ gfx.window_width=0
+
+ # Windowed height, 0 for default size
+ gfx.window_height=0
+
+ # Up-/downscale the back buffer's width. This does not change the game's rendering resolution but scales the final frame. Use this to target the native resolution of your monitor/TV, e.g. to avoid over-/underscan, bad image quality or latency caused by the monitors internal upscaler. 0 to disable this feature. Must be set in combination with the corresponding height parameter.
+ gfx.scale_back_buffer_width=0
+
+ # Up-/downscale the back buffer's height. This does not change the game's rendering resolution but scales the final frame. Use this to target the native resolution of your monitor/TV, e.g. to avoid over-/underscan, bad image quality or latency caused by the monitors internal upscaler. 0 to disable this feature. Must be set in combination with the corresponding width parameter.
+ gfx.scale_back_buffer_height=0
+
+ # Filter type to use for up-/downscaling the back buffer. Only used if scaling feature was enabled by setting the scaling width and height parameters. Available types: none, linear, point (refer to D3DTEXTUREFILTERTYPE for explanation).
+ gfx.scale_back_buffer_filter=none
+ ```
+
+ If you can't seem to find them, press `CTRL` + `F` and search for `gfx.frame_rate_limit=0.0`. This will bring you to the first line we want to edit.
+
+!!! tip ""
+ Listed below are the values we want to change them to.
+
+ ```
+ gfx.frame_rate_limit=59.95
+ gfx.windowed=true
+ gfx.window_width=1920
+ gfx.window_height=1080
+ gfx.scale_back_buffer_width=1920
+ gfx.scale_back_buffer_height=1080
+ gfx.scale_back_buffer_filter=point
+ ```
+ Unless you'd like to have the game properly windowed you can safely ignore `gfx.framed=false`.
+
+ Make sure to decide on whether you want `Linear` or `Point` rendering.
+
+ ```
+ gfx.scale_back_buffer_filter=linear
+ gfx.scale_back_buffer_filter=point
+ ```
+
+## First launch
+
+!!! danger "If you have any issues running the game, refer to the [Troubleshooting](troubleshooting.md) page"
+
+### BACKUP DATA
+
+!!! tip ""
+
+ If you've followed all instructions correctly, you're now finally ready to launch the game!
+
+ **First plug your controller if you have one** and run :material-file:`gamestart.bat`.
+
+ If it's your first time running the game, you'll immediately be greeted with this screen.
+
+
+
+
+
+!!! tip ""
+ Press your `Start` key to confirm to get to the next error message.
+
+### CLOCK ERROR
+
+
+
+!!! tip ""
+ Press your `Start` key to confirm. This will bring you into it's service menu.
+
+
+
+!!! tip ""
+ Instructions on how to navigate the menu are shown at the bottom of the screen.
+
+ - Press `1` and `2` to go up and down.
+ - Press `6` to select/execute.
+
+ Navigate to `CLOCK`. You do not need to manually change it. Navigate to `SAVE AND EXIT`.
+
+
+
+### Enabling e-AMUSEMENT for Online Play
+
+!!! tip ""
+ From the service menu, go to `NETWORK OPTIONS` then `e-AMUSEMENT SETTINGS`.
+
+
+
+
+
+!!! tip ""
+ It'll bring you to this screen, change it so that `e-AMUSEMENT` switches to `ON` and it will look like this:
+
+
+
+
+
+!!! tip ""
+ We will need to set a `SHOP NAME SETTING` and change our `PREFECTURE` otherwise the game will throw errors at us.
+
+
+
+!!! tip ""
+
+ - Name your shop to whatever you'd like. Instructions on how to navigate are at the bottom of the screen.
+ - Navigate to `EXIT` and select it.
+ - Change your prefecture once or how many times you'd like, it doesn't matter as long as it's not the default one.
+
+
+
+!!! tip ""
+ Select `SAVE AND EXIT`. The game will now give you a message, which translated means:
+
+ `e-AMUSEMENT settings have been changed. Please turn the power off and on again.`
+
+ So, close the game and open it again.
+
+
+
+## Final Notes
+
+!!! success "You're all done! Make sure to insert two credits by pressing your `SERVICE` key. Have fun!"
+
+!!! warning "Have any other errors?"
+ Check out the [Troubleshooting](troubleshooting.md) section.
diff --git a/docs/games/konami/iidx/11_red/troubleshooting.md b/docs/games/konami/iidx/11_red/troubleshooting.md
new file mode 100644
index 0000000..48ada5f
--- /dev/null
+++ b/docs/games/konami/iidx/11_red/troubleshooting.md
@@ -0,0 +1,62 @@
+
+# Troubleshooting
+
+--8<-- "docs/snippets/common/old_guide.md"
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+### My Game Is Running Crazy Fast!
+
+!!! tip ""
+ The most common reason for this is the game is running over its required 59.95hz, the game is hardcoded to run at 59.95hz and this cannot be changed. To solve this, check [Game resolution and locking FPS](setup.md#game-resolution-and-locking-fps) of the guide again.
+
+### I'm getting "NETWORK WARNING" instead of "NETWORK OK"
+
+!!! tip ""
+ This can be caused by:
+
+ - Invalid PCBID
+ - Firewall blocking connections
+ - Invalid eamuse url or port specified
+ - Game is not run using the Administrator account
+
+### My background videos aren't working!
+
+!!! tip ""
+
+ You need to install a codec.
+
+ - Open :material-zip-box:`bemanitools-supplement-v1.6.zip` and navigate to :material-folder:`\iidx.zip\iidx\misc\` where :material-file:`CLVSD.ax` is located.
+
+ - Extract :material-file:`CLVSD.ax` inside a :material-folder: folder that you know won't be moved or renamed.
+
+ - Open the :material-console:command prompt as ***administrator***. Now type `regsvr32 "
+# Game Setup
+
+--8<-- "docs/snippets/common/old_guide.md"
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+## Preparing data
+
+!!! tip ""
+
+ After downloading and extracting your data, we need to make sure your files aren't set to `Read-only`.
+
+ - Right click the folder containing your data, then click on `Properties`.
+ - In the `General` tab go down to `Attributes`, untick `Read-only` and click `Apply`.
+ - A popup will appear, select `Apply changes to this folder, subfolder and files` and press `OK`.
+ - Finally, click `OK` again to exit out of properties.
+
+## Installing Bemanitools
+
+!!! tip ""
+
+ - Download :material-package-down:[Bemanitools](https://github.com/djhackersdev/bemanitools/releases/download/5.48/bemanitools-5.48.zip).
+
+ - Inside :material-zip-box:`bemanitools-5.48.zip` locate :material-zip-box:`iidx-09-to-12.zip`.
+
+ - Extract everything inside the folder that contains the :material-file:`bm2dx.exe` which is located in :material-folder:`\ECO\JAD`.
+
+ Pictured below is what your folder should look like. We've removed any files not necessary for **HAPPY SKY**.
+
+
+
+### Using iidxhook-12.conf & RtEffect.dll
+
+!!! tip ""
+
+ - Download the :material-package-down:[Bemanitools supplements](https://github.com/djhackersdev/bemanitools-supplement/releases/download/1.6/bemanitools-supplement-1.6.zip)
+
+ - Open :material-zip-box:`bemanitools-supplement-v1.6.zip` and navigate inside :material-zip-box:`misc.zip`
+
+ - Inside :material-folder:`misc\d3d8to9`, extract :material-file-cog-outline:`d3d8.dll` to :material-folder:`\ECO\JAD`.
+
+ This enables us to use the graphic options inside :material-file-code:`iidxhook-12.conf` which we will take advantage of.
+
+ - Open :material-zip-box:`bemanitools-supplement-v1.6.zip` and navigate inside :material-zip-box:`iidx.zip`
+
+ - Inside :material-folder:`iidx/misc`, extract :material-file-cog-outline:`RtEffect_stub.dll` to :material-folder:`\ECO\JAD`.
+
+ - Delete the already existing :material-file-remove-outline:`RtEffect.dll` and rename :material-file-edit-outline:`RtEffect_stub.dll` to :material-file-cog-outline:`RtEffect.dll`.
+
+ This will eliminate any immediate crashes relating to needing specific old hardware.
+
+### Installing CLVSD.ax
+
+!!! tip ""
+
+ We need to install a codec so that background videos will work and won't cause an error.
+
+ - Open :material-zip-box:`bemanitools-supplement-v1.6.zip` and navigate to :material-folder:`\iidx.zip\iidx\misc\` where :material-file:`CLVSD.ax` is located.
+
+ - Extract :material-file:`CLVSD.ax` inside a :material-folder: folder that you know won't be moved or renamed.
+
+ - Open the :material-console:command prompt as ***administrator***. Now type `regsvr32 "
+
+## Connecting to a network
+
+!!! tip ""
+
+ - Locate your :material-file-code:`iidxhook-12.conf`
+
+ - Open it with your desired text editor (we're using [Notepad++](https://notepad-plus-plus.org/))
+
+ - Replace the `eamuse.server=localhost:80` with your desired network URL
+
+ - Replace `eamuse.pcbid=XXXXXXXXXXXXXXXXXXXX` **and** `eamuse.eamid=XXXXXXXXXXXXXXXXXXXX` with your PCBID of your network of choice.
+
+ ```
+ # URL (e.g. http://my.eamuse.server:80/whatever) or IPV4 (e.g. 127.0.0.1:80) of the target eamuse server. The port is optional but defaults to 80.
+ eamuse.server=localhost:80
+
+ # PCBID
+ eamuse.pcbid=XXXXXXXXXXXXXXXXXXXX
+
+ # EAMID
+ eamuse.eamid=XXXXXXXXXXXXXXXXXXXX
+ ```
+
+## Game resolution and locking FPS
+
+!!! tip ""
+ We'd like to mention that there are two options when it comes to how the game renders. You can choose between `Linear` and `Point`.
+
+ Below is an example of how both look like.
+
+ ??? info "Linear"
+ 
+
+ ??? info "Point"
+ 
+
+ It comes down to your own prefrence what you decide on, `Linear` is less sharp but doesn't have pixel perfect edges. `Point` is sharp and is pixel perfect.
+
+!!! tip ""
+ Next up, we'll setup borderless window and configure the proper resolution. We're using a `1920x1080` monitor so we will use that.
+
+ Repeat the previous step and open your :material-file-code:`iidxhook-12.conf`. We want to find these lines:
+
+ ```
+ # Software limit the frame rate of the rendering loop in hz, e.g. 60 or 59.95 (0.0 = no software limit)
+ gfx.frame_rate_limit=0.0
+
+ # Run the game windowed
+ gfx.windowed=false
+
+ # Windowed width, 0 for default size
+ gfx.window_width=0
+
+ # Windowed height, 0 for default size
+ gfx.window_height=0
+
+ # Up-/downscale the back buffer's width. This does not change the game's rendering resolution but scales the final frame. Use this to target the native resolution of your monitor/TV, e.g. to avoid over-/underscan, bad image quality or latency caused by the monitors internal upscaler. 0 to disable this feature. Must be set in combination with the corresponding height parameter.
+ gfx.scale_back_buffer_width=0
+
+ # Up-/downscale the back buffer's height. This does not change the game's rendering resolution but scales the final frame. Use this to target the native resolution of your monitor/TV, e.g. to avoid over-/underscan, bad image quality or latency caused by the monitors internal upscaler. 0 to disable this feature. Must be set in combination with the corresponding width parameter.
+ gfx.scale_back_buffer_height=0
+
+ # Filter type to use for up-/downscaling the back buffer. Only used if scaling feature was enabled by setting the scaling width and height parameters. Available types: none, linear, point (refer to D3DTEXTUREFILTERTYPE for explanation).
+ gfx.scale_back_buffer_filter=none
+ ```
+
+ If you can't seem to find them, press `CTRL` + `F` and search for `gfx.frame_rate_limit=0.0`. This will bring you to the first line we want to edit.
+
+!!! tip ""
+ Listed below are the values we want to change them to.
+
+ ```
+ gfx.frame_rate_limit=59.95
+ gfx.windowed=true
+ gfx.window_width=1920
+ gfx.window_height=1080
+ gfx.scale_back_buffer_width=1920
+ gfx.scale_back_buffer_height=1080
+ gfx.scale_back_buffer_filter=point
+ ```
+ Unless you'd like to have the game properly windowed you can safely ignore `gfx.framed=false`.
+
+ Make sure to decide on whether you want `Linear` or `Point` rendering.
+
+ ```
+ gfx.scale_back_buffer_filter=linear
+ gfx.scale_back_buffer_filter=point
+ ```
+
+## First launch
+
+!!! danger "If you have any issues running the game, refer to the [Troubleshooting](troubleshooting.md) page"
+
+### BACKUP DATA
+
+!!! tip ""
+
+ If you've followed all instructions correctly, you're now finally ready to launch the game!
+
+ **First plug your controller if you have one** and run :material-file:`gamestart.bat`.
+
+ If it's your first time running the game, you'll immediately be greeted with this screen.
+
+
+
+
+
+!!! tip ""
+ Press your `Start` key to confirm to get to the next error message.
+
+### CLOCK ERROR
+
+
+
+!!! tip ""
+ Press your `Start` key to confirm. This will bring you into it's service menu.
+
+
+
+!!! tip ""
+ Instructions on how to navigate the menu are shown at the bottom of the screen.
+
+ - Press `1` and `2` to go up and down.
+ - Press `6` to select/execute.
+
+ Navigate to `CLOCK`. You do not need to manually change it. Navigate to `SAVE AND EXIT`.
+
+
+
+### Enabling e-AMUSEMENT for Online Play
+
+!!! tip ""
+ From the service menu, go to `NETWORK OPTIONS` then `e-AMUSEMENT SETTINGS`.
+
+
+
+
+
+!!! tip ""
+ It'll bring you to this screen, change it so that `e-AMUSEMENT` switches to `ON` and it will look like this:
+
+
+
+
+
+!!! tip ""
+ We will need to set a `SHOP NAME SETTING` and change our `PREFECTURE` otherwise the game will throw errors at us.
+
+
+
+!!! tip ""
+
+ - Name your shop to whatever you'd like. Instructions on how to navigate are at the bottom of the screen.
+ - Navigate to `EXIT` and select it.
+ - Change your prefecture once or how many times you'd like, it doesn't matter as long as it's not the default one.
+
+
+
+!!! tip ""
+ Select `SAVE AND EXIT`. The game will now give you a message, which translated means:
+
+ `e-AMUSEMENT settings have been changed. Please turn the power off and on again.`
+
+ So, close the game and open it again.
+
+
+
+## Final Notes
+
+!!! success "You're all done! Make sure to insert two credits by pressing your `SERVICE` key. Have fun!"
+
+!!! warning "Have any other errors?"
+ Check out the [Troubleshooting](troubleshooting.md) section.
+
diff --git a/docs/games/konami/iidx/12_happysky/troubleshooting.md b/docs/games/konami/iidx/12_happysky/troubleshooting.md
new file mode 100644
index 0000000..6cce1f8
--- /dev/null
+++ b/docs/games/konami/iidx/12_happysky/troubleshooting.md
@@ -0,0 +1,62 @@
+
+# Troubleshooting
+
+--8<-- "docs/snippets/common/old_guide.md"
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+### My Game Is Running Crazy Fast!
+
+!!! tip ""
+ The most common reason for this is the game is running over its required 59.95hz, the game is hardcoded to run at 59.95hz and this cannot be changed. To solve this, check [Game resolution and locking FPS](setup.md#game-resolution-and-locking-fps) of the guide again.
+
+### I'm getting "NETWORK WARNING" instead of "NETWORK OK"
+
+!!! tip ""
+ This can be caused by:
+
+ - Invalid PCBID
+ - Firewall blocking connections
+ - Invalid eamuse url or port specified
+ - Game is not run using the Administrator account
+
+### My background videos aren't working!
+
+!!! tip ""
+
+ You need to install a codec.
+
+ - Open :material-zip-box:`bemanitools-supplement-v1.6.zip` and navigate to :material-folder:`\iidx.zip\iidx\misc\` where :material-file:`CLVSD.ax` is located.
+
+ - Extract :material-file:`CLVSD.ax` inside a :material-folder: folder that you know won't be moved or renamed.
+
+ - Open the :material-console:command prompt as ***administrator***. Now type `regsvr32 "
+# Game Setup
+
+--8<-- "docs/snippets/common/old_guide.md"
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+## Preparing data
+
+!!! tip ""
+
+ After downloading and extracting your data, we need to make sure your files aren't set to `Read-only`.
+
+ - Right click the folder containing your data, then click on `Properties`.
+ - In the `General` tab go down to `Attributes`, untick `Read-only` and click `Apply`.
+ - A popup will appear, select `Apply changes to this folder, subfolder and files` and press `OK`.
+ - Finally, click `OK` again to exit out of properties.
+
+## Installing Bemanitools
+
+!!! tip ""
+
+ - Download :material-package-down:[Bemanitools](https://github.com/djhackersdev/bemanitools/releases/download/5.48/bemanitools-5.48.zip).
+
+ - Inside :material-zip-box:`bemanitools-5.48.zip` locate :material-zip-box:`iidx-13.zip`.
+
+ - Extract everything inside the folder that contains the :material-file:`bm2dx.exe` which is located in :material-folder:`\FDD\JAG`.
+
+ Pictured below is what your folder should look like. We've removed any files not necessary for **DistorteD**.
+
+
+
+### Using iidxhook-13.conf & RtEffect.dll
+
+!!! tip ""
+
+ - Download the :material-package-down:[Bemanitools supplements](https://github.com/djhackersdev/bemanitools-supplement/releases/download/1.6/bemanitools-supplement-1.6.zip)
+
+ - Open :material-zip-box:`bemanitools-supplement-v1.6.zip` and navigate inside :material-zip-box:`misc.zip`
+
+ - Inside :material-folder:`misc\d3d8to9`, extract :material-file-cog-outline:`d3d8.dll` to :material-folder:`\FDD\JAG`.
+
+ This enables us to use the graphic options inside :material-file-code:`iidxhook-13.conf` which we will take advantage of.
+
+ - Open :material-zip-box:`bemanitools-supplement-v1.6.zip` and navigate inside :material-zip-box:`iidx.zip`
+
+ - Inside :material-folder:`iidx/misc`, extract :material-file-cog-outline:`RtEffect_stub.dll` to :material-folder:`\FDD\JAG`.
+
+ - Delete the already existing :material-file-remove-outline:`RtEffect.dll` and rename :material-file-edit-outline:`RtEffect_stub.dll` to :material-file-cog-outline:`RtEffect.dll`.
+
+ This will eliminate any immediate crashes relating to needing specific old hardware.
+
+### Installing CLVSD.ax
+
+!!! tip ""
+
+ We need to install a codec so that background videos will work and won't cause an error.
+
+ - Open :material-zip-box:`bemanitools-supplement-v1.6.zip` and navigate to :material-folder:`\iidx.zip\iidx\misc\` where :material-file:`CLVSD.ax` is located.
+
+ - Extract :material-file:`CLVSD.ax` inside a :material-folder: folder that you know won't be moved or renamed.
+
+ - Open the :material-console:command prompt as ***administrator***. Now type `regsvr32 "
+
+## Connecting to a network
+
+!!! tip ""
+
+ - Locate your :material-file-code:`iidxhook-13.conf`
+
+ - Open it with your desired text editor (we're using [Notepad++](https://notepad-plus-plus.org/))
+
+ - Replace the `eamuse.server=localhost:80` with your desired network URL
+
+ - Replace `eamuse.pcbid=XXXXXXXXXXXXXXXXXXXX` **and** `eamuse.eamid=XXXXXXXXXXXXXXXXXXXX` with your PCBID of your network of choice.
+
+ ```
+ # URL (e.g. http://my.eamuse.server:80/whatever) or IPV4 (e.g. 127.0.0.1:80) of the target eamuse server. The port is optional but defaults to 80.
+ eamuse.server=localhost:80
+
+ # PCBID
+ eamuse.pcbid=XXXXXXXXXXXXXXXXXXXX
+
+ # EAMID
+ eamuse.eamid=XXXXXXXXXXXXXXXXXXXX
+ ```
+
+## Game resolution and locking FPS
+
+!!! tip ""
+ We'd like to mention that there are two options when it comes to how the game renders. You can choose between `Linear` and `Point`.
+
+ Below is an example of how both look like.
+
+ ??? info "Linear"
+ 
+
+ ??? info "Point"
+ 
+
+ It comes down to your own prefrence what you decide on, `Linear` is less sharp but doesn't have pixel perfect edges. `Point` is sharp and is pixel perfect.
+
+!!! tip ""
+ Next up, we'll setup borderless window and configure the proper resolution. We're using a `1920x1080` monitor so we will use that.
+
+ Repeat the previous step and open your :material-file-code:`iidxhook-12.conf`. We want to find these lines:
+
+ ```
+ # Software limit the frame rate of the rendering loop in hz, e.g. 60 or 59.95 (0.0 = no software limit)
+ gfx.frame_rate_limit=0.0
+
+ # Run the game windowed
+ gfx.windowed=false
+
+ # Windowed width, 0 for default size
+ gfx.window_width=0
+
+ # Windowed height, 0 for default size
+ gfx.window_height=0
+
+ # Up-/downscale the back buffer's width. This does not change the game's rendering resolution but scales the final frame. Use this to target the native resolution of your monitor/TV, e.g. to avoid over-/underscan, bad image quality or latency caused by the monitors internal upscaler. 0 to disable this feature. Must be set in combination with the corresponding height parameter.
+ gfx.scale_back_buffer_width=0
+
+ # Up-/downscale the back buffer's height. This does not change the game's rendering resolution but scales the final frame. Use this to target the native resolution of your monitor/TV, e.g. to avoid over-/underscan, bad image quality or latency caused by the monitors internal upscaler. 0 to disable this feature. Must be set in combination with the corresponding width parameter.
+ gfx.scale_back_buffer_height=0
+
+ # Filter type to use for up-/downscaling the back buffer. Only used if scaling feature was enabled by setting the scaling width and height parameters. Available types: none, linear, point (refer to D3DTEXTUREFILTERTYPE for explanation).
+ gfx.scale_back_buffer_filter=none
+ ```
+
+ If you can't seem to find them, press `CTRL` + `F` and search for `gfx.frame_rate_limit=0.0`. This will bring you to the first line we want to edit.
+
+!!! tip ""
+ Listed below are the values we want to change them to.
+
+ ```
+ gfx.frame_rate_limit=59.95
+ gfx.windowed=true
+ gfx.window_width=1920
+ gfx.window_height=1080
+ gfx.scale_back_buffer_width=1920
+ gfx.scale_back_buffer_height=1080
+ gfx.scale_back_buffer_filter=linear
+ ```
+ Unless you'd like to have the game properly windowed you can safely ignore `gfx.framed=false`.
+
+ Make sure to decide on whether you want `Linear` or `Point` rendering.
+
+ ```
+ gfx.scale_back_buffer_filter=linear
+ gfx.scale_back_buffer_filter=point
+ ```
+
+## First launch
+
+!!! danger "If you have any issues running the game, refer to the [Troubleshooting](troubleshooting.md) page"
+
+### BACKUP DATA
+
+!!! tip ""
+
+ If you've followed all instructions correctly, you're now finally ready to launch the game!
+
+ **First plug your controller if you have one** and run :material-file:`gamestart.bat`.
+
+ If it's your first time running the game, you'll immediately be greeted with this screen.
+
+
+
+
+
+!!! tip ""
+ Press your `Test` key to confirm to get to the next error message.
+
+### CLOCK ERROR
+
+
+
+!!! tip ""
+ Press your `Test` key to confirm. This will bring you into it's service menu.
+
+
+
+!!! tip ""
+ Instructions on how to navigate the menu are shown at the bottom of the screen.
+
+ - Press `1` and `2` to go up and down.
+ - Press `6` to select/execute.
+
+ Navigate to `CLOCK`. You do not need to manually change it. Navigate to `SAVE AND EXIT`.
+
+
+
+### Enabling e-AMUSEMENT for Online Play
+
+!!! tip ""
+ From the service menu, go to `NETWORK OPTIONS` then `e-AMUSEMENT SETTINGS`.
+
+
+
+
+
+!!! tip ""
+ It'll bring you to this screen, change it so that `e-AMUSEMENT` switches to `ON` and it will look like this:
+
+
+
+
+
+!!! tip ""
+ We will need to set a `SHOP NAME SETTING` and change our `PREFECTURE` otherwise the game will throw errors at us.
+
+
+
+!!! tip ""
+
+ - Name your shop to whatever you'd like. Instructions on how to navigate are at the bottom of the screen.
+ - Navigate to `EXIT` and select it.
+ - Change your prefecture once or how many times you'd like, it doesn't matter as long as it's not the default one.
+
+
+
+!!! tip ""
+ Select `SAVE AND EXIT`. The game will now give you a message, which translated means:
+
+ `e-AMUSEMENT settings have been changed. Please turn the power off and on again.`
+
+ So, close the game and open it again.
+
+
+
+## Final Notes
+
+!!! success "You're all done! Make sure to insert two credits by pressing your `SERVICE` key. Have fun!"
+
+!!! warning "Have any other errors?"
+ Check out the [Troubleshooting](troubleshooting.md) section.
diff --git a/docs/games/konami/iidx/13_distorted/troubleshooting.md b/docs/games/konami/iidx/13_distorted/troubleshooting.md
new file mode 100644
index 0000000..7866cc7
--- /dev/null
+++ b/docs/games/konami/iidx/13_distorted/troubleshooting.md
@@ -0,0 +1,62 @@
+
+# Troubleshooting
+
+--8<-- "docs/snippets/common/old_guide.md"
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+### My Game Is Running Crazy Fast!
+
+!!! tip ""
+ The most common reason for this is the game is running over its required 59.95hz, the game is hardcoded to run at 59.95hz and this cannot be changed. To solve this, check [Game resolution and locking FPS](setup.md#game-resolution-and-locking-fps) of the guide again.
+
+### I'm getting "NETWORK WARNING" instead of "NETWORK OK"
+
+!!! tip ""
+ This can be caused by:
+
+ - Invalid PCBID
+ - Firewall blocking connections
+ - Invalid eamuse url or port specified
+ - Game is not run using the Administrator account
+
+### My background videos aren't working!
+
+!!! tip ""
+
+ You need to install a codec.
+
+ - Open :material-zip-box:`bemanitools-supplement-v1.6.zip` and navigate to :material-folder:`\iidx.zip\iidx\misc\` where :material-file:`CLVSD.ax` is located.
+
+ - Extract :material-file:`CLVSD.ax` inside a :material-folder: folder that you know won't be moved or renamed.
+
+ - Open the :material-console:command prompt as ***administrator***. Now type `regsvr32 "
+# Game Setup
+
+--8<-- "docs/snippets/common/old_guide.md"
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+## Preparing data
+
+!!! tip ""
+
+ After downloading and extracting your data, we need to make sure your files aren't set to `Read-only`.
+
+ - Right click the folder containing your data, then click on `Properties`.
+ - In the `General` tab go down to `Attributes`, untick `Read-only` and click `Apply`.
+ - A popup will appear, select `Apply changes to this folder, subfolder and files` and press `OK`.
+ - Finally, click `OK` again to exit out of properties.
+
+## Installing Bemanitools
+
+!!! tip ""
+
+ - Download :material-package-down:[Bemanitools](https://github.com/djhackersdev/bemanitools/releases/download/5.48/bemanitools-5.48.zip).
+
+ - Inside :material-zip-box:`bemanitools-5.48.zip` locate :material-zip-box:`iidx-14-to-17.zip`.
+
+ - Extract everything inside the folder that contains the :material-file:`bm2dx.exe` which is located in :material-folder:`\GLD\2007072301`.
+
+ Pictured below is what your folder should look like. We've removed any files not necessary for **GOLD**.
+
+
+
+### Using iidxhook-14.conf
+
+!!! tip ""
+
+ - Download the :material-package-down:[Bemanitools supplements](https://github.com/djhackersdev/bemanitools-supplement/releases/download/1.6/bemanitools-supplement-1.6.zip)
+
+ - Open :material-zip-box:`bemanitools-supplement-v1.6.zip` and navigate inside :material-zip-box:`misc.zip`
+
+ - Inside :material-folder:`misc\d3d8to9`, extract :material-file-cog-outline:`d3d8.dll` to :material-folder:`\GLD\2007072301`.
+
+ This enables us to use the graphic options inside :material-file-code:`iidxhook-14.conf` which we will take advantage of.
+
+### Installing CLVSD.ax
+
+!!! tip ""
+
+ We need to install a codec so that background videos will work and won't cause an error.
+
+ - Open :material-zip-box:`bemanitools-supplement-v1.6.zip` and navigate to :material-folder:`\iidx.zip\iidx\misc\` where :material-file:`CLVSD.ax` is located.
+
+ - Extract :material-file:`CLVSD.ax` inside a :material-folder: folder that you know won't be moved or renamed.
+
+ - Open the :material-console:command prompt as ***administrator***. Now type `regsvr32 "
+
+## Connecting to a network
+
+!!! tip ""
+
+ - Locate your :material-file-code:`iidxhook-14.conf`
+
+ - Open it with your desired text editor (we're using [Notepad++](https://notepad-plus-plus.org/))
+
+ - Replace the `eamuse.server=localhost:80` with your desired network URL
+
+ - Replace `eamuse.pcbid=XXXXXXXXXXXXXXXXXXXX` **and** `eamuse.eamid=XXXXXXXXXXXXXXXXXXXX` with your PCBID of your network of choice.
+
+ ```
+ # URL (e.g. http://my.eamuse.server:80/whatever) or IPV4 (e.g. 127.0.0.1:80) of the target eamuse server. The port is optional but defaults to 80.
+ eamuse.server=localhost:80
+
+ # PCBID
+ eamuse.pcbid=XXXXXXXXXXXXXXXXXXXX
+
+ # EAMID
+ eamuse.eamid=XXXXXXXXXXXXXXXXXXXX
+ ```
+
+## Game resolution and locking FPS
+
+!!! tip ""
+ We'd like to mention that there are two options when it comes to how the game renders. You can choose between `Linear` and `Point`.
+
+ Below is an example of how both look like.
+
+ ??? info "Linear"
+ 
+
+ ??? info "Point"
+ 
+
+ It comes down to your own prefrence what you decide on, `Linear` is less sharp but doesn't have pixel perfect edges. `Point` is sharp and is pixel perfect.
+
+!!! tip ""
+ Next up, we'll setup borderless window and configure the proper resolution. We're using a `1920x1080` monitor so we will use that.
+
+ Repeat the previous step and open your :material-file-code:`iidxhook-14.conf`. We want to find these lines:
+
+ ```
+ # Software limit the frame rate of the rendering loop in hz, e.g. 60 or 59.95 (0.0 = no software limit)
+ gfx.frame_rate_limit=0.0
+
+ # Run the game windowed
+ gfx.windowed=false
+
+ # Windowed width, 0 for default size
+ gfx.window_width=0
+
+ # Windowed height, 0 for default size
+ gfx.window_height=0
+
+ # Up-/downscale the back buffer's width. This does not change the game's rendering resolution but scales the final frame. Use this to target the native resolution of your monitor/TV, e.g. to avoid over-/underscan, bad image quality or latency caused by the monitors internal upscaler. 0 to disable this feature. Must be set in combination with the corresponding height parameter.
+ gfx.scale_back_buffer_width=0
+
+ # Up-/downscale the back buffer's height. This does not change the game's rendering resolution but scales the final frame. Use this to target the native resolution of your monitor/TV, e.g. to avoid over-/underscan, bad image quality or latency caused by the monitors internal upscaler. 0 to disable this feature. Must be set in combination with the corresponding width parameter.
+ gfx.scale_back_buffer_height=0
+
+ # Filter type to use for up-/downscaling the back buffer. Only used if scaling feature was enabled by setting the scaling width and height parameters. Available types: none, linear, point (refer to D3DTEXTUREFILTERTYPE for explanation).
+ gfx.scale_back_buffer_filter=none
+ ```
+
+ If you can't seem to find them, press `CTRL` + `F` and search for `gfx.frame_rate_limit=0.0`. This will bring you to the first line we want to edit.
+
+!!! tip ""
+ Listed below are the values we want to change them to.
+
+ ```
+ gfx.frame_rate_limit=59.95
+ gfx.windowed=true
+ gfx.window_width=1920
+ gfx.window_height=1080
+ gfx.scale_back_buffer_width=1920
+ gfx.scale_back_buffer_height=1080
+ gfx.scale_back_buffer_filter=linear
+ ```
+ Unless you'd like to have the game properly windowed you can safely ignore `gfx.framed=false`.
+
+ Make sure to decide on whether you want `Linear` or `Point` rendering.
+
+ ```
+ gfx.scale_back_buffer_filter=linear
+ gfx.scale_back_buffer_filter=point
+ ```
+
+## First launch
+
+!!! danger "If you have any issues running the game, refer to the [Troubleshooting](troubleshooting.md) page"
+
+### BACKUP DATA
+
+!!! tip ""
+
+ If you've followed all instructions correctly, you're now finally ready to launch the game!
+
+ **First plug your controller if you have one** and run :material-file:`gamestart.bat`.
+
+ If it's your first time running the game, you'll immediately be greeted with this screen.
+
+
+
+!!! warning "If you get `USB I/O ERROR ERROR(FM TRNS-OUT)` or `USB I/O ERROR ERROR(FM-DL TIMEOUT)`"
+ Reboot the game and it should get fixed.
+
+
+
+!!! tip ""
+ Press your `Test` key to confirm to get to the next error message.
+
+### CLOCK ERROR
+
+
+
+!!! tip ""
+ Press your `Test` key to confirm. The game will then perform a `MONITOR CHECK`.
+
+
+
+
+
+!!! tip ""
+ After the monitor check, the game will bring you into it's service menu.
+
+ Instructions on how to navigate the menu are shown at the bottom of the screen.
+
+ - Press `1` and `2` to go up and down.
+ - Press `6` to select/execute.
+
+ Navigate to `CLOCK`. You do not need to manually change it. Navigate to `SAVE AND EXIT`.
+
+
+
+### Enabling e-AMUSEMENT for Online Play
+
+!!! tip ""
+ From the service menu, go to `NETWORK OPTIONS` then `e-AMUSEMENT SETTINGS`.
+
+
+
+
+
+
+
+!!! tip ""
+ We will need to set a `SHOP NAME SETTING` and change our `SETTING AREA` otherwise the game will throw errors at us.
+
+
+
+!!! tip ""
+
+ - Name your shop to whatever you'd like. Instructions on how to navigate are at the bottom of the screen.
+ - Navigate to `EXIT` and select it.
+ - Change your `SETTING AREA` once or how many times you'd like, it doesn't matter as long as it's not the default one.
+
+
+
+!!! tip ""
+ Select `SAVE AND EXIT`.
+
+
+
+## Final Notes
+
+!!! success "You're all done! From the service menu select `GAMEMODE` and the game should load ready to be played. Make sure to insert two credits by pressing your `SERVICE` key. Have fun!"
+
+!!! warning "Have any other errors?"
+ Check out the [Troubleshooting](troubleshooting.md) section.
diff --git a/docs/games/konami/iidx/14_gold/troubleshooting.md b/docs/games/konami/iidx/14_gold/troubleshooting.md
new file mode 100644
index 0000000..f6ae41c
--- /dev/null
+++ b/docs/games/konami/iidx/14_gold/troubleshooting.md
@@ -0,0 +1,57 @@
+
+# Troubleshooting
+
+--8<-- "docs/snippets/common/old_guide.md"
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+### My Game Is Running Crazy Fast!
+
+!!! tip ""
+ The most common reason for this is the game is running over its required 59.95hz, the game is hardcoded to run at 59.95hz and this cannot be changed. To solve this, check [Game resolution and locking FPS](setup.md#game-resolution-and-locking-fps) of the guide again.
+
+### I'm getting "NETWORK WARNING" instead of "NETWORK OK"
+
+!!! tip ""
+ This can be caused by:
+
+ - Invalid PCBID
+ - Firewall blocking connections
+ - Invalid eamuse url or port specified
+ - Game is not run using the Administrator account
+
+### My background videos aren't working!
+
+!!! tip ""
+
+ You need to install a codec.
+
+ - Open :material-zip-box:`bemanitools-supplement-v1.6.zip` and navigate to :material-folder:`\iidx.zip\iidx\misc\` where :material-file:`CLVSD.ax` is located.
+
+ - Extract :material-file:`CLVSD.ax` inside a :material-folder: folder that you know won't be moved or renamed.
+
+ - Open the :material-console:command prompt as ***administrator***. Now type `regsvr32 "
+# Extra Information
+
+## Output modes
+!!! info "Output Mode"
+
+ This game supports two output modes: `S-VIDEO` and `VGA`.
+ The difference between these two is:
+
+ - `S-VIDEO` runs at 59.95hz
+ - `VGA` runs at 60.05hz
+
+ By default, the output mode is set automatically by the game.
+ !!! tip "If for some reason you want to change the output mode of your game, do the following:"
+ Open your `iidxhook-xx.conf`. Find a line that says:
+ ```
+ gfx.frame_rate_limit=xx.xx
+ ```
+
+ - Depending on the output mode of your choice, replace `xx.xx` with either 59.95 or 60.05
+
+ Now, in the service menu of your game:
+
+ - Go to `GAME OPTIONS`
+
+ 
+
+ - Go to the line that says `OUTPUT MODE` and change it to your desired mode
+
+ - Select `SAVE AND EXIT`
+
+ That's it!
+
+
\ No newline at end of file
diff --git a/docs/games/konami/iidx/16_empress/setup.md b/docs/games/konami/iidx/16_empress/setup.md
new file mode 100644
index 0000000..8c80cb1
--- /dev/null
+++ b/docs/games/konami/iidx/16_empress/setup.md
@@ -0,0 +1,167 @@
+
+# Game Setup
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+## Preparing data
+
+--8<-- "docs/snippets/common/data_readonly.md"
+
+ The **complete game data** should be approximately **26 GB or larger**.
+ If your data is significantly smaller, you likely have an update archive instead of the full game data.
+
+ Here's what the expected data structure should look like:
+
+ ```
+ 📂yyyymmddrr (revision directory, y = year digit, m = month digit, d = day digit, r = revision digit)
+ 📂data
+ 📄sidcode.txt
+ ```
+
+## Installing Bemanitools
+
+!!! tip ""
+
+ - Download the latest Bemanitools release [here](https://github.com/djhackersdev/bemanitools/releases/latest)
+
+ - Inside `bemanitools-x.xx.zip` locate `iidx-14-to-17.zip`
+
+ - Extract all files from `iidx-14-to-17.zip` to your revision directory (yyyymmddrr)
+
+!!! note "You may delete the `gamestart-[14,15,17].bat` and `iidxhook-[14,15,17].conf` files as you only need the ones for 16 (Empress)"
+
+--8<-- "docs/snippets/konami/iidx/btools_d3d8to9.md"
+
+--8<-- "docs/snippets/konami/iidx/btools_clvsd.md"
+
+!!! tip ""
+
+ In the end, here's what the expected data structure should look like:
+
+ ``` hl_lines="2 3 4 7 8 10 11 12 13 14 18 19"
+ 📄bm2dx.exe
+ 📄config.bat
+ 📄config.exe
+ 📄d3d8.dll
+ 📄d3dx9_24.dll
+ 📄dbghelp.dll
+ 📄eamio.dll
+ 📄gamestart-16.bat
+ 📄gcidata.nsd
+ 📄geninput.dll
+ 📄iidxhook3.dll
+ 📄iidxhook-16.conf
+ 📄iidxio.dll
+ 📄inject.exe
+ 📄libacio.dll
+ 📄libavs-win32.dll
+ 📄libavs-win32-ea3.dll
+ 📄vefx.txt
+ 📄vefxio.dll
+ ```
+
+## Configuring Bemanitools
+
+!!! info "Open the `config.bat` file. The following tabs correspond to the ones in the configuration window."
+
+=== "Buttons"
+
+--8<-- "docs/snippets/konami/iidx/btools_buttons.md"
+
+--8<-- "docs/snippets/konami/common/spicecfg_buttons_additionalinfo.md"
+
+=== "Lights"
+
+--8<-- "docs/snippets/konami/common/btools_lights.md"
+
+=== "Analogs"
+
+--8<-- "docs/snippets/konami/iidx/btools_analogs.md"
+
+=== "Network"
+
+--8<-- "docs/snippets/konami/common/btools_cards.md"
+
+## Connecting to a network
+
+--8<-- "docs/snippets/konami/iidx/btools_connecting_network.md"
+
+## Configuring graphics
+
+--8<-- "docs/snippets/konami/iidx/btools_graphics.md"
+
+## Before playing
+
+--8<-- "docs/snippets/common/before_playing.md"
+
+## First launch
+
+!!! tip ""
+
+ If you've followed all instructions correctly, you're now finally ready to launch the game!
+
+ **First plug your controller if you have one** and run `gamestart.bat` **as Administrator**.
+
+ If it's your first time running the game, you'll soon be greeted with this screen.
+
+
+
+ Press your `Test` key to initialize the backup data, a message will pop up stating it's been initialized.
+
+ !!! warning ""
+ If right here you get `USB I/O ERROR ERROR(FM TRNS-OUT)` or `USB I/O ERROR ERROR(FM-DL TIMEOUT)` instead of the `BACKUP DATA ERROR`, reboot the game and it should get fixed.
+
+ Next, you'll get another error.
+
+
+
+ Press your `Test` key again and let the game run for a bit until the monitor check is complete.
+
+ You will now be taken to the service menu.
+
+
+
+ Instructions on how to navigate the menu are shown at the bottom of the screen:
+
+ - Press `1` and `2` to go up and down
+ - Press `6` to select/execute
+
+ Start by going up to `CLOCK`.
+
+
+
+ Here, simply select `SAVE AND EXIT` and the clock will be set.
+
+ You'll be back in the service menu.
+
+ Go to `NETWORK OPTIONS` then `e-AMUSEMENT SETTINGS`.
+
+
+
+
+ You will need to set a shop name.
+
+ - Name your shop to whatever you'd like. Again, navigation instructions are at the bottom of the screen
+ - Go to `EXIT` then `SAVE AND EXIT`
+
+ Select `GAME OPTIONS`.
+
+
+
+ Here, you want to select a display type.
+
+ !!! warning "This setting affects timing offset in the song."
+
+ - `TYPE A`: No frame offset - Intended for CRT displays
+ - `TYPE B`: +1 frame offset - Intended for LCD displays
+
+ We recommend starting with `TYPE B` and changing this later if you encounter any issues.
+
+ - Go to `SAVE AND EXIT` then `GAME MODE`
+
+!!! success "You're all done! The game should load up properly now. Insert credits by pressing your `SERVICE` key!"
+
+## Help
+
+--8<-- "docs/snippets/common/help.md"
+
diff --git a/docs/games/konami/iidx/16_empress/troubleshooting.md b/docs/games/konami/iidx/16_empress/troubleshooting.md
new file mode 100644
index 0000000..d28d791
--- /dev/null
+++ b/docs/games/konami/iidx/16_empress/troubleshooting.md
@@ -0,0 +1,45 @@
+
+# Troubleshooting
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+!!! warning "If you get any error codes that weren't listed in the guides here, check out the [Bemanitools docs](https://github.com/djhackersdev/bemanitools/blob/master/doc/game-error-codes.md)"
+
+## Technical problems
+
+### Crashes
+
+!!! info "Riva Tuner Statistics Server (RTSS) and MSI Afterburner are known to cause odd crashes.
+# Extra Information
+
+--8<-- "docs/snippets/common/old_guide.md"
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+## More about ea3-config.xml
+
+!!! tip ""
+
+ The `ea3-config.xml` file is located inside the `prop` folder.
+
+ Below is an explanation on what different sections of this file do.
+
+ The following lines change the PCBID and HARDID that your system reports to your e-amusement server.
+ There is ^^**no need to manually change this**^^ as `spice2x` will do it for us.
+
+ ```xml
+
+# Game Setup
+
+--8<-- "docs/snippets/common/old_guide.md"
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+## Preparing data
+
+!!! tip ""
+
+ After downloading and extracting your data, we need to make sure your files aren't set to `Read-only`.
+
+ - Right click the folder containing your data, then click on `Properties`.
+ - In the `General` tab go down to `Attributes`, untick `Read-only` and click `Apply`.
+ - A popup will appear, select `Apply changes to this folder, subfolder and files` and press `OK`.
+ - Finally, click `OK` again to exit out of properties.
+
+ You should end up with a file structure with a few folders only, as follows:
+
+
+
+??? warning "If your data doesn't look like this"
+
+ If extra files are present next to your folders, such as executables, scripts, etc., **remove them**.
+ **This also means your data was tampered with and we strongly recommend getting new data from somewhere else.**
+
+## Installing spice2x
+
+!!! info ""
+
+ If you already have spice2x installed, make sure it is up to date!
+
+!!! tip ""
+
+ - Head over to [spice2x.github.io](https://spice2x.github.io) and download the latest release.
+ - Extract the `spice.exe` and `spicecfg.exe` files from the archive to your game's directory.
+
+ 
+
+## Configuring spice2x
+
+!!! info "Open `spicecfg.exe`, each following sub-section corresponds to a tab at the top"
+
+#### Buttons
+
+!!! tip ""
+
+ Click on `Bind` then press the key you want associated with the action.
+
+ With your controller and/or keyboard plugged in, configure your keys for:
+
+ - **Maintenance**: `Service, Test`
+ - **P1 Game buttons**: `1 to 7, Start, EFFECT, VEFX`
+ - **P1 Keypad**: `1 to 9, Keypad Insert Card`
+
+ **Only if** you're playing using a keyboard:
+
+ - **Turntable**: `TT+, TT-` **and optionally** `TT+/-` which alternates between `TT+` and `TT-` on each press.
+
+### Analogs (controller/cab only)
+
+!!! tip ""
+
+ With a controller rather than binding buttons to `TT+` and `TT-`, you need to:
+
+ - For Turntable P1, click `Bind`.
+ - In `Device`, pick your controller.
+ - In `Control`, pick whichever one corresponds to the turntable.
+ - Turn your turntable ensuring that the Preview turns along with it.
+ - Click `Close`, leaving the rest of the settings alone.
+
+### Overlay
+
+!!! tip ""
+
+ Modifying buttons in this section is not required but you are free to change what you want.
+
+ Click on `Bind` then press the key you want associated with the action.
+
+### Lights (controller/cab only)
+
+!!! tip ""
+
+ Your controller might support having its lights controlled by the game through spice2x.
+
+ If it does, here's how you may link different actions to your lights:
+
+ - Click `Bind`.
+ - In `Device`, pick your controller.
+ - In `Light Control`, select the corresponding light.
+ - Click `Close`.
+ - Repeat for your other lights.
+
+### Cards
+
+!!! info "Covered in the [Connecting to a network](#connecting-to-a-network) section"
+
+### Patches
+
+!!! info "Go through the [spice2x Patching](/extras/patchsp2x.md) page to import patches"
+
+!!! danger "To prevent issues, avoid patching things you don't need or understand"
+
+### API
+
+!!! warning "Leave everything at default unless you know what you're doing"
+
+### Options
+
+!!! info "If you don't know what an option does, hover over the its name with your mouse"
+
+ 
+
+!!! danger "Be very careful changing options you don't understand as it may cause issues"
+
+!!! tip "Required"
+
+ | Category | Option | Parameter | Setting |
+ |---------------|-----------------------|-------------------|---------|
+ | Network | EA Service URL | -url | Covered in [Connecting to a network](#connecting-to-a-network) |
+
+!!! tip "Highly Recommended for NVIDIA users ONLY"
+
+ | Category | Option | Parameter | Setting |
+ |-------------------|-----------------------------------|---------------| |
+ | Graphics (common) | NVIDIA profile optimization | -nvprofile | ON |
+
+
+### Advanced & Development
+
+!!! warning "Leave everything at default unless you know what you're doing"
+
+## Connecting to a network
+
+!!! danger "Please choose one of the two solutions, not both!"
+
+??? tip "Remote (Online Network)"
+
+ Open `spicecfg.exe` and head to the `Options` tab.
+
+ In the `Network` category, set the following settings:
+
+ - `EA Service URL` to the URL provided by your network.
+ - `PCBID` to the PCBID provided by your network.
+
+
+
+ Next you need a card number.
+ If you don't already have one, generate one in the `Cards` tab.
+ To keep your card number safe, create a new `.txt` file with ONLY it inside.
+
+ Once that's done, head to the `Cards` tab, for `Player 1` click `Open...` and point to your text file.
+
+
+
+??? tip "Local e-amuse Emulator (Asphyxia)"
+
+ This is covered in the [Asphyxia CORE](/extras/asphyxia.md) page.
+
+## Pre-launch requirements
+
+!!! info "These steps are required, otherwise your game won't run"
+
+### VCRedist & DirectX
+
+!!! tip ""
+
+ - Download and install the latest [VCRedist](https://www.techpowerup.com/download/visual-c-redistributable-runtime-package-all-in-one/)
+ - Download and install the [DirectX End-User Runtimes](https://www.microsoft.com/en-us/download/details.aspx?id=8109)
+
+### Audio
+
+!!! tip ""
+
+ - Open `spicecfg.exe`.
+ - At the very top, click on `Shortcuts` then `Audio Playback Devices`.
+ - In the popup window, right click on your default audio device, and click on `Properties`.
+ - Go to the `Advanced` tab.
+ - Check both boxes under `Exclusive Mode`.
+ - Open the `Default Format` dropdown.
+ - Pick the `24 bit, 44100 Hz (CD Quality)` option and click `Apply` then `OK`.
+
+
+
+## First launch
+
+!!! danger "If you have any issues running the game, refer to the [Troubleshooting](troubleshooting.md) page"
+
+### BACKUP DATA
+
+!!! tip ""
+
+ If you've followed all instructions correctly, you're now finally ready to launch the game!
+
+ **First plug your controller if you have one** and run `spice.exe`, press `Yes` when it asks for elevated privileges.
+
+ If it's your first time running the game, you'll immediately be greeted with this screen.
+
+
+
+### CLOCK ERROR
+
+!!! tip ""
+
+ Press your `Test` key to initialize the backup data, a message will pop up stating it's been initialized.
+
+ Next, you'll get another error.
+
+
+
+!!! tip ""
+
+ Let the game run for a bit until the monitor check is complete and you should be taken to the service menu.
+
+
+
+!!! tip ""
+
+ Instructions on how to navigate the menu are shown at the bottom of the screen.
+
+ - Press `1` and `2` to go up and down.
+ - Press `6` to select/execute.
+
+ Start by going up to `CLOCK`.
+
+
+
+!!! tip ""
+
+ Here, simply select `SAVE AND EXIT` and the clock will be set.
+
+ You'll be back in the service menu.
+
+### DEFINITION TYPE
+
+!!! tip ""
+
+ Go to `GAME OPTIONS` then `DEFINITION TYPE`.
+
+!!! tip ""
+
+ Choose either `HD` or `HD*` depending on your preferences.
+
+ `HD*` adds `+1.0` offset in-game, while `HD` doesn't.
+
+
+
+!!! tip ""
+
+ Once done selecting, select `YES` then `SAVE AND EXIT`.
+
+
+
+### NETWORK OPTIONS
+
+!!! tip ""
+
+ Go to `NETWORK OPTIONS` then `SHOP NAME SETTING`.
+
+
+
+
+!!! tip ""
+
+ We will need to set a shop name.
+
+ - Name your shop to whatever you'd like. Instructions on how to navigate are at the bottom of the screen.
+ - Go to `EXIT` then `SAVE AND EXIT`.
+
+
+
+
+!!! tip ""
+
+ Select `GAME MODE`.
+
+ You're all done! The game should load up properly now.
+
+## Carding in
+
+!!! tip ""
+ To card into the game:
+
+ 1. Press your `Keypad Insert Card` button.
+ 2. Enter your code using your keypad binds.
+
+## Troubleshooting
+
+!!! warning "Have any other issue?"
+
+ Check out the [Troubleshooting](troubleshooting.md) and [Error Codes](/errorcodes/konami.md) pages.
+
+ For any more game-specific information, check out [Extra Information](extras.md).
\ No newline at end of file
diff --git a/docs/games/konami/iidx/24_sinobuz/troubleshooting.md b/docs/games/konami/iidx/24_sinobuz/troubleshooting.md
new file mode 100644
index 0000000..b491ac4
--- /dev/null
+++ b/docs/games/konami/iidx/24_sinobuz/troubleshooting.md
@@ -0,0 +1,36 @@
+
+# Troubleshooting
+
+--8<-- "docs/snippets/common/old_guide.md"
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+### I'm having performance issues!
+
+!!! tip ""
+
+ If you're having performance issues of some kind, spice2x's [PC optimization](https://github.com/spice2x/spice2x.github.io/wiki/PC-optimization) guide is worth looking at.
+
+### My game is running slow/fast, After finishing a song the game gets stuck loading!
+
+!!! tip ""
+
+ The most common reason for this is the game is running over its required refresh rate.
+ To solve this, make sure v-sync isn't disabled in your graphics card's settings.
+
+ For NVIDIA users, enable `NVIDIA profile optimization (-nvprofile)` in the `Options` tab.
+
+### How do I set my offset?
+
+!!! tip ""
+
+ Play through a chart you're comfortable with.
+
+ If you're getting too many `Fast`, increase your offset `(+)`.
+ If you're getting too many `Slow`, decrease your offset `(-)`.
+
+### My inputs aren't working / I can't get past error messages!
+
+!!! tip ""
+
+ If **none** of your inputs are working, try updating [spice2x](https://spice2x.github.io/), you can also try using the beta versions if the stable releases don't work for you.
\ No newline at end of file
diff --git a/docs/games/konami/iidx/25_cannonballers/setup.md b/docs/games/konami/iidx/25_cannonballers/setup.md
new file mode 100644
index 0000000..cedfbca
--- /dev/null
+++ b/docs/games/konami/iidx/25_cannonballers/setup.md
@@ -0,0 +1,117 @@
+
+# Game Setup
+
+--8<-- "docs/snippets/common/old_guide.md"
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+## Getting Started
+
+!!! tip ""
+ Before we even touch the game, let's fiddle with our audio settings to minimize any potential crashing on startup. In Windows, go to `Playback Devices` and then right click on your default device and go to `Properties`. From there, hit the `Advanced` tab and set your `Default Format` to `44100 Hz` and check both of the options inside `Exclusive Mode` as pictured.
+
+
+
+!!! tip ""
+ Once that's done, it's time to work on setting up your data.
+
+ After downloading your data, the first thing to do is make sure your files aren't set to READ ONLY, make sure to uncheck it from the main folder in the Windows Properties tab if so. Then, put your desired **64-bit** tools inside the game's `contents` folder, and to create a `.bat` file. Pictured below is what your folder should look like, feel free to name your `.bat` file whatever you desire, for the sake of convenience we've named ours `gamestart.bat`.
+
+
+
+## Configuring Your Tools
+
+!!! tip ""
+ Now that you have your files ready, open up your `.bat` file in your desired text editor (we're using [Notepad++](https://notepad-plus-plus.org/)) and edit it with your desired parameters, for the purpose of this guide we will demonstrate both a local network configuration and an online example below with SpiceTools, skip to whichever you're in need of accordingly and please keep in mind you can add whatever additional parameters you desire.
+
+!!! warning "If you're not using SpiceTools:"
+ The overall structure of your .bat file will differ from the guide, namely the initialization of SpiceTools won't be present and potential parameters may differ. As stated above, make sure to check the documentation of your tools to ensure you're using the correct parameters for your needs.
+
+## Configuring for a Local Network
+
+!!! tip ""
+ For our local network configuration example, on a single line in the `.bat` file we're going to type `spice64.exe -ea -w` and save the file.
+
+ What do these different parameters do?
+
+ - `-ea` enables an integrated e-amusement server within SpiceTools.
+ - `-w` will boot the game in windowed mode which will ease our initial setup and testing later, make sure to remove `-w` to run the game fullscreen once you're done setting up!
+
+ Pictured below, the contents of our `gamestart.bat` file in Notepad++.
+
+
+
+## Configuring for an Online Network
+
+!!! tip ""
+ For our online network example we're simply doing the above but with different parameters! On our single line, we're going to type `spice64.exe -p XXXXXXXXXXXXXXXXXXXX -url http://yoururlhere.com/ -w` and save the file.
+
+ What do these different parameters do?
+
+ - `-p` takes your PCBID on your network of choice, simply replace `XXXXXXXXXXXXXXXXXXXX` with your PCBID.
+ - `-url` allows you to specify a custom service URL to connect with, simply replace `http://yoururlhere.com/` with your chosen network's URL.
+ - `-w` will boot the game in windowed mode which will ease our initial setup and testing later, make sure to remove `-w` to run the game fullscreen once you're done setting up!
+
+ Pictured below, the contents of our `gamestart.bat` file in Notepad++.
+
+
+
+!!! tip ""
+ One final note, since you're playing on a network, you will have one additional step of setting up your card file within your chosen tools, make sure to check your server's information on how to setup a card file.
+
+## Final Steps and Setting up the Game
+
+!!! tip ""
+ The last steps you'll have to do with your chosen tools is simply setting up your desired keybinds! Make sure you setup the `Test` keybind as it will be critical for setting up the game. Once you've done that, launch your game for the first time by double clicking the `.bat` you setup and the game should load.
+
+ If it's your first time running the game, you'll immediately be greeted with this screen, oh no!
+
+
+
+!!! tip ""
+ Ignore this message, simply hit your `Test` keybind and continue onto this.
+
+
+
+!!! tip ""
+ Hit the `Test` keybinding again to initialize the backup data, a message will pop up stating it's been initialized.
+
+
+
+!!! tip ""
+ Lastly, you'll run into this error message as well, let's work on eliminating these messages. Let the game run for a bit until the monitor check is complete and you should be taken to the service menu pictured below.
+
+
+
+!!! tip ""
+ Start by navigating up to `CLOCK` and entering that menu.
+
+
+
+!!! tip ""
+ Simply hit save and exit and leave, the clock will be saved. Then, back in the service menu, go up to `GAME OPTIONS`
+
+
+
+!!! tip ""
+ Once inside that menu, navigate your way up to `DEFINITION TYPE` and choose either `HD` or `HD*` depending on your preferences, both run the game at 720p but have a timing difference addressed on the FAQ page. It might be worth noting that the `HD*` option is no longer present as of beatmania IIDX 26 ROOTAGE.
+
+
+
+!!! tip ""
+ The game will then count down asking you to confirm the selection before reverting, just hit `YES` assuming it loaded just fine on your computer. Then, exit out of that menu and head to `NETWORK OPTIONS` from back inside the service menu.
+
+
+
+!!! tip ""
+ From here, we will need to set a shop name to play, so select the `SHOP NAME SETTING` option. Once inside, name your shop whatever you desire! For the purpose of the guide, we named it `Guide` but highly encourage fun and/or lazy names. Once that's done go to `EXIT` and then `SAVE AND EXIT` inside of `NETWORK OPTIONS` once you've chosen your desired name, as pictured below.
+
+
+
+
+
+!!! tip ""
+ You're all done! From the service menu select `GAME MODE` and the game should load ready to be played! Have fun!
+
+!!! warning "Have any other errors?"
+ Check out the [Troubleshooting](troubleshooting.md) section and [Error Code](/errorcodes/konami.md) section to resolve any issues not seen in this guide to greater depth.
\ No newline at end of file
diff --git a/docs/games/konami/iidx/25_cannonballers/troubleshooting.md b/docs/games/konami/iidx/25_cannonballers/troubleshooting.md
new file mode 100644
index 0000000..2935b14
--- /dev/null
+++ b/docs/games/konami/iidx/25_cannonballers/troubleshooting.md
@@ -0,0 +1,70 @@
+
+# Troubleshooting
+
+--8<-- "docs/snippets/common/old_guide.md"
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+## Hardware Specs
+
+!!! tip ""
+ Bemani PC (ADE-6291)
+
+ Konami (2018)
+
+ Based on an AMD Embedded R Series SoC.
+
+ CPU: AMD RX-421BD
+
+ GPU: Radeon R7
+
+ RAM: 4 GB
+
+ OS: Windows 7 Embedded
+
+### My Game Is Running Slow/Lagging
+
+!!! tip ""
+ Make sure you at least meet the above hardware requirements, try to eliminate any unnecessary background processes during play as well.
+
+### My Game Is Running Crazy Fast!
+
+!!! tip ""
+ The most common reason for this is the game is running over its required 60 Hz, the game is hardcoded to run at 60 Hz and this cannot be changed. To solve this, set your monitor's refresh rate to 60 Hz. You can always check on the game's monitor check if the game is fluctuating around 59.94hz, the NTSC standard. If it's not around there and your monitor is indeed set to 60 Hz, consider trying a different panel or forcing vsync on in your GPU's graphics settings.
+
+### Camera Device Error Message
+
+!!! tip ""
+ The game released with two USB cameras and naturally it's looking for them, if you do not have two cameras plugged into your computer then the game outputs this error, which can be ignored simply by hitting `Test` or waiting 60 seconds for it to be auto-dismissed.
+
+ But if you're tired of this message every time you start up the game, the `CAMERA DEVICE ERROR` message can be removed via a patch.
+
+### Occasional Game Stutters During Play
+
+!!! tip ""
+ Sometimes you might have occasional stutters during play, while solutions can vary wildly from general performance issues to bad hard drives, try adding SpiceTools `-realtime` parameter to your .bat file.
+
+### HD and HD*
+
+!!! tip ""
+ This version of IIDX has two HD mode options, `HD` and `HD*` neither is inherently better than the other, the only difference is HD* is an additional + 1.0 offset in-game, the official reasoning is to account for a different set of monitors on arcade cabs. In beatmania IIDX 26 ROOTAGE this option is removed entirely and only HD is present.
+
+### Which Offset Is Which?
+
+!!! tip ""
+ If you're getting too many fasts, increase your offset (+). If you're getting too many slows, decrease your offset (-).
+
+### A Note About SSE 4.2
+
+!!! tip ""
+ In the rare case you are running this game on *very* old hardware, IIDX 25 requires a processor supporting the [SSE 4.2 instruction set](https://en.wikipedia.org/wiki/SSE4#SSE4.2). But, in the event your processor does not have this, there is a patch available to bypass this.
+
+### When I Run This Game All Other Background Audio Is Gone! What's Going On?
+
+!!! tip ""
+ 64-bit versions of IIDX are now utilizing a feature in Windows called [WASAPI exclusive mode](https://docs.microsoft.com/en-us/windows/win32/coreaudio/exclusive-mode-streams) to obtain less audio latency than the former 32-bit versions of the games which used [DirectSound](https://en.wikipedia.org/wiki/DirectSound). Unfortunately, this cannot be changed.
+
+### I'm Not Getting Any Audio/My Audio Is Completely Wrecked and I'm Using an External Dac!
+
+!!! tip ""
+ Several external DACs have issues with [WASAPI exclusive mode](https://docs.microsoft.com/en-us/windows/win32/coreaudio/exclusive-mode-streams) and are unable to be used entirely, it's likely you'll be forced to use your motherboard's sound chip, or find a compatible DAC.
\ No newline at end of file
diff --git a/docs/games/konami/iidx/26_rootage/setup.md b/docs/games/konami/iidx/26_rootage/setup.md
new file mode 100644
index 0000000..11eabce
--- /dev/null
+++ b/docs/games/konami/iidx/26_rootage/setup.md
@@ -0,0 +1,117 @@
+
+# Game Setup
+
+--8<-- "docs/snippets/common/old_guide.md"
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+## Getting Started
+
+!!! tip ""
+ Before we even touch the game, let's fiddle with our audio settings to minimize any potential crashing on startup. In Windows, go to `Playback Devices` and then right click on your default device and go to `Properties`. From there, hit the `Advanced` tab and set your `Default Format` to `44100 Hz` and check both of the options inside `Exclusive Mode` as pictured.
+
+
+
+!!! tip ""
+ Once that's done, it's time to work on setting up your data.
+
+ After downloading your data, the first thing to do is make sure your files aren't set to READ ONLY, make sure to uncheck it from the main folder in the Windows Properties tab if so. Then, put your desired **64-bit** tools inside the game's `contents` folder, and to create a `.bat` file. Pictured below is what your folder should look like, feel free to name your `.bat` file whatever you desire, for the sake of convenience we've named ours `gamestart.bat`.
+
+
+
+## Configuring Your Tools
+
+!!! tip ""
+ Now that you have your files ready, open up your `.bat` file in your desired text editor (we're using [Notepad++](https://notepad-plus-plus.org/)) and edit it with your desired parameters, for the purpose of this guide we will demonstrate both a local network configuration and an online example below with SpiceTools, skip to whichever you're in need of accordingly and please keep in mind you can add whatever additional parameters you desire.
+
+!!! warning "If you're not using SpiceTools:"
+ The overall structure of your .bat file will differ from the guide, namely the initialization of SpiceTools won't be present and potential parameters may differ. As stated above, make sure to check the documentation of your tools to ensure you're using the correct parameters for your needs.
+
+## Configuring for a Local Network
+
+!!! tip ""
+ For our local network configuration example, on a single line in the `.bat` file we're going to type `spice64.exe -ea -w` and save the file.
+
+ What do these different parameters do?
+
+ - `-ea` enables an integrated e-amusement server within SpiceTools.
+ - `-w` will boot the game in windowed mode which will ease our initial setup and testing later, make sure to remove `-w` to run the game fullscreen once you're done setting up!
+
+ Pictured below, the contents of our `gamestart.bat` file in Notepad++.
+
+
+
+## Configuring for an Online Network
+
+!!! tip ""
+ For our online network example we're simply doing the above but with different parameters! On our single line, we're going to type `spice64.exe -p XXXXXXXXXXXXXXXXXXXX -url http://yoururlhere.com/ -w` and save the file.
+
+ What do these different parameters do?
+
+ - `-p` takes your PCBID on your network of choice, simply replace `XXXXXXXXXXXXXXXXXXXX` with your PCBID.
+ - `-url` allows you to specify a custom service URL to connect with, simply replace `http://yoururlhere.com/` with your chosen network's URL.
+ - `-w` will boot the game in windowed mode which will ease our initial setup and testing later, make sure to remove `-w` to run the game fullscreen once you're done setting up!
+
+ Pictured below, the contents of our `gamestart.bat` file in Notepad++.
+
+
+
+!!! tip ""
+ One final note, since you're playing on a network, you will have one additional step of setting up your card file within your chosen tools, make sure to check your server's information on how to setup a card file.
+
+## Final Steps and Setting up the Game
+
+!!! tip ""
+ The last steps you'll have to do with your chosen tools is simply setting up your desired keybinds! Make sure you setup the `Test` keybind as it will be critical for setting up the game. Once you've done that, launch your game for the first time by double clicking the `.bat` you setup and the game should load.
+
+ If it's your first time running the game, you'll immediately be greeted with this screen, oh no!
+
+
+
+!!! tip ""
+ Ignore this message, simply hit your `Test` keybind and continue onto this.
+
+
+
+!!! tip ""
+ Hit the `Test` keybinding again to initialize the backup data, a message will pop up stating it's been initialized.
+
+
+
+!!! tip ""
+ Lastly, you'll run into this error message as well, let's work on eliminating these messages. Let the game run for a bit until the monitor check is complete and you should be taken to the service menu pictured below.
+
+
+
+!!! tip ""
+ Start by navigating up to `CLOCK` and entering that menu.
+
+
+
+!!! tip ""
+ Simply hit save and exit and leave, the clock will be saved. Then, back in the service menu, go up to `GAME OPTIONS`
+
+
+
+!!! tip ""
+ Once inside that menu, navigate your way up to `DEFINITION TYPE` and choose either `SD` or `HD` depending on your preferences.
+
+
+
+!!! tip ""
+ The game will then count down asking you to confirm the selection before reverting, just hit `YES` assuming it loaded just fine on your computer. Then, exit out of that menu and head to `NETWORK OPTIONS` from back inside the service menu.
+
+
+
+!!! tip ""
+ From here, we will need to set a shop name to play, so select the `SHOP NAME SETTING` option. Once inside, name your shop whatever you desire! For the purpose of the guide, we named it `Guide` but highly encourage fun and/or lazy names. Once that's done go to `EXIT` and then `SAVE AND EXIT` inside of `NETWORK OPTIONS` once you've chosen your desired name, as pictured below.
+
+
+
+
+
+!!! tip ""
+ You're all done! From the service menu select `GAME MODE` and the game should load ready to be played! Have fun!
+
+!!! warning "Have any other errors?"
+ Check out the [Troubleshooting](troubleshooting.md) section and [Error Code](/errorcodes/konami.md) section to resolve any issues not seen in this guide to greater depth.
\ No newline at end of file
diff --git a/docs/games/konami/iidx/26_rootage/troubleshooting.md b/docs/games/konami/iidx/26_rootage/troubleshooting.md
new file mode 100644
index 0000000..e437688
--- /dev/null
+++ b/docs/games/konami/iidx/26_rootage/troubleshooting.md
@@ -0,0 +1,70 @@
+
+# Troubleshooting
+
+--8<-- "docs/snippets/common/old_guide.md"
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+## Hardware Specs
+
+!!! tip ""
+ Bemani PC (ADE-6291)
+
+ Konami (2018)
+
+ Based on an AMD Embedded R Series SoC.
+
+ CPU: AMD RX-421BD
+
+ GPU: Radeon R7
+
+ RAM: 4 GB
+
+ OS: Windows 7 Embedded
+
+### My Game Is Running Slow/Lagging
+
+!!! tip ""
+ Make sure you at least meet the above hardware requirements, try to eliminate any unnecessary background processes during play as well.
+
+### My Game Is Running Crazy Fast!
+
+!!! tip ""
+ The most common reason for this is the game is running over its required 60 Hz, the game is hardcoded to run at 60 Hz and this cannot be changed. To solve this, set your monitor's refresh rate to 60 Hz. You can always check on the game's monitor check if the game is fluctuating around 59.94hz, the NTSC standard. If it's not around there and your monitor is indeed set to 60 Hz, consider trying a different panel or forcing vsync on in your GPU's graphics settings.
+
+### Camera Device Error Message
+
+!!! tip ""
+ The game released with two USB cameras and naturally it's looking for them, if you do not have two cameras plugged into your computer then the game outputs this error, which can be ignored simply by hitting `Test` or waiting 60 seconds for it to be auto-dismissed.
+
+ But if you're tired of this message every time you start up the game, the `CAMERA DEVICE ERROR` message can be removed via a patch.
+
+### Occasional Game Stutters During Play
+
+!!! tip ""
+ Sometimes you might have occasional stutters during play, while solutions can vary wildly from general performance issues to bad hard drives, try adding SpiceTools `-realtime` parameter to your .bat file.
+
+### HD and HD*
+
+!!! tip ""
+ This version of IIDX has removed having two HD mode options, leaving only HD. `HD` and `HD*` neither is inherently better than the other, the only difference is HD* is an additional + 1.0 offset in-game, now applied to the lone `HD` mode. The official reasoning is to account for a different set of monitors on arcade cabs.
+
+### Which Offset Is Which?
+
+!!! tip ""
+ If you're getting too many fasts, increase your offset (+). If you're getting too many slows, decrease your offset (-).
+
+### A Note About SSE 4.2
+
+!!! tip ""
+ In the rare case you are running this game on *very* old hardware, IIDX 26 requires a processor supporting the [SSE 4.2 instruction set](https://en.wikipedia.org/wiki/SSE4#SSE4.2). But, in the event your processor does not have this, there is a patch available to bypass this.
+
+### When I Run This Game All Other Background Audio Is Gone! What's Going On?
+
+!!! tip ""
+ 64-bit versions of IIDX are now utilizing a feature in Windows called [WASAPI exclusive mode](https://docs.microsoft.com/en-us/windows/win32/coreaudio/exclusive-mode-streams) to obtain less audio latency than the former 32-bit versions of the games which used [DirectSound](https://en.wikipedia.org/wiki/DirectSound). Unfortunately, this cannot be changed.
+
+### I'm Not Getting Any Audio/My Audio Is Completely Wrecked and I'm Using an External Dac!
+
+!!! tip ""
+ Several external DACs have issues with [WASAPI exclusive mode](https://docs.microsoft.com/en-us/windows/win32/coreaudio/exclusive-mode-streams) and are unable to be used entirely, it's likely you'll be forced to use your motherboard's sound chip, or find a compatible DAC.
\ No newline at end of file
diff --git a/docs/games/konami/iidx/27_heroicverse/extras.md b/docs/games/konami/iidx/27_heroicverse/extras.md
new file mode 100644
index 0000000..6d9dde8
--- /dev/null
+++ b/docs/games/konami/iidx/27_heroicverse/extras.md
@@ -0,0 +1,74 @@
+
+# Extra Information
+
+--8<-- "docs/snippets/common/old_guide.md"
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+## Notes
+
+!!! tip ""
+ Booting the game in Lightning Mode requires a few things. To start off with, you will need to enable the `-iidxtdj` option in SpiceTools and you will also need to enable the `Enable Lightning Mode` patch.
+
+ In doing so, and subsequently every time you choose to switch between the two modes, you will want to delete everything inside your `dev/nvram` folder, and redo the setup process again with initializing the backup date, setting the clock, shop name, and the definition type.
+
+ SpiceTools as of 10/26/2020 has some updated features to work with this as well. Namely, the ability to toggle the Lightning Model subscreen via the `Toggle Subscreen` option in the Buttons tab. You can use your mouse to navigate the touchscreen as desired. Enter your pin, toggle buttons, etc.
+
+ SpiceCompanion has also as of 10/26/2020 added a brand new Screen feature as well. Using SpiceCompanion, you can receive the subscreen on your phone/tablet/etc and then use your device as a touch device for the subscreen. Do note that at this time it will not work while the game is running in windowed mode. If you run into performance issues, go to the settings tab to adjust things like the Screen Quality, Screen Threads, and Screen Divide, this feature is heavily dependent on connection and you will notice as you bump up the quality that the ping will increase as well. It may take some fiddling to find the most ideal settings for your setup.
+
+## Lightning-specific Troubleshooting
+
+!!! tip ""
+ Below are the two main issues that have arisen for users utilizing this guide and general startup practices.
+
+## Hardware Specs
+
+!!! tip ""
+
+ Bemani PC Type 11 (ARESPEAR C300)
+
+ Konami (2019)
+
+ Based on KONAMI ARESPEAR C300 gaming PC.
+
+ CPU: Intel i5-9400F 2.9Ghz
+
+ GPU: GIGABYTE GeForce GTX 1650 1530Mhz 4GB
+
+ RAM: 8 GB DDR4
+
+ STORAGE: Innodisk 2.5" 3ME3 SATA SSD 256GB
+
+ AUDIO: ASUS Xonar AE
+
+ OS: Windows 10 IoT Enterprise
+
+## Enabling Lighting Mode Patch
+
+!!! tip ""
+ If you get a stack trace in your `log.txt` with the following line...
+
+ `I:stackwalker: 00000001805FC970 (bm2dx): (unknown): dll_entry_main`
+
+ Please enable the lightning mode patch in SpiceTool's patch manager.
+
+## Audio Related Crash
+
+!!! tip ""
+ If you get a stack trace in your `log.txt` that looks like this:..
+
+ `exception raised: EXCEPTION_ACCESS_VIOLATION`
+
+ `[2020/10/22 18:20:21] I:signal: printing callstack`
+
+ `[2020/10/22 18:20:21] I:stackwalker: 000000018026E906 (bm2dx): (unknown): (unknown)`
+
+ For cab type 1 (LDJ), change your audio device to motherboard audio and/or use -audiobackend asio `-asiodriverid ... -audiodummy`
+
+ For cab type 2 (TDJ, with `-iidxtdj` or another means), you have a few options:
+
+ 1) Use `-iidxasio "Driver Name Here"` to set the ASIO driver used by IIDX's own ASIO handler. (Does not work with all ASIO drivers, they designed it to work best with a specific revision of the XONAR SOUNCARD(64))
+
+ 2) Use `-iidxsounddevice wasapi` to set IIDX to use WASAPI instead of its own ASIO handler.
+
+ 3) Use `-iidxsounddevice wasapi` along with `-audiobackend asio ...` to have the game pipe audio through Spice's own ASIO handler which is more compatible with various ASIO drivers
\ No newline at end of file
diff --git a/docs/games/konami/iidx/27_heroicverse/setup.md b/docs/games/konami/iidx/27_heroicverse/setup.md
new file mode 100644
index 0000000..d66ad5f
--- /dev/null
+++ b/docs/games/konami/iidx/27_heroicverse/setup.md
@@ -0,0 +1,129 @@
+
+# Game Setup
+
+--8<-- "docs/snippets/common/old_guide.md"
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+## Getting Started
+
+!!! tip ""
+ Before we even touch the game, let's fiddle with our audio settings to minimize any potential crashing on startup. In Windows, go to `Playback Devices` and then right click on your default device and go to `Properties`. From there, hit the `Advanced` tab and set your `Default Format` to `44100 Hz` and check both of the options inside `Exclusive Mode` as pictured.
+
+
+
+!!! tip ""
+ Once that's done, it's time to work on setting up your data.
+
+ After downloading your data, the first thing to do is make sure your files aren't set to READ ONLY, make sure to uncheck it from the main folder in the Windows Properties tab if so. Then, put your desired **64-bit** tools inside the game's `contents` folder, Pictured below is what your folder should look like.
+
+
+
+## Configuring Your Tools
+
+!!! tip ""
+ Now that you have your files ready, open up `spicecfg.exe` and head to the `Options` where we'll set our desired parameters. For the purpose of this guide, we will demonstrate both a local network configuration and an online example below with SpiceTools, skip to whichever you're in need of accordingly and please keep in mind you can add whatever additional parameters you desire.
+
+!!! warning "If you're not using SpiceTools:"
+ You will have to likely generate a .bat file given your existing tool's documentation. As stated above, make sure to check the documentation of your tools to ensure you're using the correct parameters for your needs and to consult appropriate support if you're unsure how to do this.
+
+## Configuring for a Local Network
+
+!!! tip ""
+ For our local network configuration example, inside `Options` tab we're going to click on the following: `E-Amusement Emulation: -ea` and `Windowed Mode: -w` to enable them.
+
+ What do these different parameters do?
+
+ - `-ea` enables an integrated e-amusement server within SpiceTools.
+ - `-w` will boot the game in windowed mode which will ease our initial setup and testing later, make sure to remove `-w` to run the game fullscreen once you're done setting up!
+
+ Pictured below, the selected options inside the `Options` tab in `spicecfg.exe`.
+
+
+
+## Configuring for an Online Network
+
+!!! tip ""
+ For our online network example we're simply doing the above but with different parameters! On the `Service URL: -url` parameter, we're going to input our chosen network URL like so: `http://yoururlhere.com/`
+
+ To go alongside this, we'll also be inputting into the `PCBID: -p` parameter, the PCBID given to us from our network, like so: `XXXXXXXXXXXXXXXXXXXX`
+
+ Lastly, we'll click on the `Windowed Mode: -w` parameter.
+
+ What do these different parameters do?
+
+ - `-url` allows you to specify a custom service URL to connect with, simply replace `http://yoururlhere.com/` with your chosen network's URL.
+ - `-p` takes your PCBID on your network of choice, simply replace `XXXXXXXXXXXXXXXXXXXX` with your PCBID.
+ - `-w` will boot the game in windowed mode which will ease our initial setup and testing later, make sure to remove `-w` to run the game fullscreen once you're done setting up!
+
+ Pictured below, the selected options inside the `Options` tab in `spicecfg.exe`.
+
+
+
+!!! tip ""
+ One final note, since you're playing on a network, you will have one additional step of setting up your card file within your chosen tools, make sure to check your server's information on how to setup a card file.
+
+## Final Steps and Setting up the Game
+
+!!! tip ""
+ The last steps you'll have to do with your chosen tools is simply setting up your desired keybinds inside the `Buttons` and `Analogs` tabs! Make sure you setup the `Test` keybind as it will be critical for setting up the game.
+
+
+!!! tip ""
+ Once you've done that, launch your game for the first time by double clicking the `spice64.exe` and the game should load with your chosen parameters from `spicecfg.exe`.
+
+ If it's your first time running the game, you'll immediately be greeted with this screen, oh no!
+
+
+
+!!! tip ""
+ Ignore this message, simply hit your `Test` keybind and continue onto this.
+
+
+
+!!! tip ""
+ Hit the `Test` keybinding to initialize the backup data, a message will pop up stating it's been initialized.
+
+
+
+!!! tip ""
+ You'll also run into this error message as well, let's work on eliminating these messages. Let the game run for a bit until the monitor check is complete and you should be taken to the service menu pictured below.
+
+
+
+!!! tip ""
+ Start by navigating up to `CLOCK` and entering that menu.
+
+
+
+!!! tip ""
+ Simply hit save and exit and leave, the clock will be saved. Then, back in the service menu, go up to `GAME OPTIONS`
+
+
+
+!!! tip ""
+ Once inside that menu, navigate your way up to `DEFINITION TYPE` and choose either `SD` or `HD` depending on your preferences.
+
+
+
+!!! tip ""
+ The game will then count down asking you to confirm the selection before reverting, just hit `YES` assuming it loaded just fine on your computer. Then, exit out of that menu and head to `NETWORK OPTIONS` from back inside the service menu.
+
+ If it doesn't transition to HD, after you've saved, you can simply reboot the game and all should be well.
+
+
+
+!!! tip ""
+ The final thing we need to set is here inside `NETWORK OPTIONS`, we will need to set a shop name to play, so select the `SHOP NAME SETTING` option. Once inside, name your shop whatever you desire! For the purpose of the guide, we named it `Guide` but highly encourage fun and/or lazy names. Once that's done go to `EXIT` and then `SAVE AND EXIT` inside of `NETWORK OPTIONS` once you've chosen your desired name, as pictured below.
+
+
+
+
+
+!!! tip ""
+ You're all done! From the service menu select `GAME MODE` and the game should load ready to be played! Have fun!
+
+!!! warning "Have any other errors?"
+ Check out the [Troubleshooting](troubleshooting.md) section and [Error Code](/errorcodes/konami.md) section to resolve any issues not seen in this guide to greater depth.
+
+ Lightning Mode specifics can be found in the [Extra Information](extras.md#lightning-specific-troubleshooting)
\ No newline at end of file
diff --git a/docs/games/konami/iidx/27_heroicverse/troubleshooting.md b/docs/games/konami/iidx/27_heroicverse/troubleshooting.md
new file mode 100644
index 0000000..bbe8329
--- /dev/null
+++ b/docs/games/konami/iidx/27_heroicverse/troubleshooting.md
@@ -0,0 +1,63 @@
+
+# Troubleshooting
+
+--8<-- "docs/snippets/common/old_guide.md"
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+## Hardware Specs
+
+!!! tip ""
+
+ (These are the specs for non-lightning model cab running Heroic Verse)
+
+ Bemani PC Type 9 (ADE-6291)
+
+ Konami (2017)
+
+ Based on an AMD Embedded R Series SoC.
+
+ CPU: AMD RX-421BD 2.1/3.4GHz APU
+
+ GPU: Radeon R7 800Mhz
+
+ RAM: 4 GB
+
+ STORAGE: innodisk 3ME2 mSATA SSD 256GB
+
+ OS: Windows 7 Embedded
+
+### My Game Is Running Slow/Lagging
+
+!!! tip ""
+ Make sure you at least meet the above hardware requirements, try to eliminate any unnecessary background processes during play as well.
+
+### My Game Is Running Crazy Fast!
+
+!!! tip ""
+ The most common reason for this is the game is running over its required 60 Hz or 120 Hz framerate, depending on if you're in LDJ or TDJ mode. The game is hardcoded to run at these specific framerates and this cannot be changed. To solve this, set your monitor's refresh rate to match if you're in LDJ 60 Hz or TDJ 120 Hz mode. You can always check on the game's monitor check if the game is fluctuating around 59.94hz, the NTSC standard or around 120.00hz. If it's not around there and your monitor is indeed set correctly for the given mode, consider trying a different panel or forcing vsync on in your GPU's graphics settings.
+
+### Occasional Game Stutters During Play
+
+!!! tip ""
+ Sometimes you might have occasional stutters during play, while solutions can vary wildly from general performance issues to bad hard drives, try adding SpiceTools `-realtime` parameter to your .bat file.
+
+### Which Offset Is Which?
+
+!!! tip ""
+ If you're getting too many fasts, increase your offset (+). If you're getting too many slows, decrease your offset (-).
+
+### A Note About SSE 4.2
+
+!!! tip ""
+ In the rare case you are running this game on *very* old hardware, IIDX 27 requires a processor supporting the [SSE 4.2 instruction set](https://en.wikipedia.org/wiki/SSE4#SSE4.2). But, in the event your processor does not have this, there is a patch available to bypass this.
+
+### When I Run This Game All Other Background Audio Is Gone! What's Going On?
+
+!!! tip ""
+ 64-bit versions of IIDX are now utilizing a feature in Windows called [WASAPI exclusive mode](https://docs.microsoft.com/en-us/windows/win32/coreaudio/exclusive-mode-streams) to obtain less audio latency than the former 32-bit versions of the games which used [DirectSound](https://en.wikipedia.org/wiki/DirectSound). Unfortunately, this cannot be changed.
+
+### I'm Not Getting Any Audio/My Audio Is Completely Wrecked and I'm Using an External Dac!
+
+!!! tip ""
+ Several external DACs have issues with [WASAPI exclusive mode](https://docs.microsoft.com/en-us/windows/win32/coreaudio/exclusive-mode-streams) and are unable to be used entirely, it's likely you'll be forced to use your motherboard's sound chip, or find a compatible DAC.
\ No newline at end of file
diff --git a/docs/games/konami/iidx/30_resident/extras.md b/docs/games/konami/iidx/30_resident/extras.md
new file mode 100644
index 0000000..72f1efa
--- /dev/null
+++ b/docs/games/konami/iidx/30_resident/extras.md
@@ -0,0 +1,88 @@
+
+# Extra Information
+
+## Standard and Lightning modes
+
+!!! warning "Lightning mode requires a 120 Hz capable monitor"
+
+!!! tip ""
+
+ To make use of the Lightning Mode, which unlocks the subscreen and 120FPS, we need to go to the `contents\prop` folder and edit the `ea3-config.xml` file.
+
+ We're interested in these lines:
+
+ ```xml
+
+# Game Setup
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+## Standard and Lightning modes
+
+!!! note ""
+
+ Before proceeding with the setup, it's important to understand the two cabinet types for IIDX:
+
+ - **Lightning (TDJ/LDJ-010)**:
+
+ - Runs at 120 FPS
+ - Requires a 120 Hz main monitor
+ - Optional second touchscreen 60 Hz monitor called a subscreen
+
+ - **Standard/Legacy (LDJ/LDJ-003/LDJ-012)**:
+
+ - Runs at 60 FPS
+ - Requires a 60 Hz main monitor
+ - No subscreen
+
+ The game data comes in three variants based on the `bm2dx.dll` file.
+ You can patch an LDJ dll to run in TDJ mode, but this will disable video recording.
+
+ For simplicity, we'll use "TDJ" for Lightning Mode and "LDJ" for Standard Mode throughout our guides.
+
+## Preparing data
+
+--8<-- "docs/snippets/common/data_readonly.md"
+
+ The **complete game data** should be approximately **95 GB or larger**.
+ If your data is significantly smaller, you likely have an update archive instead of the full game data.
+
+ Here's what the expected data structure should look like:
+
+ ```
+ 📂data
+ 📂dev
+ 📂modules
+ 📂prop
+ ```
+
+--8<-- "docs/snippets/konami/common/data_bad.md"
+
+!!! info "If your data is already up-to-date, you can skip ahead to the [Installing spice2x](#installing-spice2x) section"
+
+## Updating data
+
+!!! danger "Make sure you're using the right update for your current game version"
+
+ IIDX updates have `LDJ` and one or two datecodes in their archive names.
+
+ **Single datecode:** Contains one update (e.g., `LDJ_NewDateCode.7z`)
+ **Two datecodes:** Updates from the older to newer version (e.g., `LDJ_OldDateCode-NewDateCode.rar`)
+
+ A date code should look something like this: `YYYYMMDDXX`
+
+ In the two-datecode example:
+
+ - `OldDateCode` is the older date, the game version required to apply this update
+ - `NewDateCode` is the newer date, and is the version you'll arrive at after applying the update
+
+--8<-- "docs/snippets/konami/common/data_update.md"
+
+## Installing spice2x
+
+--8<-- "docs/snippets/konami/common/spice2x64_install.md"
+
+ ``` hl_lines="5-6"
+ 📂data
+ 📂dev
+ 📂modules
+ 📂prop
+ 🌶️spice64.exe
+ 🌶️spicecfg.exe
+ ```
+
+--8<-- "docs/snippets/konami/common/spice2x64_stubs.md"
+
+## Configuring spice2x
+
+--8<-- "docs/snippets/konami/common/spicecfg_preamble.md"
+
+=== "Buttons"
+
+--8<-- "docs/snippets/konami/common/spicecfg_buttons.md"
+
+--8<-- "docs/snippets/konami/iidx/spicecfg_buttons.md"
+
+--8<-- "docs/snippets/konami/common/spicecfg_buttons_additionalinfo.md"
+
+=== "Analogs"
+
+--8<-- "docs/snippets/konami/iidx/spicecfg_analogs.md"
+
+=== "Overlay"
+
+--8<-- "docs/snippets/konami/common/spicecfg_overlay.md"
+
+=== "Lights"
+
+--8<-- "docs/snippets/konami/common/spicecfg_lights.md"
+
+=== "Cards"
+
+--8<-- "docs/snippets/konami/common/spicecfg_cards.md"
+
+=== "Patches"
+
+--8<-- "docs/snippets/konami/common/spicecfg_patches.md"
+
+=== "API"
+
+--8<-- "docs/snippets/konami/common/spicecfg_nochange.md"
+
+=== "Options"
+
+--8<-- "docs/snippets/konami/iidx/spicecfg_options_disablecams.md"
+
+--8<-- "docs/snippets/konami/common/spicecfg_options_nvprofile.md"
+
+--8<-- "docs/snippets/konami/iidx/spicecfg_options_tdj.md"
+
+=== "Advanced"
+
+--8<-- "docs/snippets/konami/iidx/spicecfg_advanced_camhook.md"
+
+=== "Development"
+
+--8<-- "docs/snippets/konami/common/spicecfg_nochange.md"
+
+## Configuring audio
+
+--8<-- "docs/snippets/konami/common/setup_audio.md"
+
+## Connecting to a network
+
+--8<-- "docs/snippets/konami/common/setup_network.md"
+
+## Configuring your game
+
+!!! info "Read through the [Extra Information](extras.md) page"
+
+## Installing VCRedist & DirectX
+
+--8<-- "docs/snippets/common/setup_vcredist_directx.md"
+
+## Before playing
+
+--8<-- "docs/snippets/common/before_playing.md"
+
+## First launch
+
+!!! tip ""
+
+ If you've followed all instructions correctly, you're now finally ready to launch the game!
+
+ **First plug your controller if you have one** and run `spice64.exe`, press `Yes` when it asks for elevated privileges.
+
+ If it's your first time running the game, you'll immediately be greeted with this screen.
+
+ 
+
+ Press your `Test` key to initialize the backup data, a message will pop up stating it's been initialized.
+
+ Next, you'll get another error.
+
+ 
+
+ Press your `Test` key again and let the game run for a bit until the monitor check is complete.
+
+ You will now be taken to the service menu.
+
+ 
+
+ Instructions on how to navigate the menu are shown at the bottom of the screen:
+
+ - Press `1` and `2` to go up and down.
+ - Press `6` to select/execute.
+
+ Start by going up to `CLOCK`.
+
+ 
+
+ Here, simply select `SAVE AND EXIT` and the clock will be set.
+
+ You'll be back in the service menu.
+
+ Go to `NETWORK OPTIONS` then `SHOP NAME SETTING`.
+
+ 
+ 
+
+ You will need to set a shop name.
+
+ - Name your shop to whatever you'd like. Again, navigation instructions are at the bottom of the screen.
+ - Go to `EXIT` then `SAVE AND EXIT`.
+
+ 
+
+ Select `GAME MODE`.
+
+
+
+!!! success "You're all done! The game should load up properly now"
+
+## Carding in
+
+!!! info "Before carding in, you have the option to change the game's language by pressing your `EFFECT` key"
+
+??? tip "For LDJ (Standard mode)"
+
+ LDJ should accept keypad number binds:
+
+ - Press your `Keypad Insert Card` button.
+ - Enter your code using your keypad binds.
+
+??? tip "For TDJ (Lightning mode)"
+
+ TDJ will ignore keypad number binds, you need to:
+
+ - Press your `Keypad Insert Card` button.
+ - Press your `Toggle Sub Screen` overlay button *(PgUp by default)* to bring up the sub screen.
+ - Enter your code by clicking on the subscreen's keypad.
+ - If your code is accepted, you may now close the overlay.
+
+## Help
+
+--8<-- "docs/snippets/common/help.md"
\ No newline at end of file
diff --git a/docs/games/konami/iidx/30_resident/troubleshooting.md b/docs/games/konami/iidx/30_resident/troubleshooting.md
new file mode 100644
index 0000000..c570ce9
--- /dev/null
+++ b/docs/games/konami/iidx/30_resident/troubleshooting.md
@@ -0,0 +1,97 @@
+
+# Troubleshooting
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+!!! info "For any issues not covered here, spice2x's [Known issues](https://github.com/spice2x/spice2x.github.io/wiki/Known-issues) page might prove useful"
+
+## Technical problems
+
+### Crashes
+
+!!! info "Riva Tuner Statistics Server (RTSS) and MSI Afterburner are known to cause odd crashes.
+--8<-- "docs/games/konami/iidx/common/31plus/extras.md"
\ No newline at end of file
diff --git a/docs/games/konami/iidx/31_epolis/setup.md b/docs/games/konami/iidx/31_epolis/setup.md
new file mode 100644
index 0000000..da04eb4
--- /dev/null
+++ b/docs/games/konami/iidx/31_epolis/setup.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/konami/iidx/common/31plus/setup.md"
\ No newline at end of file
diff --git a/docs/games/konami/iidx/31_epolis/troubleshooting.md b/docs/games/konami/iidx/31_epolis/troubleshooting.md
new file mode 100644
index 0000000..e4c1d86
--- /dev/null
+++ b/docs/games/konami/iidx/31_epolis/troubleshooting.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/konami/iidx/common/31plus/troubleshooting.md"
\ No newline at end of file
diff --git a/docs/games/konami/iidx/32_pinkycrush/extras.md b/docs/games/konami/iidx/32_pinkycrush/extras.md
new file mode 100644
index 0000000..1b68351
--- /dev/null
+++ b/docs/games/konami/iidx/32_pinkycrush/extras.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/konami/iidx/common/31plus/extras.md"
\ No newline at end of file
diff --git a/docs/games/konami/iidx/32_pinkycrush/setup.md b/docs/games/konami/iidx/32_pinkycrush/setup.md
new file mode 100644
index 0000000..23bdd58
--- /dev/null
+++ b/docs/games/konami/iidx/32_pinkycrush/setup.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/konami/iidx/common/31plus/setup.md"
\ No newline at end of file
diff --git a/docs/games/konami/iidx/32_pinkycrush/troubleshooting.md b/docs/games/konami/iidx/32_pinkycrush/troubleshooting.md
new file mode 100644
index 0000000..b6a77b6
--- /dev/null
+++ b/docs/games/konami/iidx/32_pinkycrush/troubleshooting.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/konami/iidx/common/31plus/troubleshooting.md"
\ No newline at end of file
diff --git a/docs/games/konami/iidx/33_sparkleshower/extras.md b/docs/games/konami/iidx/33_sparkleshower/extras.md
new file mode 100644
index 0000000..ebf5f8b
--- /dev/null
+++ b/docs/games/konami/iidx/33_sparkleshower/extras.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/konami/iidx/common/31plus/extras.md"
\ No newline at end of file
diff --git a/docs/games/konami/iidx/33_sparkleshower/setup.md b/docs/games/konami/iidx/33_sparkleshower/setup.md
new file mode 100644
index 0000000..da4dd06
--- /dev/null
+++ b/docs/games/konami/iidx/33_sparkleshower/setup.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/konami/iidx/common/31plus/setup.md"
\ No newline at end of file
diff --git a/docs/games/konami/iidx/33_sparkleshower/troubleshooting.md b/docs/games/konami/iidx/33_sparkleshower/troubleshooting.md
new file mode 100644
index 0000000..8d9005e
--- /dev/null
+++ b/docs/games/konami/iidx/33_sparkleshower/troubleshooting.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/konami/iidx/common/31plus/troubleshooting.md"
\ No newline at end of file
diff --git a/docs/games/konami/iidx/9thstyle/setup.md b/docs/games/konami/iidx/9thstyle/setup.md
new file mode 100644
index 0000000..3e02f84
--- /dev/null
+++ b/docs/games/konami/iidx/9thstyle/setup.md
@@ -0,0 +1,275 @@
+
+# Game Setup
+
+--8<-- "docs/snippets/common/old_guide.md"
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+## Preparing data
+
+!!! tip ""
+
+ After downloading and extracting your data, we need to make sure your files aren't set to `Read-only`.
+
+ - Right click the folder containing your data, then click on `Properties`.
+ - In the `General` tab go down to `Attributes`, untick `Read-only` and click `Apply`.
+ - A popup will appear, select `Apply changes to this folder, subfolder and files` and press `OK`.
+ - Finally, click `OK` again to exit out of properties.
+
+## Installing Bemanitools
+
+!!! tip ""
+
+ - Download :material-package-down:[Bemanitools](https://github.com/djhackersdev/bemanitools/releases/download/5.48/bemanitools-5.48.zip).
+
+ - Inside :material-zip-box:`bemanitools-5.48.zip` locate :material-zip-box:`iidx-09-to-12.zip`.
+
+ - Extract everything inside the folder that contains the :material-file:`bm2dx.exe` which is located in :material-folder:`\C02\D\C02\JAG`.
+
+ Pictured below is what your folder should look like. We've removed any files not necessary for **9th style**.
+
+
+
+### Using iidxhook-09.conf
+
+!!! tip ""
+
+ - Download the :material-package-down:[Bemanitools supplements](https://github.com/djhackersdev/bemanitools-supplement/releases/download/1.6/bemanitools-supplement-1.6.zip)
+
+ - Open :material-zip-box:`bemanitools-supplement-v1.6.zip` and navigate inside :material-zip-box:`misc.zip`
+
+ - Inside :material-folder:`misc\d3d8to9`, extract :material-file-cog-outline:`d3d8.dll` to :material-folder:`\C02\D\C02\JAG`.
+
+ This enables us to use the graphic options inside :material-file-code:`iidxhook-09.conf` which we will take advantage of.
+
+## Configuring Bemanitools
+
+!!! info "To configure your keybinds, open your :material-file:`config.bat` file"
+
+### Buttons
+
+!!! tip ""
+
+ Double click on the right on a button that you wish to bind, then press the key you want associated with the action.
+
+ With your controller and/or keyboard plugged in, configure your keys for:
+
+ - **Maintenance**: `Service, Test`
+ - **P1 Game buttons**: `1 to 7, Start, EFFECT, VEFX`
+ - **P1 Keypad**: `Keypad Insert Card`
+
+ **Only if** you're playing using a keyboard:
+
+ - **Turntable**: `TT+, TT-` **and optionally** `TT+/-` which alternates between `TT+` and `TT-` on each press.
+
+### Analogs (controller/cab only)
+
+!!! tip ""
+
+ With a controller rather than binding buttons to `TT+` and `TT-`, you need to:
+
+ - Head to the `Analogs` tab at the top.
+ - In `Device`, pick your controller.
+ - In `Control`, pick whichever one corresponds to the turntable.
+ - Turn your turntable ensuring that the preview turns along with it.
+ - Click `OK`, leaving the rest of the settings alone.
+
+### Lights (controller/cab only)
+
+!!! tip ""
+
+ Your controller might support having its lights controlled by the game through bemanitools.
+
+ If it does, here's how you may link different actions to your lights:
+
+ - In `Device`, pick your controller.
+ - In `Game Light`, select the corresponding button that will be used for that light.
+ - Repeat for your other lights.
+
+!!! info "If you'd like to play offline, you can head straight to [Game resolution and locking FPS](#game-resolution-and-locking-fps)"
+
+### Configuring Bemanitools for a network
+
+!!! tip "Head over to the `Network` tab"
+
+!!! tip ""
+ Now we will set up our PIN pad and card.
+
+ - Click on `Keyboard device`
+ - You may or may not have more than one option. To figure out which one is your actual keyboard, select a device inside that list and press a button on the numpad.
+ - Once you have found your correct device, the `Keyboard status` will change **(the number and location of the number does not matter, it only matters that it changed)**.
+ - Grab your card, create a :material-file-document-edit:`.txt` and name it however you like. In this example it's called :material-file-document-edit:`card.txt`
+ - Place the file in a location that is easily accessible and you won't forget. In this case it's in a seperate folder.
+
+!!! info "If you don't have a numpad, make sure to tick `Use top keyboard row for PIN pad input`. This will also change the `Card In` button to `Backspace`"
+
+
+
+## Connecting to a network
+
+!!! tip ""
+
+ - Locate your :material-file-code:`iidxhook-09.conf`
+
+ - Open it with your desired text editor (we're using [Notepad++](https://notepad-plus-plus.org/))
+
+ - Replace the `eamuse.server=localhost:80` with your desired network URL
+
+ - Replace `eamuse.pcbid=XXXXXXXXXXXXXXXXXXXX` **and** `eamuse.eamid=XXXXXXXXXXXXXXXXXXXX` with your PCBID of your network of choice.
+
+ ```
+ # URL (e.g. http://my.eamuse.server:80/whatever) or IPV4 (e.g. 127.0.0.1:80) of the target eamuse server. The port is optional but defaults to 80.
+ eamuse.server=localhost:80
+
+ # PCBID
+ eamuse.pcbid=XXXXXXXXXXXXXXXXXXXX
+
+ # EAMID
+ eamuse.eamid=XXXXXXXXXXXXXXXXXXXX
+ ```
+
+## Game resolution and locking FPS
+
+!!! tip ""
+ We'd like to mention that there are two options when it comes to how the game renders. You can choose between `Linear` and `Point`.
+
+ Below is an example of how both look like.
+
+ ??? info "Linear"
+ 
+
+ ??? info "Point"
+ 
+
+ It comes down to your own prefrence what you decide on, `Linear` is less sharp but doesn't have pixel perfect edges. `Point` is sharp and is pixel perfect.
+
+!!! tip ""
+ Next up, we'll setup borderless window and configure the proper resolution. We're using a `1920x1080` monitor so we will use that.
+
+ Repeat the previous step and open your :material-file-code:`iidxhook-09.conf`. We want to find these lines:
+
+ ```
+ # Software limit the frame rate of the rendering loop in hz, e.g. 60 or 59.95 (0.0 = no software limit)
+ gfx.frame_rate_limit=0.0
+
+ # Run the game windowed
+ gfx.windowed=false
+
+ # Windowed width, 0 for default size
+ gfx.window_width=0
+
+ # Windowed height, 0 for default size
+ gfx.window_height=0
+
+ # Up-/downscale the back buffer's width. This does not change the game's rendering resolution but scales the final frame. Use this to target the native resolution of your monitor/TV, e.g. to avoid over-/underscan, bad image quality or latency caused by the monitors internal upscaler. 0 to disable this feature. Must be set in combination with the corresponding height parameter.
+ gfx.scale_back_buffer_width=0
+
+ # Up-/downscale the back buffer's height. This does not change the game's rendering resolution but scales the final frame. Use this to target the native resolution of your monitor/TV, e.g. to avoid over-/underscan, bad image quality or latency caused by the monitors internal upscaler. 0 to disable this feature. Must be set in combination with the corresponding width parameter.
+ gfx.scale_back_buffer_height=0
+
+ # Filter type to use for up-/downscaling the back buffer. Only used if scaling feature was enabled by setting the scaling width and height parameters. Available types: none, linear, point (refer to D3DTEXTUREFILTERTYPE for explanation).
+ gfx.scale_back_buffer_filter=none
+ ```
+
+ If you can't seem to find them, press `CTRL` + `F` and search for `gfx.frame_rate_limit=0.0`. This will bring you to the first line we want to edit.
+
+!!! tip ""
+ Listed below are the values we want to change them to.
+
+ ```
+ gfx.frame_rate_limit=59.95
+ gfx.windowed=true
+ gfx.window_width=1920
+ gfx.window_height=1080
+ gfx.scale_back_buffer_width=1920
+ gfx.scale_back_buffer_height=1080
+ gfx.scale_back_buffer_filter=linear
+ ```
+ Unless you'd like to have the game properly windowed you can safely ignore `gfx.framed=false`.
+
+ Make sure to decide on whether you want `Linear` or `Point` rendering.
+
+ ```
+ gfx.scale_back_buffer_filter=linear
+ gfx.scale_back_buffer_filter=point
+ ```
+
+## First launch
+
+!!! danger "If you have any issues running the game, refer to the [Troubleshooting](troubleshooting.md) page"
+
+### CLOCK ERROR
+
+!!! tip ""
+
+ If you've followed all instructions correctly, you're now finally ready to launch the game!
+
+ **First plug your controller if you have one** and run :material-file:`gamestart.bat`.
+
+ If it's your first time running the game, you'll immediately be greeted with this screen.
+
+
+
+
+
+!!! tip ""
+ The game will automatically bring you into it's service menu.
+
+
+
+!!! tip ""
+ Instructions on how to navigate the menu are shown at the bottom of the screen.
+
+ - Press `1` and `2` to go up and down.
+ - Press `6` to select/execute.
+
+ Navigate to `CLOCK SETUP`. You do not need to manually change it. Navigate to `SAVE AND EXIT`.
+
+
+
+!!! info "If you'd like to play offline, you can head straight to [Final Notes](#final-notes)"
+
+### Enabling e-AMUSEMENT for Online Play
+
+!!! tip ""
+ From the service menu, go to `e-AMUSEMENT OPTIONS` then `e-AMUSEMENT SETTINGS`.
+
+
+
+
+
+!!! tip ""
+ It'll bring you to this screen, change it so that `e-AMUSEMENT` switches to `ON` and it will look like this:
+
+
+
+
+
+!!! tip ""
+ We will need to set a `SHOP NAME SETTING` and change our `PREFECTURE` otherwise the game will throw errors at us.
+
+
+
+!!! tip ""
+
+ - Name your shop to whatever you'd like. Instructions on how to navigate are at the bottom of the screen.
+ - Navigate to `EXIT` and select it.
+ - Change your prefecture once or how many times you'd like, it doesn't matter as long as it's not the default one.
+
+
+
+!!! tip ""
+ Select `SAVE AND EXIT`. The game will now give you a message, which translated means:
+
+ `e-AMUSEMENT settings have been changed. Please turn the power off and on again.`
+
+ So, close the game and open it again.
+
+
+
+## Final Notes
+
+!!! success "You're all done! Make sure to insert two credits by pressing your `SERVICE` key. Have fun!"
+
+!!! warning "Have any other errors?"
+ Check out the [Troubleshooting](troubleshooting.md) section.
\ No newline at end of file
diff --git a/docs/games/konami/iidx/9thstyle/troubleshooting.md b/docs/games/konami/iidx/9thstyle/troubleshooting.md
new file mode 100644
index 0000000..e1a2405
--- /dev/null
+++ b/docs/games/konami/iidx/9thstyle/troubleshooting.md
@@ -0,0 +1,62 @@
+
+# Troubleshooting
+
+--8<-- "docs/snippets/common/old_guide.md"
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+### My Game Is Running Crazy Fast!
+
+!!! tip ""
+ The most common reason for this is the game is running over its required 59.95hz, the game is hardcoded to run at 59.95hz and this cannot be changed. To solve this, check [Game resolution and locking FPS](setup.md#game-resolution-and-locking-fps) again.
+
+### I'm getting "NETWORK WARNING" instead of "NETWORK OK"
+
+!!! tip ""
+ This can be caused by:
+
+ - Invalid PCBID
+ - Firewall blocking connections
+ - Invalid eamuse url or port specified
+ - Game is not run using the Administrator account
+
+### My background videos aren't working!
+
+!!! tip ""
+
+ You need to install a codec.
+
+ - Open :material-zip-box:`bemanitools-supplement-v1.6.zip` and navigate to :material-folder:`\iidx.zip\iidx\misc\` where :material-file:`CLVSD.ax` is located.
+
+ - Extract :material-file:`CLVSD.ax` inside a :material-folder: folder that you know won't be moved or renamed.
+
+ - Open the :material-console:command prompt as ***administrator***. Now type `regsvr32 "
+
+ Press your `Test` key to initialize the backup data, a message will pop up stating it's been initialized.
+
+ Next, you'll get another error.
+
+
+
+ Press your `Test` key again and let the game run for a bit until the monitor check is complete.
+
+ You will now be taken to the service menu.
+
+
+
+ Instructions on how to navigate the menu are shown at the bottom of the screen:
+
+ - Press `1` and `2` to go up and down.
+ - Press `6` to select/execute.
+
+ Start by going up to `CLOCK`.
+
+
+
+ Here, simply select `SAVE AND EXIT` and the clock will be set.
+
+ You'll be back in the service menu.
+
+ Go to `NETWORK OPTIONS` then `SHOP NAME SETTING`.
+
+
+
+
+ You will need to set a shop name.
+
+ - Name your shop to whatever you'd like. Again, navigation instructions are at the bottom of the screen.
+ - Go to `EXIT` then `SAVE AND EXIT`.
+
+
+
+ Select `GAME MODE`.
+
+
+
+!!! success "You're all done! The game should load up properly now"
+
+## Carding in
+
+!!! info "Before carding in, you have the option to change the game's language by pressing your `EFFECT` key"
+
+??? tip "For LDJ (Standard mode)"
+
+ LDJ should accept keypad number binds:
+
+ - Press your `Keypad Insert Card` button.
+ - Enter your code using your keypad binds.
+
+??? tip "For TDJ (Lightning mode)"
+
+ TDJ will ignore keypad number binds, you need to:
+
+ - Press your `Keypad Insert Card` button.
+ - Press your `Toggle Sub Screen` overlay button *(PgUp by default)* to bring up the sub screen.
+ - Enter your code by clicking on the subscreen's keypad.
+ - If your code is accepted, you may now close the overlay.
+
+## Help
+
+--8<-- "docs/snippets/common/help.md"
\ No newline at end of file
diff --git a/docs/games/konami/iidx/common/31plus/troubleshooting.md b/docs/games/konami/iidx/common/31plus/troubleshooting.md
new file mode 100644
index 0000000..8d5481d
--- /dev/null
+++ b/docs/games/konami/iidx/common/31plus/troubleshooting.md
@@ -0,0 +1,105 @@
+# Troubleshooting
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+!!! info "For any issues not covered here, spice2x's [Known issues](https://github.com/spice2x/spice2x.github.io/wiki/Known-issues) page might prove useful"
+
+## Technical problems
+
+### Crashes
+
+!!! info "Riva Tuner Statistics Server (RTSS) and MSI Afterburner are known to cause odd crashes.
+--8<-- "docs/games/konami/jubeat/common/setup.md"
\ No newline at end of file
diff --git a/docs/games/konami/jubeat/beyondtheavenue/setup.md b/docs/games/konami/jubeat/beyondtheavenue/setup.md
new file mode 100644
index 0000000..1fc0e07
--- /dev/null
+++ b/docs/games/konami/jubeat/beyondtheavenue/setup.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/konami/jubeat/common/setup.md"
\ No newline at end of file
diff --git a/docs/games/konami/jubeat/common/setup.md b/docs/games/konami/jubeat/common/setup.md
new file mode 100644
index 0000000..a7a481e
--- /dev/null
+++ b/docs/games/konami/jubeat/common/setup.md
@@ -0,0 +1,190 @@
+# Game Setup
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+## Preparing data
+
+--8<-- "docs/snippets/common/data_readonly.md"
+
+ The **complete game data** should be approximately **10 GB or larger**.
+ If your data is significantly smaller, you likely have an update archive instead of the full game data.
+
+ Here's what the expected data structure should look like:
+
+ ```
+ 📂data
+ 📂modules
+ 📂prop
+ ⚙️msvcr100.dll
+ ```
+
+!!! danger "If your data does not look like this"
+
+ If you have **other** `.dll` files next to your `data`, `prop`, etc., folders:
+
+ - Create a `modules` folder if it does not exist already
+ - Move all `.dll` files into it
+
+ If extra directories or files are still present (executables, scripts, etc.), **remove them**.
+
+ **This also indicates tampered data, we strongly recommend obtaining clean data from elsewhere.**
+
+!!! info "If your data is already up-to-date, you can skip ahead to the [Installing spice2x](#installing-spice2x) section"
+
+## Updating data
+
+!!! danger "Make sure you're using the right update for your current game version"
+
+ jubeat updates have `L44` and one or two datecodes in their archive names.
+
+ **Single datecode:** Contains one update (e.g., `L44_NewDateCode.7z`)
+ **Two datecodes:** Updates from the older to newer version (e.g., `L44_OldDateCode-NewDateCode.rar`)
+
+ A date code should look something like this: `YYYYMMDDXX`
+
+ In the two-datecode example:
+
+ - `OldDateCode` is the older date, the game version required to apply this update
+ - `NewDateCode` is the newer date, and is the version you'll arrive at after applying the update
+
+--8<-- "docs/snippets/konami/common/data_update.md"
+
+## Installing spice2x
+
+--8<-- "docs/snippets/konami/common/spice2x32_install.md"
+
+ ``` hl_lines="5-6"
+ 📂data
+ 📂modules
+ 📂prop
+ ⚙️msvcr100.dll
+ 🌶️spice.exe
+ 🌶️spicecfg.exe
+ ```
+
+--8<-- "docs/snippets/konami/common/spice2x32_stubs.md"
+
+## Configuring spice2x
+
+--8<-- "docs/snippets/konami/common/spicecfg_preamble.md"
+
+=== "Buttons"
+
+--8<-- "docs/snippets/konami/common/spicecfg_buttons.md"
+
+ !!! tip "Binding your buttons"
+
+ Click on `Bind` or `Naive` then press the key you want associated with the action.
+
+ With your controller and/or keyboard plugged in, configure your keys for:
+
+ - **Maintenance**: `Service, Test`
+ - **Game buttons**: `Button 1 to Button 16`
+ - **Keypad**: `Keypad Insert Card`
+
+ !!! tip "Using a touch screen"
+
+ spice2x supports using a touch screen instead of the 16 game buttons. In that case, you don't need to bind these buttons.
+
+--8<-- "docs/snippets/konami/common/spicecfg_buttons_additionalinfo.md"
+
+=== "Analogs"
+
+--8<-- "docs/snippets/konami/common/spicecfg_nochange.md"
+
+=== "Overlay"
+
+--8<-- "docs/snippets/konami/common/spicecfg_overlay.md"
+
+=== "Lights"
+
+--8<-- "docs/snippets/konami/common/spicecfg_lights.md"
+
+=== "Cards"
+
+--8<-- "docs/snippets/konami/common/spicecfg_cards.md"
+
+=== "Patches"
+
+--8<-- "docs/snippets/konami/common/spicecfg_patches.md"
+
+=== "API"
+
+--8<-- "docs/snippets/konami/common/spicecfg_nochange.md"
+
+=== "Options"
+
+--8<-- "docs/snippets/konami/common/spicecfg_options_nvprofile.md"
+
+=== "Advanced"
+
+--8<-- "docs/snippets/konami/common/spicecfg_nochange.md"
+
+=== "Development"
+
+--8<-- "docs/snippets/konami/common/spicecfg_nochange.md"
+
+## Configuring audio
+
+!!! tip ""
+
+ - Open `spicecfg.exe`
+ - At the very top, click on `Shortcuts` then `Audio Playback Devices`
+ - In the popup window, right click on your default audio device, and click on `Properties`
+ - Go to the `Advanced` tab
+ - Open the `Default Format` dropdown
+ - Pick the `16 bit, 48000 Hz (DVD Quality)` option, click `Apply` then `OK`
+
+ Optionally: go to the `Options` tab in `spicecfg.exe`, and at the very bottom enable `Low Latency Shared Audio` to help mitigate audio latency.
+
+## Connecting to a network
+
+--8<-- "docs/snippets/konami/common/setup_network.md"
+
+## Installing VCRedist & DirectX
+
+--8<-- "docs/snippets/common/setup_vcredist_directx.md"
+
+## Before playing
+
+--8<-- "docs/snippets/common/before_playing.md"
+
+## First launch
+
+!!! tip ""
+
+ If you've followed all instructions correctly, you're now finally ready to launch the game!
+
+ **First plug your controller if you have one** and run `spice.exe`, press `Yes` when it asks for elevated privileges.
+
+ If it's your first time running the game, you'll immediately be greeted with this screen.
+
+ 
+
+ Press your `Test` key to initialize the backup data, another message with the same error will pop up.
+ Press your `Test` key again to open the service menu.
+
+ You will be greeted by a warning asking you to reboot the game, you can safely ignore it for the moment.
+
+ *Instructions on how to navigate the menu are shown on the screen.*
+
+ Go to `GAME OPTIONS`, then `SHOP SETTINGS`.
+
+ 
+
+ You will need to set a shop name.
+
+ - Name your shop to whatever you'd like. Again, navigation instructions are on the screen.
+ - Press the `EXIT` button.
+
+ Then, set the shop area to whatever region you'd like.
+
+ Select `SAVE AND EXIT` then `EXIT`.
+
+ Finally, restart the game.
+
+!!! success "You're all done! The game should load up properly now"
+
+## Help
+
+--8<-- "docs/snippets/common/help.md"
diff --git a/docs/games/konami/jubeat/festo/setup.md b/docs/games/konami/jubeat/festo/setup.md
new file mode 100644
index 0000000..73f99db
--- /dev/null
+++ b/docs/games/konami/jubeat/festo/setup.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/konami/jubeat/common/setup.md"
\ No newline at end of file
diff --git a/docs/games/konami/mfg/setup.md b/docs/games/konami/mfg/setup.md
new file mode 100644
index 0000000..4dbdc3a
--- /dev/null
+++ b/docs/games/konami/mfg/setup.md
@@ -0,0 +1,110 @@
+
+# Game Setup
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+## Preparing Data
+
+--8<-- "docs/snippets/common/data_readonly.md"
+
+ The **complete game data** should be approximately **5 GB or larger**
+
+ Here's what the expected data structure should look like:
+
+ ```
+ 📂prop
+ 📂modules
+ 📂game
+ 📄game.inf
+ ```
+
+--8<-- "docs/snippets/konami/common/data_bad.md"
+
+## Installing spice2x
+
+--8<-- "docs/snippets/konami/common/spice2x64_install.md"
+
+ ``` hl_lines="5-6"
+ 📂prop
+ 📂modules
+ 📂game
+ 📄game.inf
+ 🌶️spice64.exe
+ 🌶️spicecfg.exe
+ ```
+
+## Configuring spice2x
+
+--8<-- "docs/snippets/konami/common/spicecfg_preamble.md"
+
+=== "Buttons"
+
+--8<-- "docs/snippets/konami/common/spicecfg_buttons.md"
+
+ !!! tip "Binding your buttons"
+
+ Click on `Bind` or `Naive` then press the key you want associated with the action.
+
+ With your keyboard plugged in, configure your keys for P1 and/or P2:
+
+ - **Maintenance**: `Service, Test`
+
+ Mahjong Fight Girl is a touchscreen game, so it does not need any extra button configuration beyond the above.
+
+--8<-- "docs/snippets/konami/common/spicecfg_buttons_additionalinfo.md"
+
+=== "Analogs"
+
+--8<-- "docs/snippets/konami/common/spicecfg_nochange.md"
+
+=== "Overlay"
+
+--8<-- "docs/snippets/konami/common/spicecfg_overlay.md"
+
+=== "Lights"
+
+--8<-- "docs/snippets/konami/common/spicecfg_nochange.md"
+
+=== "Cards"
+
+--8<-- "docs/snippets/konami/common/spicecfg_cards.md"
+
+=== "Patches"
+
+--8<-- "docs/snippets/konami/common/spicecfg_nochange.md"
+
+=== "API"
+
+--8<-- "docs/snippets/konami/common/spicecfg_nochange.md"
+
+=== "Options"
+
+--8<-- "docs/snippets/konami/common/spicecfg_options.md"
+
+ !!! tip "Choose Cab Type"
+
+ Mahjong Fight Girl has multiple cab types. **HG** is currently the only supported cab type.
+
+=== "Advanced"
+
+--8<-- "docs/snippets/konami/common/spicecfg_nochange.md"
+
+=== "Development"
+
+--8<-- "docs/snippets/konami/common/spicecfg_nochange.md"
+
+## Connecting to a network
+
+--8<-- "docs/snippets/konami/common/setup_network.md"
+
+## Installing VCRedist & DirectX
+
+--8<-- "docs/snippets/common/setup_vcredist_directx.md"
+
+## Before playing
+
+--8<-- "docs/snippets/common/before_playing.md"
+
+## Help
+
+--8<-- "docs/snippets/common/help.md"
diff --git a/docs/games/konami/mfg/troubleshooting.md b/docs/games/konami/mfg/troubleshooting.md
new file mode 100644
index 0000000..68268f2
--- /dev/null
+++ b/docs/games/konami/mfg/troubleshooting.md
@@ -0,0 +1,13 @@
+
+
+# Troubleshooting
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+!!! info "For any issues not covered here, spice2x's [Known issues](https://github.com/spice2x/spice2x.github.io/wiki/Known-issues) page might prove useful"
+
+## Technical problems
+
+??? tip "I can't select anything on screen"
+
+ Make sure your cab type in spicecfg is set to **HG**
\ No newline at end of file
diff --git a/docs/games/konami/museca/1plushalf/setup.md b/docs/games/konami/museca/1plushalf/setup.md
new file mode 100644
index 0000000..4bd5f43
--- /dev/null
+++ b/docs/games/konami/museca/1plushalf/setup.md
@@ -0,0 +1,152 @@
+
+# Game Setup
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+## Preparing data
+
+--8<-- "docs/snippets/common/data_readonly.md"
+
+ The **complete game data** should be approximately **2.7 GB**.
+
+ Here's what the expected data structure should look like:
+
+ ```
+ 📂data
+ 📂dev
+ 📂modules
+ 📂prop
+ ```
+
+--8<-- "docs/snippets/konami/common/data_bad.md"
+
+## Installing spice2x
+
+--8<-- "docs/snippets/konami/common/spice2x64_install.md"
+
+ ``` hl_lines="5-6"
+ 📂data
+ 📂dev
+ 📂modules
+ 📂prop
+ 🌶️spice64.exe
+ 🌶️spicecfg.exe
+ ```
+
+--8<-- "docs/snippets/konami/common/spice2x64_stubs.md"
+
+## Configuring spice2x
+
+--8<-- "docs/snippets/konami/common/spicecfg_preamble.md"
+
+=== "Buttons"
+
+--8<-- "docs/snippets/konami/common/spicecfg_buttons.md"
+
+ !!! tip "Binding your buttons"
+
+ Click on `Bind` or `Naive` then press the key you want associated with the action.
+
+ With your controller and/or keyboard plugged in, configure your keys for:
+
+ - **Maintenance:** `Service, Test, Start`
+ - **Game buttons:** `Disk# Press (1 to 5), Foot Pedal`
+ - **P1 Keypad**: `Keypad 0 to 9, Keypad Insert Card`
+
+ **Only if** you play with a keyboard:
+
+ - **Disks:** `Disk#- (1 to 5), Disk#+ (1 to 5)` (`Disk#-` is counter-clockwise, while `Disk#+` is clockwise.)
+
+--8<-- "docs/snippets/konami/common/spicecfg_buttons_additionalinfo.md"
+
+=== "Analogs"
+
+ !!! info "This tab is used to bind analog controls like the disks"
+
+ !!! warning "Ignore this tab if you play with a keyboard"
+
+ !!! tip "Bind your controller's disks"
+
+ With a controller, instead of binding your disks in the `Buttons` tab, you need to:
+
+ - Click `Bind`
+ - In `Device`, pick your controller
+ - In `Control`, pick the control that updates the preview when turning the corresponding disk
+ - Click `Close`, leaving the rest of the settings alone
+ - Repeat for your other disks
+
+=== "Overlay"
+
+--8<-- "docs/snippets/konami/common/spicecfg_overlay.md"
+
+=== "Lights"
+
+--8<-- "docs/snippets/konami/common/spicecfg_lights.md"
+
+=== "Cards"
+
+--8<-- "docs/snippets/konami/common/spicecfg_cards.md"
+
+=== "Patches"
+
+--8<-- "docs/snippets/konami/common/spicecfg_patches.md"
+
+=== "API"
+
+--8<-- "docs/snippets/konami/common/spicecfg_nochange.md"
+
+=== "Options"
+
+--8<-- "docs/snippets/konami/common/spicecfg_options.md"
+
+--8<-- "docs/snippets/konami/common/spicecfg_options_nvprofile.md"
+
+=== "Advanced"
+
+--8<-- "docs/snippets/konami/common/spicecfg_nochange.md"
+
+=== "Development"
+
+--8<-- "docs/snippets/konami/common/spicecfg_nochange.md"
+
+## Configuring Audio
+
+--8<-- "docs/snippets/konami/common/setup_audio_wasapiexcl_only.md"
+
+## Connecting to a network
+
+--8<-- "docs/snippets/konami/common/setup_network.md"
+
+## Monitor Orientation
+
+--8<-- "docs/snippets/konami/common/display_portraitfirst.md"
+
+## Installing VCRedist & DirectX
+
+--8<-- "docs/snippets/common/setup_vcredist_directx.md"
+
+## First launch
+
+!!! tip ""
+
+ If you've followed all instructions correctly, you're finally ready to launch the game!
+
+ Run `spice64.exe`, press `Yes` when it asks for elevated privileges.
+
+ The game will go through a series of checks, let it run, if you've done everything properly they'll pass.
+
+ 
+
+ If you're seeing this screen, it means you need to press the `Test` button to initialize the game's backup data.
+
+ Once the game shows `BACKUP DATA: INITIALIZED`, restart the game.
+
+!!! success "You're all done! The game should load up properly now"
+
+## MÚSECA PLUS
+
+!!! info "Since MÚSECA is no longer receiving official updates, community mods like [MÚSECA PLUS](https://museca.plus/) exist to enhance the game with additional content and English translations"
+
+## Help
+
+--8<-- "docs/snippets/common/help.md"
\ No newline at end of file
diff --git a/docs/games/konami/museca/1plushalf/troubleshooting.md b/docs/games/konami/museca/1plushalf/troubleshooting.md
new file mode 100644
index 0000000..3eda4f2
--- /dev/null
+++ b/docs/games/konami/museca/1plushalf/troubleshooting.md
@@ -0,0 +1,66 @@
+
+# Troubleshooting
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+!!! info "For any issues not covered here, spice2x's [Known issues](https://github.com/spice2x/spice2x.github.io/wiki/Known-issues) page might prove useful"
+
+## Technical Problems
+
+??? tip "I'm using a laptop with a hybrid internal+dedicated GPU setup"
+
+ Laptops often have odd issues running data. The game may open on the wrong monitor, run at the wrong resolution or framerate, or simply crashes.
+
+ There is currently no known fix for this, other than maybe playing in windowed mode, or using a desktop PC instead.
+
+### Performance
+
+!!! info "Check out spice2x's [PC optimization](https://github.com/spice2x/spice2x.github.io/wiki/PC-optimization) guide"
+
+??? tip "Game is running too slow/fast"
+
+ Your game is likely running at an incorrect framerate. MÚSECA expects the game to run at 60 fps constantly.
+
+ Try these steps to resolve framerate issues:
+
+ - Verify your monitor's refresh ratae is set at exactly 60 Hz.
+ - Close any software that can affect framerates (like RTSS)
+ - Close unnecessary background programs
+ - Ensure V-SYNC is not forcefully disabled in your graphics card control panel
+ - For NVIDIA users: Enable `NVIDIA profile optimization (-nvprofile)` in spicecfg's `Options` tab
+
+ If issues persist:
+
+ - Double-check that you followed all steps in the [setup guide](setup.md) correctly
+ - Your PC hardware might be insufficient to keep a steady 60 FPS. Make sure your PC meets the requirements of this game.
+ - Your data may be corrupt in one way or another, you could try starting from scratch using trusted data sources.
+
+ Your PC may not meet the specifications for MÚSECA. In the arcade, it runs on a Konami PC (ADE-6291):
+
+ - CPU: AMD RX-421BD
+
+ - GPU: Radeon R7
+
+ - RAM: 4 GB
+
+ - OS: Windows 7 Embedded
+
+## Audio
+
+??? tip "I can't hear anything else than the game!"
+
+ Museca only supports [WASAPI exclusive](https://docs.microsoft.com/en-us/windows/win32/coreaudio/exclusive-mode-streams) for its audio. This means the game takes exclusive control of your audio device while running, which cannot be changed.
+
+??? tip "I'm not getting any audio/My audio is completely wrecked and I'm using an external DAC!"
+
+ Many external DACs do not work with [WASAPI exclusive mode](https://docs.microsoft.com/en-us/windows/win32/coreaudio/exclusive-mode-streams) and therefore won't function with Museca. Usually, you'll need to use your motherboard's onboard audio or a DAC confirmed to be compatible.
+
+## FAQ
+
+??? tip "How to run the game in windowed borderless mode?"
+
+ You'll need to use 3rd party software like [Borderless Gaming](https://github.com/Codeusa/Borderless-Gaming/releases) in order to achieve this.
+
+??? tip "Can the game be run offline?"
+
+ If your game version is PIX-2018073002, this version supports turning off E-Amusement. In order to do that, change the game code to `J:B:A` (`
+# Game Setup
+
+--8<-- "docs/snippets/common/old_guide.md"
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+## Getting Started
+
+!!! tip ""
+ Before we even touch the game, let's fiddle with our audio settings to minimize any potential audio issues on startup. In Windows, go to `Playback Devices` and then right click on your default device and go to `Properties`. From there, hit the `Advanced` tab and set your `Default Format` to `44100 Hz` and check both of the options inside `Exclusive Mode` as pictured.
+
+
+
+!!! tip ""
+ Once that's done, it's time to work on setting up your data.
+
+ After downloading your data, the first thing to do is make sure your files aren't set to READ ONLY, make sure to uncheck it from the main folder in the Windows Properties tab if so. Then, put your desired 64-bit tools inside the game's main folder and to create a `.bat` file. Pictured below is what your folder should look like, feel free to name your `.bat` file whatever you desire, for the sake of convenience we've named ours `gamestart.bat`.
+
+
+
+## Configuring Your Tools
+
+!!! tip ""
+ Now that you have your files ready, open up your `.bat` file in your desired text editor (we're using [Notepad++](https://notepad-plus-plus.org/)) and edit it with your desired parameters, for the purpose of this guide we will demonstrate ONLY a local network configuration with SpiceTools. Why only local? Because none of the most typical places currently support Nostalgia. Regardless, please keep in mind you can add whatever additional parameters you desire.
+
+!!! warning "If you're not using SpiceTools:"
+ The overall structure of your .bat file will differ from the guide, namely the initialization of SpiceTools won't be present and potential parameters may differ. As stated above, make sure to check the documentation of your tools to ensure you're using the correct parameters for your needs.
+
+## Configuring for a Local Network
+
+!!! tip ""
+ For our local network configuration example, on a single line in the `.bat` file we're going to type `spice64.exe -ea -w` and save the file.
+
+ What do these different parameters do?
+
+ - `-ea` enables an integrated e-amusement server within SpiceTools.
+ - `-w` will boot the game in windowed mode which will ease our initial setup and testing later, make sure to remove `-w` to run the game fullscreen once you're done setting up!
+
+## Configuring for an Online Network
+
+!!! tip ""
+ For our online network example we're simply doing the above but with different parameters! On our single line, we're going to type `spice64.exe -p XXXXXXXXXXXXXXXXXXXX -url http://yoururlhere.com/ -w` and save the file.
+
+ What do these different parameters do?
+
+ - `-p` takes your PCBID on your network of choice, simply replace `XXXXXXXXXXXXXXXXXXXX` with your PCBID.
+ - `-url` allows you to specify a custom service URL to connect with, simply replace `http://yoururlhere.com/` with your chosen network's URL.
+ - `-w` will boot the game in windowed mode which will ease our initial setup and testing later, make sure to remove `-w` to run the game fullscreen once you're done setting up!
+
+## Final Steps and Setting up the Game
+
+!!! tip ""
+ The last steps you'll have to do with your chosen tools is simply setting up your desired keybinds! Make sure you setup the `Test` keybind as it will be critical for setting up the game. Once you've done that, launch your game for the first time by double clicking the `.bat` you setup and the game should load.
+
+ If it's your first time running the game, you should be automatically forced into the service menu with lots of scary flashing notifications as pictured below, let's work through them.
+
+
+
+!!! tip ""
+ Interestingly, only the red flashing ones really take any effort to deal with. You can start by entering and exiting the following menus: `SOUND OPTIONS`, `GAME OPTIONS`, `COIN OPTIONS`, `ECOMODE OPTIONS`, and `NETWORK OPTIONS`.
+
+ Once you've done that, enter `CLOCK` and set the clock by hitting `SAVE AND EXIT` as pictured below.
+
+
+
+!!! tip ""
+ The final menu we must deal with is `VIRTUAL COIN`, enter the menu and select `OPERATION SETTINGS` as seen below.
+
+
+
+!!! tip ""
+ Once inside this menu, we'll need to deal with all 4 blinking options, let's start by entering the `TAX RATE SETTING` menu, shown below.
+
+
+
+!!! tip ""
+ Set the tax rate by simply selecting `SAVE AND EXIT` while will take us back into the `OPERATING SETTINGS`. Pictured below is the `TAX RATE SETTING` menu.
+
+
+
+!!! tip ""
+ Once back inside the `TAX RATE SETTING` menu, we must deal with the three blinking `PATTERN` options. Doing so is effortless, simply enter all three menus one by one and hit `SAVE AND EXIT` just as we did for the `TAX RATE SETTING` in the previous step. Pictured below is the inside of `PATTERN 1`.
+
+
+
+!!! tip ""
+ After saving and exiting all three `PATTERN` options, you're all done! From the service menu select `GAME MODE` and the game should load ready to be played! Have fun!
+
+!!! warning "Have any other errors?"
+ Check out the [Troubleshooting](troubleshooting.md) section and [Error Code](/errorcodes/konami.md) section to resolve any issues not seen in this guide to greater depth.
diff --git a/docs/games/konami/nostalgia/forte/troubleshooting.md b/docs/games/konami/nostalgia/forte/troubleshooting.md
new file mode 100644
index 0000000..d9beb39
--- /dev/null
+++ b/docs/games/konami/nostalgia/forte/troubleshooting.md
@@ -0,0 +1,44 @@
+
+# Troubleshooting
+
+--8<-- "docs/snippets/common/old_guide.md"
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+## Hardware Specs
+
+!!! tip ""
+ Konami PC Type 6 (ADE-704A)
+
+ Based on an AMD Embedded R Series SoC.
+
+ CPU: Intel Celeron B810
+
+ GPU: AMD Radeon E4690
+
+ OS: Windows 7 Embedded
+
+### My Game Is Running Slow/Lagging
+
+!!! tip ""
+ Make sure you at least meet the above hardware requirements, try to eliminate any unnecessary background processes during play as well.
+
+### My Game Is Running Crazy Fast!
+
+!!! tip ""
+ The most common reason for this is the game is running over its required 60 Hz, the game is hardcoded to run at 60 Hz and this cannot be changed. To solve this, set your monitor's refresh rate to 60 Hz. You can always check on the game's monitor check if the game is fluctuating around 59.94hz, the NTSC standard. If it's not around there and your monitor is indeed set to 60 Hz, consider trying a different panel or forcing vsync on in your GPU's graphics settings.
+
+### Occasional Game Stutters During Play
+
+!!! tip ""
+ Sometimes you might have occasional stutters during play, while solutions can vary wildly from general performance issues to bad hard drives, try adding SpiceTools `-realtime` parameter to your .bat file.
+
+### Which Offset Is Which?
+
+!!! tip ""
+ If you're getting too many fasts, increase your offset (+). If you're getting too many slows, decrease your offset (-).
+
+### No Matter What I Do, the Game Crashes and I Have Multiple Monitors!
+
+!!! tip ""
+ This problem is somewhat irregular, but sometimes Nostalgia has issues booting with multiple monitors present, particularly when trying to boot the game windowed. Make sure you're running the latest SpiceTools which has attempted to resolve all instances of this issue.
\ No newline at end of file
diff --git a/docs/games/konami/nostalgia/op2/setup.md b/docs/games/konami/nostalgia/op2/setup.md
new file mode 100644
index 0000000..079c269
--- /dev/null
+++ b/docs/games/konami/nostalgia/op2/setup.md
@@ -0,0 +1,91 @@
+
+# Game Setup
+
+--8<-- "docs/snippets/common/old_guide.md"
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+## Getting Started
+
+!!! tip ""
+ Before we even touch the game, let's fiddle with our audio settings to minimize any potential audio issues on startup. In Windows, go to `Playback Devices` and then right click on your default device and go to `Properties`. From there, hit the `Advanced` tab and set your `Default Format` to `44100 Hz` and check both of the options inside `Exclusive Mode` as pictured.
+
+
+
+!!! tip ""
+ Once that's done, it's time to work on setting up your data.
+
+ After downloading your data, the first thing to do is make sure your files aren't set to READ ONLY, make sure to uncheck it from the main folder in the Windows Properties tab if so. Then, put your desired 64-bit tools inside the game's main folder and to create a `.bat` file. Pictured below is what your folder should look like, feel free to name your `.bat` file whatever you desire, for the sake of convenience we've named ours `gamestart.bat`.
+
+
+
+## Configuring Your Tools
+
+!!! tip ""
+ Now that you have your files ready, open up your `.bat` file in your desired text editor (we're using [Notepad++](https://notepad-plus-plus.org/)) and edit it with your desired parameters, for the purpose of this guide we will demonstrate ONLY a local network configuration with SpiceTools. Why only local? Because none of the most typical places currently support Nostalgia. Regardless, please keep in mind you can add whatever additional parameters you desire.
+
+!!! warning "If you're not using SpiceTools:"
+ The overall structure of your .bat file will differ from the guide, namely the initialization of SpiceTools won't be present and potential parameters may differ. As stated above, make sure to check the documentation of your tools to ensure you're using the correct parameters for your needs.
+
+## Configuring for a Local Network
+
+!!! tip ""
+ For our local network configuration example, on a single line in the `.bat` file we're going to type `spice64.exe -ea -w` and save the file.
+
+ What do these different parameters do?
+
+ - `-ea` enables an integrated e-amusement server within SpiceTools.
+ - `-w` will boot the game in windowed mode which will ease our initial setup and testing later, make sure to remove `-w` to run the game fullscreen once you're done setting up!
+
+## Configuring for an Online Network
+
+!!! tip ""
+ For our online network example we're simply doing the above but with different parameters! On our single line, we're going to type `spice64.exe -p XXXXXXXXXXXXXXXXXXXX -url http://yoururlhere.com/ -w` and save the file.
+
+ What do these different parameters do?
+
+ - `-p` takes your PCBID on your network of choice, simply replace `XXXXXXXXXXXXXXXXXXXX` with your PCBID.
+ - `-url` allows you to specify a custom service URL to connect with, simply replace `http://yoururlhere.com/` with your chosen network's URL.
+ - `-w` will boot the game in windowed mode which will ease our initial setup and testing later, make sure to remove `-w` to run the game fullscreen once you're done setting up!
+
+## Final Steps and Setting up the Game
+
+!!! tip ""
+ The last steps you'll have to do with your chosen tools is simply setting up your desired keybinds! Make sure you setup the `Test` keybind as it will be critical for setting up the game. Once you've done that, launch your game for the first time by double clicking the `.bat` you setup and the game should load.
+
+ If it's your first time running the game, you should be automatically forced into the service menu with lots of scary flashing notifications as pictured below, let's work through them.
+
+
+
+!!! tip ""
+ Interestingly, only the red flashing ones really take any effort to deal with. You can start by entering and exiting the following menus: `SOUND OPTIONS`, `GAME OPTIONS`, `COIN OPTIONS`, `ECOMODE OPTIONS`, and `NETWORK OPTIONS`.
+
+ Once you've done that, enter `CLOCK` and set the clock by hitting `SAVE AND EXIT` as pictured below.
+
+
+
+!!! tip ""
+ The final menu we must deal with is `VIRTUAL COIN`, enter the menu and select `OPERATION SETTINGS` as seen below.
+
+
+
+!!! tip ""
+ Once inside this menu, we'll need to deal with all 4 blinking options, let's start by entering the `TAX RATE SETTING` menu, shown below.
+
+
+
+!!! tip ""
+ Set the tax rate by simply selecting `SAVE AND EXIT` while will take us back into the `OPERATING SETTINGS`. Pictured below is the `TAX RATE SETTING` menu.
+
+
+
+!!! tip ""
+ Once back inside the `TAX RATE SETTING` menu, we must deal with the three blinking `PATTERN` options. Doing so is effortless, simply enter all three menus one by one and hit `SAVE AND EXIT` just as we did for the `TAX RATE SETTING` in the previous step. Pictured below is the inside of `PATTERN 1`.
+
+
+
+!!! tip ""
+ After saving and exiting all three `PATTERN` options, you're all done! From the service menu select `GAME MODE` and the game should load ready to be played! Have fun!
+
+!!! warning "Have any other errors?"
+ Check out the [Troubleshooting](troubleshooting.md) section and [Error Code](/errorcodes/konami.md) section to resolve any issues not seen in this guide to greater depth.
\ No newline at end of file
diff --git a/docs/games/konami/nostalgia/op2/troubleshooting.md b/docs/games/konami/nostalgia/op2/troubleshooting.md
new file mode 100644
index 0000000..ca7cba1
--- /dev/null
+++ b/docs/games/konami/nostalgia/op2/troubleshooting.md
@@ -0,0 +1,46 @@
+
+# Troubleshooting
+
+--8<-- "docs/snippets/common/old_guide.md"
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+## Hardware Specs
+
+!!! tip ""
+ Konami PC Type 6 (ADE-704A)
+
+ Based on an AMD Embedded R Series SoC.
+
+ CPU: Intel Celeron B810
+
+ GPU: AMD Radeon E4690
+
+ OS: Windows 7 Embedded
+
+### My Game Is Running Slow/Lagging
+
+!!! tip ""
+ Make sure you at least meet the above hardware requirements, try to eliminate any unnecessary background processes during play as well.
+
+### My Game Is Running Crazy Fast!
+
+!!! tip ""
+ The most common reason for this is the game is running over its required 60 Hz, the game is hardcoded to run at 60 Hz and this cannot be changed. To solve this, set your monitor's refresh rate to 60 Hz. You can always check on the game's monitor check if the game is fluctuating around 59.94hz, the NTSC standard. If it's not around there and your monitor is indeed set to 60 Hz, consider trying a different panel or forcing vsync on in your GPU's graphics settings.
+
+### Occasional Game Stutters During Play
+
+!!! tip ""
+ Sometimes you might have occasional stutters during play, while solutions can vary wildly from general performance issues to bad hard drives, try adding SpiceTools `-realtime` parameter to your .bat file.
+
+### Which Offset Is Which?
+
+!!! tip ""
+ If you're getting too many fasts, increase your offset (+). If you're getting too many slows, decrease your offset (-).
+
+### No Matter What I Do, the Game Crashes and I Have Multiple Monitors!
+
+!!! tip ""
+ This problem is somewhat irregular, but sometimes Nostalgia has issues booting with multiple monitors present, particularly when trying to boot the game windowed. Make sure you're running the latest SpiceTools which has attempted to resolve all instances of this issue.
+
+
diff --git a/docs/games/konami/popn/common/setup.md b/docs/games/konami/popn/common/setup.md
new file mode 100644
index 0000000..302b8d0
--- /dev/null
+++ b/docs/games/konami/popn/common/setup.md
@@ -0,0 +1,124 @@
+# Game Setup
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+## Preparing data
+
+--8<-- "docs/snippets/common/data_readonly.md"
+
+ The **complete game data** should be approximately **20 GB or larger**.
+ If your data is significantly smaller, you likely have an update archive instead of the full game data.
+
+ Here's what the expected data structure should look like:
+
+ ```
+ 📂data
+ 📂dev
+ 📂modules
+ 📂prop
+ ```
+
+--8<-- "docs/snippets/konami/common/data_bad.md"
+
+!!! info "If your data is already up-to-date, you can skip ahead to the [Installing spice2x](#installing-spice2x) section"
+
+## Updating data
+
+!!! danger "Make sure you're using the right update for your current game version"
+
+ pop'n music updates have `M39` and one or two datecodes in their archive names.
+
+ **Single datecode:** Contains one update (e.g., `M39_NewDateCode.7z`)
+ **Two datecodes:** Updates from the older to newer version (e.g., `M39_OldDateCode-NewDateCode.rar`)
+
+ A date code should look something like this: `YYYYMMDDXX`
+
+ In the two-datecode example:
+
+ - `OldDateCode` is the older date, the game version required to apply this update
+ - `NewDateCode` is the newer date, and is the version you'll arrive at after applying the update
+
+--8<-- "docs/snippets/konami/common/data_update.md"
+
+## Installing spice2x
+
+--8<-- "docs/snippets/konami/common/spice2x32_install.md"
+
+ ``` hl_lines="5-6"
+ 📂data
+ 📂dev
+ 📂modules
+ 📂prop
+ 🌶️spice.exe
+ 🌶️spicecfg.exe
+ ```
+
+## Configuring spice2x
+
+--8<-- "docs/snippets/konami/common/spicecfg_preamble.md"
+
+=== "Buttons"
+
+--8<-- "docs/snippets/konami/common/spicecfg_buttons.md"
+
+ !!! tip "Binding your buttons"
+
+ Click on `Bind` or `Naive` then press the key you want associated with the action.
+
+ With your controller and/or keyboard plugged in, configure your keys for:
+
+ - **Maintenance**: `Service, Test`
+ - **Game buttons**: `1 to 9`
+ - **P1 Keypad**: `1 to 9, Keypad Insert Card`
+
+--8<-- "docs/snippets/konami/common/spicecfg_buttons_additionalinfo.md"
+
+=== "Analogs"
+
+--8<-- "docs/snippets/konami/common/spicecfg_nochange.md"
+
+=== "Overlay"
+
+--8<-- "docs/snippets/konami/common/spicecfg_overlay.md"
+
+=== "Lights"
+
+--8<-- "docs/snippets/konami/common/spicecfg_lights.md"
+
+=== "Cards"
+
+--8<-- "docs/snippets/konami/common/spicecfg_cards.md"
+
+=== "Patches"
+
+ !!! tip "We recommend using [popnhax](https://github.com/CrazyRedMachine/popnhax) instead of spice2x patching"
+
+=== "API"
+
+--8<-- "docs/snippets/konami/common/spicecfg_nochange.md"
+
+=== "Advanced"
+
+--8<-- "docs/snippets/konami/common/spicecfg_nochange.md"
+
+=== "Options"
+
+--8<-- "docs/snippets/konami/common/spicecfg_options_nvprofile.md"
+
+=== "Development"
+
+--8<-- "docs/snippets/konami/common/spicecfg_nochange.md"
+
+## Connecting to a network
+
+--8<-- "docs/snippets/konami/common/setup_network.md"
+
+## Before playing
+
+--8<-- "docs/snippets/common/before_playing.md"
+
+!!! success "You're all done! The game should load up properly now"
+
+## Help
+
+--8<-- "docs/snippets/common/help.md"
\ No newline at end of file
diff --git a/docs/games/konami/popn/common/troubleshooting.md b/docs/games/konami/popn/common/troubleshooting.md
new file mode 100644
index 0000000..625b723
--- /dev/null
+++ b/docs/games/konami/popn/common/troubleshooting.md
@@ -0,0 +1,27 @@
+# Troubleshooting
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+### My game crashes on launch
+
+!!! tip ""
+
+ Some monitors and display adapters may not support the odd resolution that the game runs at, which is 1360x768 as opposed to the occasionally seen 1366x768. To resolve this, set a custom resolution in your graphics card's settings, or enable GPU resolution scaling.
+
+### My game is too slow/fast
+
+!!! tip ""
+
+ Potential causes:
+
+ 1. The game could be running over/under its required refresh rate (60)
+ To solve this, make sure v-sync isn't disabled in your graphics card's settings.
+ For NVIDIA users, enable `NVIDIA profile optimization (-nvprofile)` in the `Options` tab.
+ You can also set `Force Refresh Rate` to 60.
+ 2. It could be that your computer's performance isn't good enough to keep a steady framerate.
+
+### My game doesn't have audio
+
+!!! tip ""
+
+ Enable the `HDMI Audio Fix` patch.
\ No newline at end of file
diff --git a/docs/games/konami/popn/kaimei_riddles/setup.md b/docs/games/konami/popn/kaimei_riddles/setup.md
new file mode 100644
index 0000000..4c993b8
--- /dev/null
+++ b/docs/games/konami/popn/kaimei_riddles/setup.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/konami/popn/common/setup.md"
\ No newline at end of file
diff --git a/docs/games/konami/popn/kaimei_riddles/troubleshooting.md b/docs/games/konami/popn/kaimei_riddles/troubleshooting.md
new file mode 100644
index 0000000..b77117a
--- /dev/null
+++ b/docs/games/konami/popn/kaimei_riddles/troubleshooting.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/konami/popn/common/troubleshooting.md"
\ No newline at end of file
diff --git a/docs/games/konami/popn/peace/setup.md b/docs/games/konami/popn/peace/setup.md
new file mode 100644
index 0000000..77f74c6
--- /dev/null
+++ b/docs/games/konami/popn/peace/setup.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/konami/popn/common/setup.md"
\ No newline at end of file
diff --git a/docs/games/konami/popn/peace/troubleshooting.md b/docs/games/konami/popn/peace/troubleshooting.md
new file mode 100644
index 0000000..cd94970
--- /dev/null
+++ b/docs/games/konami/popn/peace/troubleshooting.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/konami/popn/common/troubleshooting.md"
\ No newline at end of file
diff --git a/docs/games/konami/popn/unilab/setup.md b/docs/games/konami/popn/unilab/setup.md
new file mode 100644
index 0000000..a0c1e30
--- /dev/null
+++ b/docs/games/konami/popn/unilab/setup.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/konami/popn/common/setup.md"
\ No newline at end of file
diff --git a/docs/games/konami/popn/unilab/troubleshooting.md b/docs/games/konami/popn/unilab/troubleshooting.md
new file mode 100644
index 0000000..0c9e0fe
--- /dev/null
+++ b/docs/games/konami/popn/unilab/troubleshooting.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/konami/popn/common/troubleshooting.md"
\ No newline at end of file
diff --git a/docs/games/konami/popn/usaneko/setup.md b/docs/games/konami/popn/usaneko/setup.md
new file mode 100644
index 0000000..d98ffaf
--- /dev/null
+++ b/docs/games/konami/popn/usaneko/setup.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/konami/popn/common/setup.md"
\ No newline at end of file
diff --git a/docs/games/konami/popn/usaneko/troubleshooting.md b/docs/games/konami/popn/usaneko/troubleshooting.md
new file mode 100644
index 0000000..e94b60e
--- /dev/null
+++ b/docs/games/konami/popn/usaneko/troubleshooting.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/konami/popn/common/troubleshooting.md"
\ No newline at end of file
diff --git a/docs/games/konami/reflecbeat/reflesia/setup.md b/docs/games/konami/reflecbeat/reflesia/setup.md
new file mode 100644
index 0000000..0686fda
--- /dev/null
+++ b/docs/games/konami/reflecbeat/reflesia/setup.md
@@ -0,0 +1,70 @@
+
+# Game Setup
+
+--8<-- "docs/snippets/common/old_guide.md"
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+## Getting Started
+
+!!! tip ""
+
+ This game still uses DirectSound so we can skip audio related setup needed for other games. After downloading your data, the first thing to do is put your desired 32-bit tools inside the game's `contents` folder, and to create a `.bat` file. Pictured below is what your folder should look like, feel free to name your `.bat` file anything you desire, for the sake of convenience we've named ours `gamestart.bat`.
+
+
+
+
+## Configuring Your Tools
+
+!!! tip ""
+
+ Now that you have your files ready, open up your `.bat` file in your desired text editor (we're using [Notepad++](https://notepad-plus-plus.org/)) and edit it with your desired parameters, for the purpose of this guide we will demonstrate both a local network configuration and an online example below with SpiceTools, skip to whichever you're in need of accordingly and please keep in mind you can add whatever additional parameters you desire.
+
+!!! warning "If you're not using SpiceTools:"
+
+ The overall structure of your .bat file will differ from the guide, namely the initialization of SpiceTools won't be present and potential parameters may differ. As stated above, make sure to check the documentation of your tools to ensure you're using the correct parameters for your needs.
+
+## Configuring for a Local Network
+
+!!! tip ""
+
+ For our local network configuration example, on a single line in the `.bat` file we're going to type `spice.exe -ea -w` and save the file.
+
+ What do these different parameters do?
+
+ - `-ea` enables an integrated e-amusement server within SpiceTools.
+ - `-w` will boot the game in windowed mode which will ease our initial setup and testing later, make sure to remove `-w` to run the game fullscreen once you're done setting up!
+
+## Configuring for an Online Network
+
+!!! tip ""
+
+ For our online network example we're simply doing the above but with different parameters! On our single line, we're going to type `spice.exe -p XXXXXXXXXXXXXXXXXXXX -url http://yoururlhere.com/ -w` and save the file.
+
+ What do these different parameters do?
+
+ - `-p` takes your PCBID on your network of choice, simply replace `XXXXXXXXXXXXXXXXXXXX` with your PCBID.
+ - `-url` allows you to specify a custom service URL to connect with, simply replace `http://yoururlhere.com/` with your chosen network's URL.
+ - `-w` will boot the game in windowed mode which will ease our initial setup and testing later, make sure to remove `-w` to run the game fullscreen once you're done setting up!
+
+!!! tip ""
+
+ One final note, since you're playing on a network, you will have one additional step of setting up your card file within your chosen tools, make sure to check your server's information on how to setup a card file.
+
+## Final Steps and Setting up the Game
+
+!!! tip ""
+
+ It's important to note before booting the game that Reflec Beat uses portrait mode and attempting to boot the game fullscreen in most landscape environments will result in a crash. To alleviate this, we must set our *main* monitor to portrait mode and be ready to rotate it! To do so, right click on your desktop and go into `Display Settings`, then simply set the orientation to `Portrait`.
+
+ In the event that you do not have the means to run the game in portrait mode and cannot rotate your monitor, it is recommended you boot the game in windowed mode. In SpiceTools, simply add the windowed mode parameter, this parameter is `-w` and can be placed right after any other desired parameters chosen in our `gamestart.bat`
+
+ As for the touch stuff, by default SpiceTools should detect your mouse just fine, you can use the `-s` parameter to have your cursor show at all times above the game window. For touchscreen monitors, it's a bit tricky to write something encompassing them all. Many should be detected automatically, however some may require adding the `-wintouch` parameter for support.
+
+ With that, you're all done! The final step you'll have to do with your chosen tools is simply setting up your desired keybinds! Once you've done that, Boot the game with your `gamestart.bat` and the game should load and be ready to be enjoyed! Have fun!
+
+## Troubleshooting
+
+!!! warning "Have any other errors?"
+
+ Check out the [Troubleshooting](troubleshooting.md) and [Error Code](/errorcodes/konami.md) sections to resolve any issues not seen in this guide.
diff --git a/docs/games/konami/reflecbeat/reflesia/troubleshooting.md b/docs/games/konami/reflecbeat/reflesia/troubleshooting.md
new file mode 100644
index 0000000..d7439d2
--- /dev/null
+++ b/docs/games/konami/reflecbeat/reflesia/troubleshooting.md
@@ -0,0 +1,47 @@
+
+# Troubleshooting
+
+--8<-- "docs/snippets/common/old_guide.md"
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+## Hardware Specs
+
+!!! tip ""
+ Konami PC (ADE-704A)
+
+ CPU: Intel Celeron B810 1.6GHz
+
+ GPU: E4690 Radeon MXM
+
+ OS: Windows XP Embedded
+
+### My Game Doesn't Boot After Following the Guide!
+
+!!! tip ""
+ The most common problem present here is if you do not have an E:/ drive. To resolve this issue, you must apply the `E:/drive fix` patch.
+
+### My Game Is Running Slow/Lagging
+
+!!! tip ""
+ Make sure you at least meet the above hardware requirements, try to eliminate any unnecessary background processes during play as well.
+
+### My Game Is Running Crazy Fast/After Finishing a Song Loading Is Stuck
+
+!!! tip ""
+ The most common reason for this is the game is running over its required 60 Hz, the game is hardcoded to run at 60 Hz and this cannot be changed. To solve this, set your monitor's refresh rate to 60 Hz. You can always check on the game's monitor check if the game is fluctuating around 59.94hz, the NTSC standard. If it's not around there and your monitor is indeed set to 60 Hz, consider trying a different panel or forcing vsync on in your GPU's graphics settings.
+
+### Which Offset Is Which?
+
+!!! tip ""
+ If you're getting too many fasts, increase your offset (+). If you're getting too many slows, decrease your offset (-).
+
+### Failed to Create Texture Error in SpiceTools
+
+!!! tip ""
+ If your error is along the lines of a failure to create a texture W:afputils: CTexture::create_texture テクスチャの作成に失敗しました。 then boot the game without touching anything, even your mouse, maybe give it a few tries, it's admittedly a strange issue with no exact science behind it discovered.
+
+### I Get a White Screen That Silently Closes After a Few Seconds
+
+!!! tip ""
+ Reflesia runs at 768x1360 opposed to more common resolutions. If your monitor doesn't have support for this, try making a custom resolution in your graphic's cards options. Also, make sure your monitor is in portrait mode as opposed to landscape.
\ No newline at end of file
diff --git a/docs/games/konami/sdvx/4_heavenlyhaven/setup.md b/docs/games/konami/sdvx/4_heavenlyhaven/setup.md
new file mode 100644
index 0000000..28bff93
--- /dev/null
+++ b/docs/games/konami/sdvx/4_heavenlyhaven/setup.md
@@ -0,0 +1,74 @@
+
+# Game Setup
+
+--8<-- "docs/snippets/common/old_guide.md"
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+### Getting Started
+
+!!! tip ""
+
+ This game still uses DirectSound so we can skip audio related setup needed for other games. After downloading your data, the first thing to do is make sure your files aren't set to READ ONLY, make sure to uncheck it from the main folder in the Windows Properties tab if so. Then, put your desired 32-bit tools inside the game's `contents` folder, and to create a `.bat` file. Pictured below is what your folder should look like, feel free to name your `.bat` file anything you desire, for the sake of convenience we've named ours `gamestart.bat`.
+
+
+
+
+### Configuring Your Tools
+
+!!! tip ""
+
+ Now that you have your files ready, open up your `.bat` file in your desired text editor (we're using [Notepad++](https://notepad-plus-plus.org/)) and edit it with your desired parameters, for the purpose of this guide we will demonstrate both a local network configuration and an online example below with SpiceTools, skip to whichever you're in need of accordingly and please keep in mind you can add whatever additional parameters you desire.
+
+!!! warning "If you're not using SpiceTools:"
+
+ The overall structure of your .bat file will differ from the guide, namely the initialization of SpiceTools won't be present and potential parameters may differ. As stated above, make sure to check the documentation of your tools to ensure you're using the correct parameters for your needs.
+
+### Configuring for a Local Network
+
+!!! tip ""
+
+ For our local network configuration example, on a single line in the `.bat` file we're going to type `spice.exe -ea -w` and save the file.
+
+ What do these different parameters do?
+
+ - `-ea` enables an integrated e-amusement server within SpiceTools.
+ - `-w` will boot the game in windowed mode which will ease our initial setup and testing later, make sure to remove `-w` to run the game fullscreen once you're done setting up!
+
+ Pictured below, the contents of our `gamestart.bat` file in Notepad++.
+
+
+
+### Configuring for an Online Network
+
+!!! tip ""
+
+ For our online network example we're simply doing the above but with different parameters! On our single line, we're going to type `spice.exe -p XXXXXXXXXXXXXXXXXXXX -url http://yoururlhere.com/ -w` and save the file.
+
+ What do these different parameters do?
+
+ - `-p` takes your PCBID on your network of choice, simply replace `XXXXXXXXXXXXXXXXXXXX` with your PCBID.
+ - `-url` allows you to specify a custom service URL to connect with, simply replace `http://yoururlhere.com/` with your chosen network's URL.
+ - `-w` will boot the game in windowed mode which will ease our initial setup and testing later, make sure to remove `-w` to run the game fullscreen once you're done setting up!
+
+ Pictured below, the contents of our `gamestart.bat` file in Notepad++.
+
+
+
+!!! tip ""
+
+ One final note, since you're playing on a network, you will have one additional step of setting up your card file within your chosen tools, make sure to check your server's information on how to setup a card file.
+
+### Final Steps and Setting up the Game
+
+!!! tip ""
+
+ It's important to note before booting the game that Sound Voltex uses portrait mode and attempting to boot the game fullscreen in most landscape environments will result in a crash. To alleviate this, we must set our *main* monitor to portrait mode and be ready to rotate it! To do so, right click on your desktop and go into `Display Settings`, then simply set the orientation to `Portrait`.
+
+ In the event that you do not have the means to run the game in portrait mode and cannot rotate your monitor, it is recommended you boot the game in windowed mode. In SpiceTools, simply add the windowed mode parameter, this parameter is `-w` and can be placed right after any other desired parameters chosen in our `gamestart.bat`
+
+ With that, you're all done! The final step you'll have to do with your chosen tools is simply setting up your desired keybinds! Once you've done that, Boot the game with your `gamestart.bat` and the game should load and be ready to be enjoyed! Have fun!
+
+!!! warning "Have any other errors?"
+
+ Check out the [Troubleshooting](troubleshooting.md) section and [Error Code](/errorcodes/konami.md) section to resolve any issues not seen in this guide to greater depth.
diff --git a/docs/games/konami/sdvx/4_heavenlyhaven/troubleshooting.md b/docs/games/konami/sdvx/4_heavenlyhaven/troubleshooting.md
new file mode 100644
index 0000000..b33a211
--- /dev/null
+++ b/docs/games/konami/sdvx/4_heavenlyhaven/troubleshooting.md
@@ -0,0 +1,44 @@
+
+# Troubleshooting
+
+--8<-- "docs/snippets/common/old_guide.md"
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+## Hardware Specs
+
+!!! tip ""
+ Konami PC Type 4
+
+ CPU: Celeron M 440 1.86GHz
+
+ GPU: ATI Radeon HD 2400
+
+ RAM: 2 GB
+
+ OS: Windows XP Embedded
+
+### My Game Is Running Slow/Lagging
+
+!!! tip ""
+ Make sure you at least meet the above hardware requirements, try to eliminate any unnecessary background processes during play as well.
+
+### My Game Is Running Crazy Fast/After Finishing a Song Loading Is Stuck
+
+!!! tip ""
+ The most common reason for this is the game is running over its required 60 Hz, the game is hardcoded to run at 60 Hz and this cannot be changed. To solve this, set your monitor's refresh rate to 60 Hz. You can always check on the game's monitor check if the game is fluctuating around 59.94hz, the NTSC standard. If it's not around there and your monitor is indeed set to 60 Hz, consider trying a different panel or forcing vsync on in your GPU's graphics settings.
+
+### Which Offset Is Which?
+
+!!! tip ""
+ If you're getting too many fasts, increase your offset (+). If you're getting too many slows, decrease your offset (-). Please note that Sound Voltex IV's offset is *purely visual* and the game does not have an audio-based offset adjustment. Sound Voltex V however, does.
+
+### Running the Game Windowed and Borderless
+
+!!! tip ""
+ Some players utilizing windowed mode use 3rd party software called [Borderless Gaming](https://github.com/Codeusa/Borderless-Gaming/releases) in order to achieve this, follow the program's instructions accordingly.
+
+### Where Are All the Navigators?
+
+!!! tip ""
+ Many navigators are locked behind network requirements and they will not show unless connected to a network that has written support for the events that they're typically locked behind.
\ No newline at end of file
diff --git a/docs/games/konami/sdvx/5_vividwave/setup.md b/docs/games/konami/sdvx/5_vividwave/setup.md
new file mode 100644
index 0000000..c7ee71f
--- /dev/null
+++ b/docs/games/konami/sdvx/5_vividwave/setup.md
@@ -0,0 +1,74 @@
+
+# Game Setup
+
+--8<-- "docs/snippets/common/old_guide.md"
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+## Getting Started
+
+!!! tip ""
+
+ Before we even touch the game, let's fiddle with our audio settings to minimize any potential crashing on startup. In Windows, go to `Playback Devices` and then right click on your default device and go to `Properties`. From there, hit the `Advanced` tab and set your `Default Format` to `44100 Hz` and check both of the options inside `Exclusive Mode` as pictured.
+
+
+
+!!! tip ""
+
+ After downloading your data, the first thing to do is make sure your files aren't set to READ ONLY, make sure to uncheck it from the main folder in the Windows Properties tab if so. Then, put your desired 64-bit tools inside the game's `contents` folder, and to create a `.bat` file. Pictured below is what your folder should look like, feel free to name your `.bat` file anything you desire, for the sake of convenience we've named ours `gamestart.bat`.
+
+
+
+!!! tip ""
+ Why does this look different than the usual? This installation includes a `modules` folder that Spice automatically detects, keeping things clean and simple. If your version of the game doesn't have this, it probably has the `contents` folder populated with many different dll files such as the main `soundvoltex.dll`. You should still place your tools here if so!
+
+## Configuring Your Tools
+
+!!! tip ""
+
+ Now that you have your files ready, open up your `.bat` file in your desired text editor (we're using [Notepad++](https://notepad-plus-plus.org/)) and edit it with your desired parameters, for the purpose of this guide we will demonstrate both a local network configuration and an online example below with SpiceTools, skip to whichever you're in need of accordingly and please keep in mind you can add whatever additional parameters you desire.
+
+!!! warning "If you're not using SpiceTools:"
+
+ The overall structure of your .bat file will differ from the guide, namely the initialization of SpiceTools won't be present and potential parameters may differ. As stated above, make sure to check the documentation of your tools to ensure you're using the correct parameters for your needs.
+
+## Configuring for a Local Network
+
+!!! tip ""
+
+ For our local network configuration example, on a single line in the `.bat` file we're going to type `spice64.exe -ea -w` and save the file.
+
+ What do these different parameters do?
+
+ - `-ea` enables an integrated e-amusement server within SpiceTools.
+ - `-w` will boot the game in windowed mode which will ease our initial setup and testing later, make sure to remove `-w` to run the game fullscreen once you're done setting up!
+
+## Configuring for an Online Network
+
+!!! tip ""
+
+ For our online network example we're simply doing the above but with different parameters! On our single line, we're going to type `spice64.exe -p XXXXXXXXXXXXXXXXXXXX -url http://yoururlhere.com/ -w` and save the file.
+
+ What do these different parameters do?
+
+ - `-p` takes your PCBID on your network of choice, simply replace `XXXXXXXXXXXXXXXXXXXX` with your PCBID.
+ - `-url` allows you to specify a custom service URL to connect with, simply replace `http://yoururlhere.com/` with your chosen network's URL.
+ - `-w` will boot the game in windowed mode which will ease our initial setup and testing later, make sure to remove `-w` to run the game fullscreen once you're done setting up!
+
+!!! tip ""
+
+ One final note, since you're playing on a network, you will have one additional step of setting up your card file within your chosen tools, make sure to check your server's information on how to setup a card file.
+
+## Final Steps and Setting up the Game
+
+!!! tip ""
+
+ It's important to note before booting the game that Sound Voltex uses portrait mode and attempting to boot the game fullscreen in most landscape environments will result in a crash. To alleviate this, we must set our *main* monitor to portrait mode and be ready to rotate it! To do so, right click on your desktop and go into `Display Settings`, then simply set the orientation to `Portrait`.
+
+ In the event that you do not have the means to run the game in portrait mode and cannot rotate your monitor, it is recommended you boot the game in windowed mode. In SpiceTools, simply add the windowed mode parameter, this parameter is `-w` and can be placed right after any other desired parameters chosen in our `gamestart.bat`
+
+ With that, you're all done! The final step you'll have to do with your chosen tools is simply setting up your desired keybinds! Once you've done that, Boot the game with your `gamestart.bat` and the game should load and be ready to be enjoyed! Have fun!
+
+!!! warning "Have any other errors?"
+
+ Check out the [Troubleshooting](troubleshooting.md) section and [Error Code](/errorcodes/konami.md) section to resolve any issues not seen in this guide to greater depth.
\ No newline at end of file
diff --git a/docs/games/konami/sdvx/5_vividwave/troubleshooting.md b/docs/games/konami/sdvx/5_vividwave/troubleshooting.md
new file mode 100644
index 0000000..dc7621f
--- /dev/null
+++ b/docs/games/konami/sdvx/5_vividwave/troubleshooting.md
@@ -0,0 +1,72 @@
+
+# Troubleshooting
+
+--8<-- "docs/snippets/common/old_guide.md"
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+## Hardware Specs
+
+!!! tip ""
+
+ Konami PC Type 4
+
+ CPU: Intel i3-4300 3.5GHz
+
+ GPU: Nvidia GeForce GTX 1050 2GB
+
+ RAM: 8GB DDR3L PC3-12800 (4GB*2)
+
+ OS: Windows 7 Embedded
+
+### My Game Is Running Slow/Lagging
+
+!!! tip ""
+
+ Make sure you at least meet the above hardware requirements, try to eliminate any unnecessary background processes during play as well.
+
+ At the time of writing, some individuals with more than capable PCs have had framerate issues, most notably with Ryzen CPUs. There's really no fix as the issues seem largely random, but it's worth noting regardless to consider trying different computers if you have them available.
+
+### My Game Is Running Crazy Fast/After Finishing a Song Loading Is Stuck
+
+!!! tip ""
+
+ The most common reason for this is the game is running over its required 60 Hz, the game is hardcoded to run at 60 Hz and this cannot be changed. To solve this, set your monitor's refresh rate to 60 Hz. You can always check on the game's monitor check if the game is fluctuating around 59.94hz, the NTSC standard. If it's not around there and your monitor is indeed set to 60 Hz, consider trying a different panel or forcing vsync on in your GPU's graphics settings.
+
+### Which Offset Is Which?
+
+!!! tip ""
+
+ If you're getting too many fasts, increase your offset (+). If you're getting too many slows, decrease your offset (-). Sound Voltex V has two types of offset adjustments, visual and audio based, so be sure to fiddle with both to find desirable settings.
+
+### Running the Game Windowed and Borderless
+
+!!! tip ""
+
+ Some players utilizing windowed mode use 3rd party software called [Borderless Gaming](https://github.com/Codeusa/Borderless-Gaming/releases) in order to achieve this, follow the program's instructions accordingly.
+
+### Where Are All the Navigators?
+
+!!! tip ""
+
+ Many navigators are locked behind network requirements and they will not show unless connected to a network that has written support for the events that they're typically locked behind.
+
+### A Note About SSE 4.2
+
+!!! tip ""
+
+ In the rare case you are running this game on *very* old hardware, SDVX V requires a processor supporting the [SSE 4.2 instruction set](https://en.wikipedia.org/wiki/SSE4#SSE4.2). But, in the event your processor does not have this, there is a patch available to bypass this.
+
+### When I Run This Game All Other Background Audio Is Gone! What's Going On?
+
+!!! tip ""
+
+ 64-bit versions of SDVX are now utilizing a feature in Windows called [WASAPI exclusive mode](https://docs.microsoft.com/en-us/windows/win32/coreaudio/exclusive-mode-streams) to obtain less audio latency than the former 32-bit versions of the games which used [DirectSound](https://en.wikipedia.org/wiki/DirectSound). You can use the `Shared Mode WASAPI` patch to deal with some hardware issues, it can also be used to hear background audio outside the game so that the game does not take total control. Many have reported that this edit only works when the audio is set to either 16-bit 44100Hz or 24-bit 44100Hz.
+
+### I'm Not Getting Any Audio/My Audio Is Completely Wrecked and I'm Using an External Dac!
+
+!!! tip ""
+
+ Several external DACs have issues with [WASAPI exclusive mode](https://docs.microsoft.com/en-us/windows/win32/coreaudio/exclusive-mode-streams) and are unable to be used entirely, it's likely you'll be forced to use your motherboard's sound chip, or find a compatible DAC.
+
+ Alongside this, many setups have found some difficulty with audio due to various equipment being used. Consider applying the `Shared Mode WASAPI` patch.
diff --git a/docs/games/konami/sdvx/6_exceedgear/extras.md b/docs/games/konami/sdvx/6_exceedgear/extras.md
new file mode 100644
index 0000000..9dd400f
--- /dev/null
+++ b/docs/games/konami/sdvx/6_exceedgear/extras.md
@@ -0,0 +1,110 @@
+
+# Extra Information
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+## Nemsys and Valkyrie modes
+
+!!! warning "Valkyrie mode requires a 120 Hz capable monitor, or to have patched your `.dll` with `Valkyrie Mode 60 Hz`"
+
+!!! tip ""
+
+ To make use of the Valkyrie Mode (Subscreen, 120FPS, S-CRITICAL..) you need to go to the `contents\prop` folder and edit the `ea3-config.xml` file.
+
+ We're interested in these lines:
+
+ ```xml
+
+# Game Setup
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+## Preparing data
+
+--8<-- "docs/snippets/common/data_readonly.md"
+
+ The **complete game data** should be approximately **20 GB or larger**.
+ If your data is significantly smaller, you likely have an update archive instead of the full game data.
+
+ Here's what the expected data structure should look like:
+
+ ```
+ 📂data
+ 📂dev
+ 📂ext
+ 📂modules
+ 📂prop
+ ```
+
+--8<-- "docs/snippets/konami/common/data_bad.md"
+
+!!! info "If your data is already up-to-date, you can skip ahead to the [Installing spice2x](#installing-spice2x) section"
+
+## Updating data
+
+!!! info "For a comprehensive list of all game updates in chronological order, visit [BemaniWiki](https://bemaniwiki.com/?SOUND+VOLTEX+EXCEED+GEAR#sdvxegvernew)"
+
+!!! danger "Make sure you're using the right update for your current game version"
+
+ SDVX updates have `KFC` and one or two datecodes in their archive names.
+
+ **Single datecode:** Contains one update (e.g., `KFC_NewDateCode.7z`)
+ **Two datecodes:** Updates from the older to newer version (e.g., `KFC-OldDateCode-NewDateCode.rar`)
+
+ In the two-datecode example:
+
+ - `OldDateCode` is the older date, the game version required to apply this update
+ - `NewDateCode` is the newer date, and is the version you'll arrive at after applying the update
+
+--8<-- "docs/snippets/konami/common/data_update.md"
+
+## Installing spice2x
+
+--8<-- "docs/snippets/konami/common/spice2x64_install.md"
+
+ ``` hl_lines="6-7"
+ 📂data
+ 📂dev
+ 📂ext
+ 📂modules
+ 📂prop
+ 🌶️spice64.exe
+ 🌶️spicecfg.exe
+ ```
+
+--8<-- "docs/snippets/konami/common/spice2x64_stubs.md"
+
+## Configuring spice2x
+
+--8<-- "docs/snippets/konami/common/spicecfg_preamble.md"
+
+=== "Buttons"
+
+--8<-- "docs/snippets/konami/common/spicecfg_buttons.md"
+
+--8<-- "docs/snippets/konami/sdvx/spicecfg_buttons.md"
+
+--8<-- "docs/snippets/konami/common/spicecfg_buttons_additionalinfo.md"
+
+=== "Analogs"
+
+--8<-- "docs/snippets/konami/sdvx/spicecfg_analogs.md"
+
+=== "Overlay"
+
+--8<-- "docs/snippets/konami/common/spicecfg_overlay.md"
+
+=== "Lights"
+
+--8<-- "docs/snippets/konami/common/spicecfg_lights.md"
+
+=== "Cards"
+
+--8<-- "docs/snippets/konami/common/spicecfg_cards.md"
+
+=== "Patches"
+
+--8<-- "docs/snippets/konami/common/spicecfg_patches.md"
+
+=== "API"
+
+--8<-- "docs/snippets/konami/common/spicecfg_nochange.md"
+
+=== "Options"
+
+--8<-- "docs/snippets/konami/common/spicecfg_options.md"
+
+--8<-- "docs/snippets/konami/common/spicecfg_options_nvprofile.md"
+
+=== "Advanced"
+
+--8<-- "docs/snippets/konami/common/spicecfg_nochange.md"
+
+=== "Development"
+
+--8<-- "docs/snippets/konami/common/spicecfg_nochange.md"
+
+## Configuring audio
+
+--8<-- "docs/snippets/konami/common/setup_audio.md"
+
+## Connecting to a network
+
+--8<-- "docs/snippets/konami/common/setup_network.md"
+
+## Configuring your game
+
+!!! info "Read through the [Extra Information](extras.md) page"
+
+## Monitor Orientation
+
+--8<-- "docs/snippets/konami/common/display_portraitfirst.md"
+
+## Installing VCRedist & DirectX
+
+--8<-- "docs/snippets/common/setup_vcredist_directx.md"
+
+## Before playing
+
+--8<-- "docs/snippets/common/before_playing.md"
+
+## First launch
+
+!!! tip ""
+
+ If you've followed all instructions correctly, you're finally ready to launch the game!
+
+ Run `spice64.exe`, press `Yes` when it asks for elevated privileges.
+
+ The game will go through a series of checks, let it run, if you've done everything properly they'll pass.
+
+ 
+
+ If you're seeing this screen, it means you need to calibrate your knobs.
+
+ Press your `Test` key to go to the service menu.
+
+ Instructions on how to navigate the menu are shown at the bottom of the screen:
+
+ - Press `BT-A` to go up
+ - Press `BT-B` to go down
+ - Press `Start` to select
+
+ Select `I/O CHECK` and press `Start`.
+
+ 
+
+ Select `CALIBRATION SETTINGS` and press `Start`.
+
+ 
+ 
+
+ Select `CALIBRATION` and press `Start`.
+
+ First, your left knob (`VOL-L` for keyboard players)
+
+ - **Slowly turn** your **LEFT knob counterclockwise** (`VOL-L Left`) until the line says `COUNT = OK` then press `Start`.
+ - **Slowly turn** your **LEFT knob clockwise** (`VOL-L Right`) until the line says `COUNT = OK` then press `Start`.
+
+ Now same thing but for the right knob (`VOL-R` for keyboard players)
+
+ - **Slowly turn** your **RIGHT knob counterclockwise** (`VOL-R Left`) until the line says `COUNT = OK` then press `Start`.
+ - **Slowly turn** your **RIGHT knob clockwise** (`VOL-R Right`) until the line says `COUNT = OK` then press `Start`.
+
+ 
+
+ Select `SAVE AND EXIT` and press `Start`.
+
+ 
+
+ Select `GAME MODE` and press `Start`.
+
+!!! success "You're all done! The game should load up properly now"
+
+## Help
+
+--8<-- "docs/snippets/common/help.md"
diff --git a/docs/games/konami/sdvx/6_exceedgear/troubleshooting.md b/docs/games/konami/sdvx/6_exceedgear/troubleshooting.md
new file mode 100644
index 0000000..fc8e21b
--- /dev/null
+++ b/docs/games/konami/sdvx/6_exceedgear/troubleshooting.md
@@ -0,0 +1,141 @@
+
+# Troubleshooting
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+!!! info "For any issues not covered here, spice2x's [Known issues](https://github.com/spice2x/spice2x.github.io/wiki/Known-issues) page might prove useful"
+
+## Technical problems
+
+### Crashes
+
+!!! info "Riva Tuner Statistics Server (RTSS) and MSI Afterburner are known to cause odd crashes.
+# Extra Information
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+!!! warning "Starting with Nabla, Nemsys cabs (60 FPS mode) are no longer officially supported"
+
+ However the F spec and BIO2/Valkyrie 60hz patches still seem to work for the time being, though beware things most likely will break in the future.
+
+# Nemsys and Valkyrie modes
+
+!!! warning "Valkyrie mode requires a 120 Hz capable monitor, or to have patched your `.dll` with `Valkyrie Mode 60 Hz`"
+
+!!! tip ""
+
+ To make use of the Valkyrie Mode (Subscreen, 120FPS, S-CRITICAL..) you need to go to the `contents\prop` folder and edit the `ea3-config.xml` file.
+
+ We're interested in these lines:
+
+ ```xml
+
+# Game Setup
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+## Preparing data
+
+--8<-- "docs/snippets/common/data_readonly.md"
+
+ The **complete game data** should be approximately **20 GB or larger**.
+ If your data is significantly smaller, you likely have an update archive instead of the full game data.
+
+ Here's what the expected data structure should look like:
+
+ ```
+ 📂data
+ 📂dev
+ 📂ext
+ 📂modules
+ 📂prop
+ ```
+
+--8<-- "docs/snippets/konami/common/data_bad.md"
+
+!!! info "If your data is already up-to-date, you can skip ahead to the [Installing spice2x](#installing-spice2x) section"
+
+## Updating data
+
+!!! info "For a comprehensive list of all game updates in chronological order, visit [BemaniWiki](https://bemaniwiki.com/?SOUND+VOLTEX+%A2%E0#sdvxnblvernew)"
+
+!!! danger "Make sure you're using the right update for your current game version"
+
+ SDVX updates have `KFC` and one or two datecodes in their archive names.
+
+ **Single datecode:** Contains one update (e.g., `KFC_NewDateCode.7z`)
+ **Two datecodes:** Updates from the older to newer version (e.g., `KFC-OldDateCode-NewDateCode.rar`)
+
+ In the two-datecode example:
+
+ - `OldDateCode` is the older date, the game version required to apply this update
+ - `NewDateCode` is the newer date, and is the version you'll arrive at after applying the update
+
+--8<-- "docs/snippets/konami/common/data_update.md"
+
+## Installing spice2x
+
+--8<-- "docs/snippets/konami/common/spice2x64_install.md"
+
+ ``` hl_lines="6-7"
+ 📂data
+ 📂dev
+ 📂ext
+ 📂modules
+ 📂prop
+ 🌶️spice64.exe
+ 🌶️spicecfg.exe
+ ```
+
+--8<-- "docs/snippets/konami/common/spice2x64_stubs.md"
+
+## Configuring spice2x
+
+--8<-- "docs/snippets/konami/common/spicecfg_preamble.md"
+
+=== "Buttons"
+
+--8<-- "docs/snippets/konami/common/spicecfg_buttons.md"
+
+--8<-- "docs/snippets/konami/sdvx/spicecfg_buttons.md"
+
+--8<-- "docs/snippets/konami/common/spicecfg_buttons_additionalinfo.md"
+
+=== "Analogs"
+
+--8<-- "docs/snippets/konami/sdvx/spicecfg_analogs.md"
+
+=== "Overlay"
+
+--8<-- "docs/snippets/konami/common/spicecfg_overlay.md"
+
+=== "Lights"
+
+--8<-- "docs/snippets/konami/common/spicecfg_lights.md"
+
+=== "Cards"
+
+--8<-- "docs/snippets/konami/common/spicecfg_cards.md"
+
+=== "Patches"
+
+--8<-- "docs/snippets/konami/common/spicecfg_patches.md"
+
+=== "API"
+
+--8<-- "docs/snippets/konami/common/spicecfg_nochange.md"
+
+=== "Options"
+
+--8<-- "docs/snippets/konami/common/spicecfg_options.md"
+
+--8<-- "docs/snippets/konami/common/spicecfg_options_nvprofile.md"
+
+=== "Advanced"
+
+--8<-- "docs/snippets/konami/common/spicecfg_nochange.md"
+
+=== "Development"
+
+--8<-- "docs/snippets/konami/common/spicecfg_nochange.md"
+
+## Configuring audio
+
+--8<-- "docs/snippets/konami/common/setup_audio.md"
+
+## Connecting to a network
+
+--8<-- "docs/snippets/konami/common/setup_network.md"
+
+## Configuring your game
+
+!!! info "Read through the [Extra Information](extras.md) page"
+
+## Monitor Orientation
+
+--8<-- "docs/snippets/konami/common/display_portraitfirst.md"
+
+## Installing VCRedist & DirectX
+
+--8<-- "docs/snippets/common/setup_vcredist_directx.md"
+
+## Before playing
+
+--8<-- "docs/snippets/common/before_playing.md"
+
+## First launch
+
+!!! tip ""
+
+ If you've followed all instructions correctly, you're finally ready to launch the game!
+
+ Run `spice64.exe`, press `Yes` when it asks for elevated privileges.
+
+ The game will go through a series of checks, let it run, if you've done everything properly they'll pass.
+
+
+
+ If you're seeing this screen, it means you need to calibrate your knobs.
+
+ Press your `Test` key to go to the service menu.
+
+ Instructions on how to navigate the menu are shown at the bottom of the screen:
+
+ - Press `BT-A` to go up
+ - Press `BT-B` to go down
+ - Press `Start` to select
+
+ Select `I/O CHECK` and press `Start`.
+
+
+
+ Select `CALIBRATION SETTINGS` and press `Start`.
+
+
+
+
+ Select `CALIBRATION` and press `Start`.
+
+ First, your left knob (`VOL-L` for keyboard players)
+
+ - **Slowly turn** your **LEFT knob counterclockwise** (`VOL-L Left`) until the line says `COUNT = OK` then press `Start`.
+ - **Slowly turn** your **LEFT knob clockwise** (`VOL-L Right`) until the line says `COUNT = OK` then press `Start`.
+
+ Now same thing but for the right knob (`VOL-R` for keyboard players)
+
+ - **Slowly turn** your **RIGHT knob counterclockwise** (`VOL-R Left`) until the line says `COUNT = OK` then press `Start`.
+ - **Slowly turn** your **RIGHT knob clockwise** (`VOL-R Right`) until the line says `COUNT = OK` then press `Start`.
+
+
+
+ Select `SAVE AND EXIT` and press `Start`.
+
+
+
+ Select `GAME MODE` and press `Start`.
+
+!!! success "You're all done! The game should load up properly now"
+
+## Help
+
+--8<-- "docs/snippets/common/help.md"
diff --git a/docs/games/konami/sdvx/7_nabla/troubleshooting.md b/docs/games/konami/sdvx/7_nabla/troubleshooting.md
new file mode 100644
index 0000000..e7ce1b9
--- /dev/null
+++ b/docs/games/konami/sdvx/7_nabla/troubleshooting.md
@@ -0,0 +1,126 @@
+
+# Troubleshooting
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+!!! info "For any issues not covered here, spice2x's [Known issues](https://github.com/spice2x/spice2x.github.io/wiki/Known-issues) page might prove useful"
+
+## Technical problems
+
+### Crashes
+
+!!! info "Riva Tuner Statistics Server (RTSS) and MSI Afterburner are known to cause odd crashes.
+# Game Setup
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+## Preparing data
+
+!!! tip ""
+
+ Taiko is generally distributed as a single folder. For Nijiiro, this will be `SBWY 39.06`. The game folder should contain an `AMCUS`, `Data` and `Executable` folder.
+
+
+
+!!! danger "Nijiiro is a rolling release so please verify your game version by opening `AMCUS\AMConfig.ini` and verifying that it says `cacfg-game_ver=39.06`"
+
+!!! info "NAMCO data is also distributed as `.VHDX` and `.VHD` files. These files are useful for archival purposes, but are not required to run the game. Always download the unpacked data for home use"
+
+## Installing TaikoArcadeLoader (TAL)
+
+!!! tip "TaikoArcadeLoader:"
+
+ `TaikoArcadeLoader` is a loader and hardware emulator for Nijiiro. It will allow us to launch the game, as well as configure inputs and network settings. More information can be found at the [TAL github page](https://github.com/esuo1198/TaikoArcadeLoader).
+
+ - Download the latest version of TAL from [the actions tab](https://github.com/esuo1198/TaikoArcadeLoader/actions) of the TAL page. This will be a file named `TaikoArcadeLoader`. You will need to be logged into github to download this file.
+
+ - Copy the files from `TaikoArcadeLoader.zip` to your `Executable/Release` folder. When asked, choose to replace the existing files with the newly copied files.
+
+ 
+
+## Configuring TaikoArcadeLoader
+
+!!! tip ""
+
+ The configuration information for TaikoArcadeLoader is stored within `config.toml`.
+
+ Open up `config.toml` with a text editor of your choice. We'll be using [Notepad++](https://notepad-plus-plus.org/).
+
+!!! info "`config.toml` is separated into several sections, indicated by the section name in `[square brackets]`"
+ Information for this can be found at the [TAL github page](https://github.com/esuo1198/TaikoArcadeLoader).
+
+!!! tip "The `[amauth]` section contains network related config"
+
+ - `server =` can be left default if playing on a local server or offline but it is recommend to play on an [online network](#networks).
+ - `port =` do not change unless you know what you are doing.
+ - `chassis_id =` do not change unless you know what you are doing.
+ - `shop_id =` mostly visual. change if you want to.
+ - `game_ver =` mostly visual. change if you want to.
+ - `country_code =` do not change unless you know what you are doing.
+
+ ```toml
+ [amauth]
+ server = "127.0.0.1"
+ port = "54430"
+ chassis_id = "284111080000"
+ shop_id = "TWO-TORIAL"
+ game_ver = "39.06"
+ country_code = "JPN"
+ ```
+
+!!! tip "The `[graphics]` section contains patches"
+
+ - `res =` change to your display's resolution.
+ - `windowed =` set to `true` if you want to run the game in windowed.
+ - `cursor =` mostly visual. change if you want to.
+ - `vsync =` set to `true` if your display is set to 120 Hz.
+ - `fpslimit =` do not change unless you know what you are doing.
+ - `model_res_rate =` do not change unless you know what you are doing.
+
+ ```toml
+ [graphics]
+ res = { x = 1920, y = 1080 }
+ windowed = false
+ cursor = true
+ vsync = false
+ # fpslimit = 0
+ model_res_rate = 1.0
+ ```
+
+!!! tip "The `[keyboard]` section contains keyboard related config"
+
+ - `auto_ime =` if set to true, changes your keyboard layout to Qwerty until the game is closed.
+ - `jp_layout =` should be set to `true` for **actual** japanese keyboards.
+
+ ```toml
+ [keyboard]
+ auto_ime = false
+ jp_layout = false
+ ```
+
+## Configuring Inputs
+
+!!! tip ""
+
+ Depending on the input method you choose, the configuration for them can change slightly. Below are all the input methods available and how to set them up.
+
+??? tip "Keyboard"
+
+ Keyboard is the default input method.
+
+ The default layout uses:
+
+ - ++d++++f++ ++j++++k++ for the P1 drum input
+ - ++z++++x++ ++c++++v++ for the P2 drum input
+ - ++p++ to `Insert Card`
+ - ++f2++ to `SERVICE`
+ - ++enter++ to add coins
+
+ If you wish to view or change all the default keybinds, you can do so in `keyconfig.toml`
+
+??? tip "Controller"
+
+ The setup for both drum and normal controllers is the same.
+
+ - In `config.toml` set `wait_period =` to `0`
+ - If you are using a controller that does not use keyboard inputs, you need to set SDL keybinds in `keyconfig.toml`
+ - When you're using an analog input for the drums, you need to set `analog_input = false` to `true` in `config.toml`
+
+ A list of valid SDL inputs can be found at the bottom of `keyconfig.toml`
+
+ !!! danger "If you're using 2 controllers, use [JoyToKey](https://joytokey.net/en/) and remove SDL inputs from `keyconfig.toml`"
+
+??? tip "Physical Card Readers"
+
+ You can insert your card with physical card readers. If you happen to have one, you can set them up to use them for Taiko no Tatsujin Nijiiro.
+
+
+ ??? tip "AIC Pico"
+ - In `config.toml` set `card_reader =` to `false`.
+ - Update to the latest [firmware](https://github.com/whowechina/aic_pico)
+ - Inside `AMFWConfig.ini` change COM4 to the port of your AIC Pico
+
+ ??? tip "ACR122U"
+ - In `config.toml` set `card_reader =` to `true`.
+ - Use AkaiiKitsune's [tal-cardreader plugin](https://gitea.farewell.dev/AkaiiKitsune/tal-cardreader)
+
+!!! note "If you don't have a physical card reader, you can skip over to the [Networks](#networks) section"
+
+## Networks
+
+!!! danger "Please choose one of the two solutions, not both!"
+
+??? tip "Online Hosted Servers (Recommended)"
+
+ There are a few online hosted servers that support Nijiiro, however most of them are currently invite only. Ask your friends where they play, and maybe they'll invite you!
+
+ **Elara Global Taiko Server**
+
+ [EGTS](https://webui.egts.ca/guide) is the only public Nijiiro server that also comes with an Omnimix verison that includes custom songs and songs from other Taiko games.
+
+??? tip "Self Hosted Local Servers (Complex)"
+
+ If you wish to run the game locally, but with the ability to create and save a profile, you can run a server on the same computer you are playing the game on. This server will need to be running before you launch the game, however it can be shut down when you are no longer playing.
+
+ Any provided setup instructions are likely to become outdated rather quickly.
+
+ Please refer to the included setup instructions on each projects respective web page.
+
+ - [TLS](https://github.com/asesidaa/TaikoLocalServer/tree/Refactor) - A network service emulator for Nijiiro. Setup can be complex as you are required to build TLS from source using [VisualStudio](https://visualstudio.microsoft.com/) and `.sln` files.
+
+## Pre-launch requirements
+
+!!! info "These steps are required, otherwise your game won't run"
+
+#### VCRedist & DirectX
+
+!!! tip ""
+
+ - Download and install the latest [VCRedist](https://www.techpowerup.com/download/visual-c-redistributable-runtime-package-all-in-one/)
+ - Download and install the [DirectX End-User Runtimes](https://www.microsoft.com/en-us/download/details.aspx?id=8109)
+
+## First Launch
+
+!!! tip ""
+
+ Run `Taiko.exe` to start the game.
+
+ Enter the I/O setup screen by pressing ++f1++ on the Attract screen then using the `arrow keys` and ++enter++, navigate to `I/O TEST` -> `TAIKO TEST`. Adjust these settings to your liking as they vary between controllers and keyboards. If you are unsure just leave the defaults as is.
+
+ If you would like to adjust patch settings enter the test menu by pressing ++f1++ on the Attract screen then using the `arrow keys` and ++enter++, navigate to `MOD MANAGER`.
+
+ 
+
+!!! tip ""
+
+ You're all done! The game should load up properly now.
+
+## Troubleshooting
+
+!!! warning "Have any other issue?"
+
+ Check out the [Troubleshooting](troubleshooting.md) page.
\ No newline at end of file
diff --git a/docs/games/namco/taikonijiiro/troubleshooting.md b/docs/games/namco/taikonijiiro/troubleshooting.md
new file mode 100644
index 0000000..212fcdf
--- /dev/null
+++ b/docs/games/namco/taikonijiiro/troubleshooting.md
@@ -0,0 +1,123 @@
+
+# Troubleshooting
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+### Changing the Language
+
+!!! tip ""
+
+ Nijiiro supports changing the language from the test menu. The officially supported languages are:
+
+ - Japanese (Default)
+ - English
+ - Chinese (zh-TW)
+ - Korean
+
+ An unofficial mod allows you to change the language to Chinese (simplified), this can be found on the [Discord](https://discord.gg/cZRUmEPK78).
+
+ Using ++f1++, the `arrow keys` and ++enter++, navigate to `OTHERS` -> `LANGUAGE`
+
+
+
+### My game is frozen/black screen
+
+!!! tip ""
+
+ You can fix this by running the game as admin. You can also try updating windows and gpu drivers.
+
+### My game takes a long time to boot
+
+!!! info "First boot after connecting to a network will be very long (>90s)"
+
+!!! tip ""
+
+ The game files for Nijiiro consists of thousands of small `.bin` files and Windows Defender is known to spend a long time scanning through them during game boot up.
+
+ One way to massively speed up boot times is to add the entire game folder as a Windows Defender Exception.
+
+ Doing this will prevent Defender from scanning your game folder for viruses.
+
+!!! danger "Only do this if you trust the source of your data!"
+
+!!! tip ""
+
+ - Open `Virus & threat protection`.
+ - Under `Virus & threat protection settings` click the `Manage Settings` button.
+ - Scroll down to `Exclusions` and click on `Add or remove exclusions`.
+ - Click the `Add an exclusion` button, select the `folder` option, navigate to the root of your game installation and click `Select Folder`.
+
+
+
+### My game is running crazy fast/slow
+
+!!! tip ""
+
+ The game needs to be ran at 120 FPS or things will break.
+
+ ??? tip "If you have a display that supports 120 Hz or higher"
+ - Set your display to 120 Hz. You may need to make a [custom resolution](https://customresolutionutility.net/).
+ - In `config.toml` set `vsync =` to `true`.
+
+ ??? tip "If you have a display that is less than 120 Hz"
+ - In `config.toml` set `vsync =` to `false` and `windowed =` to `true`.
+ - Alternatively you can use [RTSS](https://www.guru3d.com/download/rtss-rivatuner-statistics-server-download/).
+
+### My game is not connected to a network but I set one up
+
+!!! tip "Disable shop close time or you won't always be able to connect to the network"
+
+ Using ++f1++ `arrow keys` and ++enter++ navigate to `GAME OPTIONS` -> `CLOCK/CLOSE TIME SETTING` -> `SCHEDULE TYPE`.
+
+ 
+
+ If you are still unable to connect that means you have incorrectly configured your `config.toml` or your server.
+
+### My game is still too big/small after setting the resolution in `config.toml`
+
+!!! tip ""
+
+ This will happen if you incorrectly set your resolution or scale.
+
+ You can check your display resolution by right clicking your desktop and selecting `Display settings`.
+
+ You can set your scale to `100%` right above where it says your resolution.
+
+ 
+
+### My controller is dropping inputs / I can't hit good drumrolls
+
+!!! tip ""
+
+ This a common issue on some controllers.
+
+ In `config.toml` increase `wait_period =` by 1, then test it in-game and repeat until it feels correct.
+
+### Best settings for Nvidia GPUs
+
+!!! tip ""
+
+ This will help with latency and other issues
+
+ In `NVIDIA Control Panel` set the following settings for `Taiko.exe`.
+
+ - Low Latency Mode `Ultra`
+ - Power management mode `Prefer maximum performance`
+ - Vertical sync `Fast`
+
+### Audio
+
+!!! tip ""
+
+ By default the game will use WASAPI Shared
+
+ To use WASAPI exclusive:
+
+ - Inside `config.toml`, set `wasapi_shared =` to `false`
+
+ To use ASIO:
+
+ - Inside `config.toml`, set `wasapi_shared =` to `false` and set `asio =` to `true`.
+ - Change `asio_driver =` to `asio_driver = "
+
+--8<-- "docs/games/sega/chunithm/common/chuni/c2c.md"
diff --git a/docs/games/sega/chunithm/air/controllers.md b/docs/games/sega/chunithm/air/controllers.md
new file mode 100644
index 0000000..a61ce8f
--- /dev/null
+++ b/docs/games/sega/chunithm/air/controllers.md
@@ -0,0 +1,3 @@
+
+
+--8<-- "docs/games/sega/chunithm/common/chuni/controllers.md"
diff --git a/docs/games/sega/chunithm/air/setup.md b/docs/games/sega/chunithm/air/setup.md
new file mode 100644
index 0000000..1e210ce
--- /dev/null
+++ b/docs/games/sega/chunithm/air/setup.md
@@ -0,0 +1,4 @@
+
+
+
+--8<-- "docs/games/sega/chunithm/common/chuni/setup_belowcrystal.md"
diff --git a/docs/games/sega/chunithm/air/troubleshooting.md b/docs/games/sega/chunithm/air/troubleshooting.md
new file mode 100644
index 0000000..7f277a1
--- /dev/null
+++ b/docs/games/sega/chunithm/air/troubleshooting.md
@@ -0,0 +1,3 @@
+
+
+--8<-- "docs/games/sega/chunithm/common/chuni/troubleshooting.md"
diff --git a/docs/games/sega/chunithm/airplus/c2c.md b/docs/games/sega/chunithm/airplus/c2c.md
new file mode 100644
index 0000000..d699af5
--- /dev/null
+++ b/docs/games/sega/chunithm/airplus/c2c.md
@@ -0,0 +1,3 @@
+
+
+--8<-- "docs/games/sega/chunithm/common/chuni/c2c.md"
diff --git a/docs/games/sega/chunithm/airplus/controllers.md b/docs/games/sega/chunithm/airplus/controllers.md
new file mode 100644
index 0000000..bc45855
--- /dev/null
+++ b/docs/games/sega/chunithm/airplus/controllers.md
@@ -0,0 +1,3 @@
+
+
+--8<-- "docs/games/sega/chunithm/common/chuni/controllers.md"
diff --git a/docs/games/sega/chunithm/airplus/setup.md b/docs/games/sega/chunithm/airplus/setup.md
new file mode 100644
index 0000000..d7edfaa
--- /dev/null
+++ b/docs/games/sega/chunithm/airplus/setup.md
@@ -0,0 +1,4 @@
+
+
+
+--8<-- "docs/games/sega/chunithm/common/chuni/setup_belowcrystal.md"
diff --git a/docs/games/sega/chunithm/airplus/troubleshooting.md b/docs/games/sega/chunithm/airplus/troubleshooting.md
new file mode 100644
index 0000000..d0e6b21
--- /dev/null
+++ b/docs/games/sega/chunithm/airplus/troubleshooting.md
@@ -0,0 +1,3 @@
+
+
+--8<-- "docs/games/sega/chunithm/common/chuni/troubleshooting.md"
diff --git a/docs/games/sega/chunithm/amazon/c2c.md b/docs/games/sega/chunithm/amazon/c2c.md
new file mode 100644
index 0000000..6619e79
--- /dev/null
+++ b/docs/games/sega/chunithm/amazon/c2c.md
@@ -0,0 +1,3 @@
+
+
+--8<-- "docs/games/sega/chunithm/common/chuni/c2c.md"
diff --git a/docs/games/sega/chunithm/amazon/controllers.md b/docs/games/sega/chunithm/amazon/controllers.md
new file mode 100644
index 0000000..373375c
--- /dev/null
+++ b/docs/games/sega/chunithm/amazon/controllers.md
@@ -0,0 +1,3 @@
+
+
+--8<-- "docs/games/sega/chunithm/common/chuni/controllers.md"
diff --git a/docs/games/sega/chunithm/amazon/setup.md b/docs/games/sega/chunithm/amazon/setup.md
new file mode 100644
index 0000000..71798ae
--- /dev/null
+++ b/docs/games/sega/chunithm/amazon/setup.md
@@ -0,0 +1,4 @@
+
+
+
+--8<-- "docs/games/sega/chunithm/common/chuni/setup_belowcrystal.md"
diff --git a/docs/games/sega/chunithm/amazon/troubleshooting.md b/docs/games/sega/chunithm/amazon/troubleshooting.md
new file mode 100644
index 0000000..37a2bf7
--- /dev/null
+++ b/docs/games/sega/chunithm/amazon/troubleshooting.md
@@ -0,0 +1,3 @@
+
+
+--8<-- "docs/games/sega/chunithm/common/chuni/troubleshooting.md"
diff --git a/docs/games/sega/chunithm/amazonplus/c2c.md b/docs/games/sega/chunithm/amazonplus/c2c.md
new file mode 100644
index 0000000..7142d32
--- /dev/null
+++ b/docs/games/sega/chunithm/amazonplus/c2c.md
@@ -0,0 +1,3 @@
+
+
+--8<-- "docs/games/sega/chunithm/common/chuni/c2c.md"
diff --git a/docs/games/sega/chunithm/amazonplus/controllers.md b/docs/games/sega/chunithm/amazonplus/controllers.md
new file mode 100644
index 0000000..ce7b15f
--- /dev/null
+++ b/docs/games/sega/chunithm/amazonplus/controllers.md
@@ -0,0 +1,3 @@
+
+
+--8<-- "docs/games/sega/chunithm/common/chuni/controllers.md"
diff --git a/docs/games/sega/chunithm/amazonplus/setup.md b/docs/games/sega/chunithm/amazonplus/setup.md
new file mode 100644
index 0000000..e781622
--- /dev/null
+++ b/docs/games/sega/chunithm/amazonplus/setup.md
@@ -0,0 +1,4 @@
+
+
+
+--8<-- "docs/games/sega/chunithm/common/chuni/setup_belowcrystal.md"
diff --git a/docs/games/sega/chunithm/amazonplus/troubleshooting.md b/docs/games/sega/chunithm/amazonplus/troubleshooting.md
new file mode 100644
index 0000000..c82d5cb
--- /dev/null
+++ b/docs/games/sega/chunithm/amazonplus/troubleshooting.md
@@ -0,0 +1,3 @@
+
+
+--8<-- "docs/games/sega/chunithm/common/chuni/troubleshooting.md"
diff --git a/docs/games/sega/chunithm/chunithm/c2c.md b/docs/games/sega/chunithm/chunithm/c2c.md
new file mode 100644
index 0000000..ea9edc1
--- /dev/null
+++ b/docs/games/sega/chunithm/chunithm/c2c.md
@@ -0,0 +1,3 @@
+
+
+--8<-- "docs/games/sega/chunithm/common/chuni/c2c.md"
diff --git a/docs/games/sega/chunithm/chunithm/controllers.md b/docs/games/sega/chunithm/chunithm/controllers.md
new file mode 100644
index 0000000..03cf06e
--- /dev/null
+++ b/docs/games/sega/chunithm/chunithm/controllers.md
@@ -0,0 +1,3 @@
+
+
+--8<-- "docs/games/sega/chunithm/common/chuni/controllers.md"
diff --git a/docs/games/sega/chunithm/chunithm/setup.md b/docs/games/sega/chunithm/chunithm/setup.md
new file mode 100644
index 0000000..4c0fa03
--- /dev/null
+++ b/docs/games/sega/chunithm/chunithm/setup.md
@@ -0,0 +1,4 @@
+
+!!! warning "Warning"
+ This guide is for the original version of CHUNITHM released in 2015. If you want to run a newer version, please find and follow the right guide.
+--8<-- "docs/games/sega/chunithm/common/chuni/setup_belowcrystal.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/chunithm/troubleshooting.md b/docs/games/sega/chunithm/chunithm/troubleshooting.md
new file mode 100644
index 0000000..e5afbc8
--- /dev/null
+++ b/docs/games/sega/chunithm/chunithm/troubleshooting.md
@@ -0,0 +1,3 @@
+
+
+--8<-- "docs/games/sega/chunithm/common/chuni/troubleshooting.md"
diff --git a/docs/games/sega/chunithm/common/chuni/c2c.md b/docs/games/sega/chunithm/common/chuni/c2c.md
new file mode 100644
index 0000000..17d3584
--- /dev/null
+++ b/docs/games/sega/chunithm/common/chuni/c2c.md
@@ -0,0 +1,45 @@
+# Cab-to-Cab over Internet
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+!!! danger "You are most likely to have success with Multiplayer when all users are using the SAME data and options, from the same sources. Verify that each person can run the game normally before attempting to network them together"
+
+## Initial setup
+
+!!! tip "Network"
+
+ Every machine needs to be on the same LAN.
+ If you wish to achieve that over the internet, follow the [ZeroTier setup guide](/extras/zerotier.md).
+
+!!! tip "GAME ASSIGNMENTS"
+
+ - Open the Service Menu and navigate to `GAME ASSIGNMENTS`
+ 
+
+ - Make sure all machines are on the same group (Group A for example)
+ 
+
+ - Set one machine to `STANDARD`, and all other machines to `FOLLOW THE STANDARD`
+ 
+ 
+
+ Exit the Service Menu and load into Attract Mode. If the game passes the Group Check then chances are you're good to go! You can now login to a credit and open a cab-to-cab link request to check if the connection is working properly.
+
+## How to link?
+
+!!! Info "If you're new to CHUNITHM and have never tried link-play before and you have no idea how, keep reading"
+
+ - Login to a credit
+
+ - If you're hosting a cab-to-cab session, choose a song first, then scroll to the far left and press `Confirm`
+ The cab-to-cab request is now open
+ 
+
+ - If you're connecting, navigate to the `Cabinet-to-Cabinet Play` tab and wait for other players to create a session
+ 
+
+ If you are able to see each other's session, congrats! You can now enjoy some cab-to-cab chain action!
+
+## Help
+
+--8<-- "docs/snippets/common/help.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/common/chuni/controllers.md b/docs/games/sega/chunithm/common/chuni/controllers.md
new file mode 100644
index 0000000..6fac4b2
--- /dev/null
+++ b/docs/games/sega/chunithm/common/chuni/controllers.md
@@ -0,0 +1,124 @@
+# Controllers
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+!!! tip ""
+
+ segatools, by default, only accepts keyboard input and does not recognize any
+ controllers. However, it can be configured with an IO DLL to add support for controllers.
+
+ The controller you plan on using should also be provided with an IO DLL. If unsure,
+ check the support section for your controller, or contact the vendor directly. Alternate
+ options for the most common controllers are listed below.
+
+ These IO DLLs should be copied to your game's `App\bin\` folder and referenced in
+ `segatools.ini` under the `[chuniio]` section.
+
+!!! tip ""
+
+ To add your IO DLL, ncomment the `path=` line by removing the leading semicolon (`;`),
+ then add your DLL's file name after the `=`:
+
+ ```ini hl_lines="4"
+ [chuniio]
+ ; To use a custom Chunithm IO DLL enter its path here.
+ ; Leave empty if you want to use Segatools built-in keyboard input.
+ path=controller.dll
+ ```
+
+ 1. Note that there is no leading semicolon.
+
+### Keyboard
+
+!!! tip ""
+
+ Keyboard is the default input method, and while not recommended for playing the game,
+ it is useful for testing purposes.
+
+ The default layout uses `SDFGHJKL` for slider input, and `Space Bar` for the AIRs.
+
+ If you wish to change the default keybinds, an explanation on how to set these is included
+ above the `[io3]` section in your `segatools.ini`.
+
+### TASOLLER
+
+!!! tip ""
+
+ - Install the [custom Host and LED firmware](https://pixeldrain.com/u/DajSPEoa) to your controller.
+ Instructions on how to do so is provided in the linked archive.
+ - Download the TASOLLER IO DLL corrosponding to your firmware version and extract to your `App\bin` folder.
+ - [chuniio-rs](https://gitea.tendokyu.moe/beerpsi/chuniio-rs/releases) (download `chuni.zip`)
+ - Edit your `App\bin\segatools.ini` to reference the extracted DLLs:
+
+ ```ini
+ [chuniio]
+ path=chuniio_tasoller_v2.dll
+ ```
+
+ - Connect the controller to your computer, and then start the game.
+
+### TASOLLER PLUS
+
+!!! tip ""
+
+ - Switch your TASOLLER PLUS to WINUSB mode. You can do so in TASOLLER Options
+ found on the djdao [support page](https://www.dj-dao.com/en/support/22.html).
+ - Download TASOLLER PLUS IO DLLs and extract to your `App\bin` folder.
+ - [chuniio-rs](https://gitea.tendokyu.moe/beerpsi/chuniio-rs/releases) (download `chuni.zip`)
+ - Edit your `App\bin\segatools.ini` to reference the extracted DLLs:
+
+ ```ini
+ [chuniio]
+ path=chuniio_tasoller_plus.dll
+ ```
+
+ - Connect the controller to your computer, and then start the game.
+
+### YubiDeck
+
+!!! tip ""
+
+ - Switch your YubiDeck to HID output mode. Instructions on how to do so are provided
+ in the [YubiDeck manual](https://drive.google.com/file/d/11KVlKbg3zGCRwI7R-30t2IJc6OQwDEgo/view).
+ - Download the latest **chuni** version of [YubiDeck IO DLLs](https://gitea.tendokyu.moe/beerpsi/chuniio-yubideck/releases)
+ and extract it to your `App\bin` folder.
+ - Edit your `App\bin\segatools.ini` to reference the extracted DLLs:
+
+ ```ini
+ [chuniio]
+ path=chuniio_yubideck_v3.dll
+ ```
+
+ - Optionally, reference the included AimeIO DLL to use the controller's
+ built-in card reader:
+
+ ```ini
+ [aimeio]
+ path=aimeio_yubideck_v3.dll
+ ```
+
+ - Connect the controller to your computer, and then start the game.
+
+### Laverita 3
+
+!!! tip ""
+
+ - Switch your Laverita to HID mode. You can do so in ConfigApp
+ - Download Laverita IO DLLs and extract to your `App\bin` folder.
+ - [chuniio-rs](https://gitea.tendokyu.moe/beerpsi/chuniio-rs/releases) (download `chuni.zip`)
+ - Edit your `App\bin\segatools.ini` to reference the extracted DLLs:
+
+ ```ini
+ [chuniio]
+ path=chuniio_laverita_v3.dll
+ ```
+
+ - Connect the controller to your computer, and then start the game.
+
+### Arcade hardware and other controllers
+
+!!! tip ""
+
+ If you're interested in using a cabinet slider and air sensors, or possibly even
+ making your own controller, the [Cons&Stuff website](https://consandstuff.github.io/)
+ and Discord community is a great place to start!
diff --git a/docs/games/sega/chunithm/common/chuni/setup.md b/docs/games/sega/chunithm/common/chuni/setup.md
new file mode 100644
index 0000000..36f4553
--- /dev/null
+++ b/docs/games/sega/chunithm/common/chuni/setup.md
@@ -0,0 +1,172 @@
+# Game Setup
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+--8<-- "docs/snippets/sega/common/data_old.md"
+
+## Preparing data
+
+--8<-- "docs/snippets/sega/common/data_driveletter.md"
+
+--8<-- "docs/snippets/common/data_readonly.md"
+
+--8<-- "docs/snippets/sega/common/data_preparation.md"
+
+ ```
+ 📂bin
+ 📂data
+ 📂firm
+ 📂startup
+ 📄firewall.cfg
+ ▶️game.bat
+ ▶️oxGetHwInfo.exe
+ 📝oxGetHwInfo.ini
+ ```
+
+--8<-- "docs/snippets/sega/common/data_bad.md"
+
+## Updating data
+
+--8<-- "docs/snippets/sega/common/data_updating.md"
+
+## Installing option data
+
+--8<-- "docs/snippets/sega/chunithm/data_options.md"
+
+## Installing unprotected executables
+
+!!! tip ""
+
+ CHUNITHM executables are protected and will not run on a regular computer.
+
+ Obtain unprotected (also called "unpacked" or "decrypted" by the community) copies of `chuniApp.exe` and `aimeReaderHost.exe` for your game version.
+
+ - Copy `chuniApp.exe` and `aimeReaderHost.exe` to data's `App\bin` folder
+ - Agree to overwrite when asked
+
+## Installing ICFs
+
+--8<-- "docs/snippets/sega/common/data_icfs.md"
+
+## Patching the game
+
+--8<-- "docs/snippets/sega/common/patching.md"
+
+| Patch | Recommendation | Description |
+|------------------------------|----------------|-------------|
+| Disable shop close lockout | Either | Disables the shop lockout from 12 to 8PM JST. |
+| Force shared audio mode | Either | Force the game to use shared mode audio output, letting you listen to other audio sources while the game is running **at the cost of audio latency.** |
+| Force 2 channel audio output | Either | Try enabling this patch if you don't get audio output at all. |
+| Disable song select timer | Either | Disables the song select timer. |
+| No encryption | ON | Disable encrypting network requests. **Required if you plan to run a local server.** |
+| No TLS | ON | Disable checking if the server is `HTTPS` or not. **Required if you plan to run a local server.** |
+
+## Installing segatools
+
+--8<-- "docs/snippets/sega/common/segatools_install.md"
+ - Find `chuni.zip` and extract it to your data's `App\bin` folder
+
+ You should now have these files added to your `App\bin` directory:
+
+ ```
+ 📂DEVICE
+ ⚙️chunihook.dll
+ ▶️inject.exe
+ 📝segatools.ini
+ ▶️launch.bat
+ ```
+
+## Configuring segatools
+
+!!! tip ""
+
+--8<-- "docs/snippets/sega/common/segatools_preamble_bin.md"
+
+=== "[vfs]"
+
+--8<-- "docs/snippets/sega/common/segatools_relativepaths.md"
+
+--8<-- "docs/snippets/sega/common/segatools_vfs.md"
+
+=== "[gfx]"
+
+--8<-- "docs/snippets/sega/chunithm/segatools_gfx.md"
+
+## Configuring audio
+
+--8<-- "docs/snippets/common/audio_48khz.md"
+
+## Connecting to a network
+
+--8<-- "docs/snippets/sega/common/network_preamble.md"
+
+--8<-- "docs/snippets/sega/common/network_remote.md"
+
+--8<-- "docs/snippets/sega/common/network_local_artemisonly.md"
+
+## Installing VCRedist & DirectX
+
+--8<-- "docs/snippets/common/setup_vcredist_directx.md"
+
+## Before playing
+
+--8<-- "docs/snippets/common/before_playing.md"
+
+## First launch
+
+--8<-- "docs/snippets/sega/common/service_jp_googlelens.md"
+
+!!! tip ""
+
+ If you've followed all instructions correctly, you're now finally ready to launch the game!
+
+ Start the game by running `App\bin\launch.bat`. Let the game load until it reaches the screen below.
+
+ 
+
+ Press your `Test` button (default `F1`) to enter the service menu. Use the `Service` button
+ (default `F2`) to navigate the menu, and `Test` button to select an option.
+
+ Navigate to **ゲーム設定** (`GAME ASSIGNMENTS`, the fourth option).
+
+ 
+
+ Select **配信サーバー設定** (`DISTRIBUTION SEVER SETTING`, the first option)
+ and toggle this setting to **サーバー** (`SERVER`).
+
+ Select **筐体グループ設定** (`CABINET GROUP SETTINGS`, the second option)
+ and toggle this setting to **OFF**.
+
+ 
+
+ Select **終了** (`EXIT`, the last option) to exit to the main service menu.
+
+ Select **はい** (`YES`) and select **閉じる**
+
+ 
+
+ 
+
+ After this, your game will close. Open it back up, and enter the service menu again.
+
+ Navigate to **閉店設定** (`CLOSE SETTING`, the tenth option).
+
+ 
+
+ Navigate to **時** (`HOUR`, the second option) and use the `Service` button
+ to toggle the setting until it says **全時刻** (`ALL TIME`).
+
+ 
+
+ Select **終了** (`EXIT`, the last option) to exit to the main service menu, then select **終了**
+ (also the last option) in the main menu to exit the service menu.
+
+ If you're stuck at the `Waiting for Distribution Server` screen below, close the game and relaunch.
+
+ 
+
+--8<-- "docs/snippets/sega/common/success.md"
+
+## Help
+
+--8<-- "docs/snippets/common/help.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/common/chuni/setup_belowcrystal.md b/docs/games/sega/chunithm/common/chuni/setup_belowcrystal.md
new file mode 100644
index 0000000..d8acd50
--- /dev/null
+++ b/docs/games/sega/chunithm/common/chuni/setup_belowcrystal.md
@@ -0,0 +1,157 @@
+# Game Setup
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+--8<-- "docs/snippets/sega/common/data_old.md"
+
+## Preparing data
+
+--8<-- "docs/snippets/sega/common/data_driveletter.md"
+
+--8<-- "docs/snippets/common/data_readonly.md"
+
+--8<-- "docs/snippets/sega/common/data_preparation.md"
+
+ ```
+ 📂bin
+ 📂data
+ 📂firm
+ 📂startup
+ 📄firewall.cfg
+ ▶️game.bat
+ ▶️oxGetHwInfo.exe
+ 📝oxGetHwInfo.ini
+ ```
+
+--8<-- "docs/snippets/sega/common/data_bad.md"
+
+## Updating data
+
+--8<-- "docs/snippets/sega/common/data_updating.md"
+
+## Installing option data
+
+--8<-- "docs/snippets/sega/chunithm/data_options.md"
+
+## Installing ICFs
+
+--8<-- "docs/snippets/sega/common/data_icfs.md"
+
+## Patching the game
+
+--8<-- "docs/snippets/sega/common/patching.md"
+
+| Patch | Recommendation | Description |
+|------------------------------|----------------|-------------|
+| Disable shop close lockout | Either | Disables the shop lockout from 12 to 8PM JST. |
+| Force shared audio mode | Either | Force the game to use shared mode audio output, letting you listen to other audio sources while the game is running **at the cost of audio latency.** |
+| Force 2 channel audio output | Either | Try enabling this patch if you don't get audio output at all. |
+| Disable song select timer | Either | Disables the song select timer. |
+
+## Installing segatools
+
+--8<-- "docs/snippets/sega/common/segatools_install.md"
+ - Find `chuni.zip` and extract it to your data's `App\bin` folder
+
+ You should now have these files added to your `App\bin` directory:
+
+ ```
+ 📂DEVICE
+ ⚙️chunihook.dll
+ ▶️inject.exe
+ 📝segatools.ini
+ ▶️launch.bat
+ ```
+
+## Configuring audio
+
+--8<-- "docs/snippets/common/audio_48khz.md"
+
+## Configuring segatools
+
+--8<-- "docs/snippets/sega/common/segatools_preamble_bin.md"
+
+=== "[vfs]"
+
+--8<-- "docs/snippets/sega/common/segatools_vfs.md"
+
+=== "[gfx]"
+
+--8<-- "docs/snippets/sega/chunithm/segatools_gfx.md"
+
+## Connecting to a network
+
+--8<-- "docs/snippets/sega/common/network_preamble.md"
+
+--8<-- "docs/snippets/sega/common/network_remote.md"
+
+--8<-- "docs/snippets/sega/common/network_local_artemisonly.md"
+
+## Installing VCRedist & DirectX
+
+--8<-- "docs/snippets/common/setup_vcredist_directx.md"
+
+## Before playing
+
+--8<-- "docs/snippets/common/before_playing.md"
+
+## First launch
+
+--8<-- "docs/snippets/sega/common/service_jp_googlelens.md"
+
+!!! tip ""
+
+ If you've followed all instructions correctly, you're now finally ready to launch the game!
+
+ Start the game by running `App\bin\launch.bat`. Let the game load until it reaches the screen below.
+
+
+
+ Press your `Test` button (default `F1`) to enter the service menu. Use the `Service` button
+ (default `F2`) to navigate the menu, and `Test` button to select an option.
+
+ Navigate to **ゲーム設定** (`GAME ASSIGNMENTS`, the fourth option).
+
+
+
+ Select **配信サーバー設定** (`DISTRIBUTION SEVER SETTING`, the first option)
+ and toggle this setting to **サーバー** (`SERVER`).
+
+ Select **筐体グループ設定** (`CABINET GROUP SETTINGS`, the second option)
+ and toggle this setting to **OFF**.
+
+
+
+ Select **終了** (`EXIT`, the last option) to exit to the main service menu.
+
+ Select **はい** (`YES`) and select **閉じる**
+
+
+
+
+
+ After this, your game will close. Open it back up, and enter the service menu again.
+
+ Navigate to **閉店設定** (`CLOSE SETTING`, the tenth option).
+
+
+
+ Navigate to **時** (`HOUR`, the second option) and use the `Service` button
+ to toggle the setting until it says **全時刻** (`ALL TIME`).
+
+
+
+ Select **終了** (`EXIT`, the last option) to exit to the main service menu, then select **終了**
+ (also the last option) in the main menu to exit the service menu.
+
+!!! tip ""
+
+ If you're stuck at the `Waiting for Distribution Server` screen below, close the game and relaunch.
+
+
+
+--8<-- "docs/snippets/sega/common/success.md"
+
+## Help
+
+--8<-- "docs/snippets/common/help.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/common/chuni/troubleshooting.md b/docs/games/sega/chunithm/common/chuni/troubleshooting.md
new file mode 100644
index 0000000..1eb5b28
--- /dev/null
+++ b/docs/games/sega/chunithm/common/chuni/troubleshooting.md
@@ -0,0 +1,80 @@
+# Troubleshooting
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+### My game takes a long time to boot!
+
+!!! tip ""
+
+ CHUNITHM game files consist of thousands of small XML files, which Windows Defender
+ takes a long time to scan through. Add your game folder to the Windows Defender
+ exclusion list.
+
+!!! danger
+
+ Doing this will prevent Windows Defender from scanning your game folder for viruses.
+ Only do this if you trust the source of the data.
+
+### My game is running too slow/fast
+
+!!! tip ""
+
+ The game could be running under or over its required refresh rate.
+
+ - Make sure V-Sync isn't disabled in your graphics settings (called "Vertical sync"
+ in NVIDIA Control Panel and "Wait for Vertical Refresh" in AMD Control Panel.)
+ - Make sure your monitor's refresh rate is set to 60Hz.
+
+ It could also be that your computer's performance isn't good enough to keep
+ a steady framerate.
+
+### My game is stuttering
+
+!!! tip ""
+
+ For NVIDIA users, create an override for `chuniApp.exe` in NVIDIA Control Panel
+ and change "Power management mode" to "**Prefer maximum performance**".
+
+### My game crashes when I tab out of fullscreen!
+
+!!! tip ""
+
+ As the game is intended to run on arcade hardware, it doesn't like being minimized.
+
+ One workaround for this is to use DXVK. Download the latest version from [releases](https://github.com/doitsujin/dxvk/releases/latest).
+ This will be a `dxvk-x.y.z.tar.gz` file, which you can open using [7zip](https://www.7-zip.org/).
+ Navigate to the `x32` folder, and copy the `d3d9.dll` file to your game's `App\bin` folder, agreeing
+ to overwrite when asked.
+
+ You should now be able to tab out of fullscreen without crashing the game.
+
+!!! warning
+
+ The game will not ignore inputs when out of focus.
+
+ This means any controller inputs will still be accepted, so try not to lean onto
+ your slider whilst tabbed out!
+
+ This also means that you can accidentally enter the service menu by hitting your
+ `Test` key even if the game is minimised. If you were in the middle of a credit,
+ **your scores will be lost.**
+
+### When I run the game all other audio is gone!
+
+!!! tip ""
+
+ CHUNITHM uses [WASAPI exclusive mode](https://docs.microsoft.com/en-us/windows/win32/coreaudio/exclusive-mode-streams)
+ for audio to get better latency.
+
+ You can apply the "Shared Audio" patch on a CHUNITHM web patcher (see [Resources](/resources.md#web-patchers))
+ to hear audio outside of the game at the cost of audio latency.
+
+### Cabinet-to-Cabinet(c2c) Fixes
+
+!!! tip ""
+
+ c2c can have many problems but you can fix most of them by applying the "Patch for head-to-head play" and disabling "Set all timers to 999" on a CHUNITHM web patcher (see [Resources](/resources.md#web-patchers)).
+
+ If the above does not work then please ensure both machines have the exact same data and can communicate with each other if they cannot then you can try disabling firewalls or changing the c2c group.
+
+ If clicking the c2c button does nothing, you can fix it by resetting the network settings in Windows.
diff --git a/docs/games/sega/chunithm/common/chusan/c2c.md b/docs/games/sega/chunithm/common/chusan/c2c.md
new file mode 100644
index 0000000..c1b1464
--- /dev/null
+++ b/docs/games/sega/chunithm/common/chusan/c2c.md
@@ -0,0 +1,45 @@
+# Cab-to-Cab over Internet
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+!!! danger "You are most likely to have success with Multiplayer when all users are using the SAME data and options, from the same sources. Verify that each person can run the game normally before attempting to network them together"
+
+## Initial setup
+
+!!! tip "Network"
+
+ Every machine needs to be on the same LAN.
+ If you wish to achieve that over the internet, follow the [ZeroTier setup guide](/extras/zerotier.md).
+
+!!! tip "GAME ASSIGNMENTS"
+
+ - Open the Service Menu and navigate to `GAME ASSIGNMENTS`
+
+
+ - Make sure all machines are on the same group (Group A for example)
+
+
+ - Set one machine to `STANDARD`, and all other machines to `FOLLOW THE STANDARD`
+
+
+
+ Exit the Service Menu and load into Attract Mode. If the game passes the Group Check then chances are you're good to go! You can now login to a credit and open a cab-to-cab link request to check if the connection is working properly!
+
+## How to link?
+
+!!! Info "If you're new to CHUNITHM and have never tried link-play before and you have no idea how, keep reading"
+
+ - Login to a credit
+
+ - If you're hosting a cab-to-cab session, choose a song first, then scroll to the far left and press `Confirm`
+ The cab-to-cab request is now open
+
+
+ - If you're connecting, navigate to the `Cabinet-to-Cabinet Play` tab and wait for other players to create a session
+
+
+ If you are able to see each other's session, congrats! You can now enjoy some cab-to-cab chain action!
+
+## Help
+
+--8<-- "docs/snippets/common/help.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/common/chusan/controllers.md b/docs/games/sega/chunithm/common/chusan/controllers.md
new file mode 100644
index 0000000..ba7e338
--- /dev/null
+++ b/docs/games/sega/chunithm/common/chusan/controllers.md
@@ -0,0 +1,376 @@
+# Controllers
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+!!! tip ""
+
+ segatools, by default, only accepts keyboard input and does not recognize any
+ controllers. However, it can be configured with IO DLLs to add support for controllers.
+
+ The controller you plan on using should also be provided with these IO DLLs. If unsure,
+ check the support section for your controller, or contact the vendor directly. Alternate
+ options for the most common controllers are listed below.
+
+ These IO DLLs should be copied to your game's `App\bin\` folder and referenced in
+ `segatools.ini` under the `[chuniio]` section.
+
+!!! tip ""
+
+ If you have a single DLL, uncomment the `path=` line by removing the leading semicolon (`;`),
+ then add your DLL's file name after the `=`:
+
+ ```ini hl_lines="5"
+ [chuniio]
+ ; Uncomment this if you have custom chuniio implementation comprised of a single 32bit DLL.
+ ; (will use chu2to3 engine internally)
+ ;(1)!
+ path=controller.dll
+ ```
+
+ 1. Note that there is no leading semicolon.
+
+!!! tip ""
+
+ If you have two DLLs, ending in `_x86.dll` and `_x64.dll` (or `_chusan.dll` and `_amdaemon.dll`),
+ uncomment the `path32=` and `path64=` lines by removing the leading semicolon (`;`), then
+ add your DLLs after the `=`:
+
+ ```ini hl_lines="5 6"
+ [chuniio]
+ ; Uncomment both of these if you have custom chuniio implementation comprised of two DLLs.
+ ; x86 chuniio to path32, x64 to path64. Both are necessary.
+ ;(1)!
+ path32=controller_x86.dll
+ path64=controller_x64.dll
+ ```
+
+ 1. Note that there is no leading semicolon.
+
+### Keyboard
+
+!!! tip ""
+
+ Keyboard is the default input method, and while not recommended for playing the game,
+ it is useful for testing purposes.
+
+ The default layout uses `SDFGHJKL` for slider input, and `Space Bar` for the AIRs.
+
+ If you wish to change the default keybinds, an explanation on how to set these is included
+ above the `[io3]` section in your `segatools.ini`.
+
+### Brokenithm
+
+!!! tip ""
+
+ Brokenithm allows you to use a mobile device as a CHUNITHM controller. It uses the bottom
+ half of the screen as the ground slider, and sliding into the upper half activates the air
+ sensors.
+
+#### Android
+
+!!! warning
+
+ Your computer and your Android device must be on the same local network.
+
+!!! tip ""
+
+ - Download the latest version of [Brokenithm-Android](https://github.com/tindy2013/Brokenithm-Android/releases/latest)
+ and install it on your Android device.
+ - Download the latest version of [Brokenithm-Android-Server](https://github.com/tindy2013/Brokenithm-Android-Server/releases/latest)
+ and extract **only `brokenithm_server.exe`** to your `App\bin\` folder.
+ - Download the latest version of [Brokenithm-Evolved IO DLLs](https://gitea.tendokyu.moe/Dniel97/Brokenithm-Evolved/releases) and extract the DLL files to your `App\bin\` folder.
+ - Edit your `App\bin\segatools.ini` to reference the extracted DLLs:
+
+ ```ini hl_lines="2"
+ [aimeio]
+ path=aime_brokenithm.dll
+ ```
+
+ ```ini hl_lines="2 3"
+ [chuniio]
+ path32=brokenithm_x86.dll
+ path64=brokenithm_x64.dll
+ ```
+
+ - Run `brokenithm_server.exe`. A command prompt window should open, saying that
+ it is waiting for a device on port 52468.
+ - Open the Brokenithm app on your Android device. Enter your computer's IP address
+ in the Address box on the top right, then tap Start.
+ - Run the game as normal.
+
+??? info "Getting your computer's IP address"
+
+ Open **Settings** -> **Network and Internet** and select **Properties**. Scroll down to
+ the bottom and check the address under the **IPv4 address** field:
+
+ 
+
+ That is your computer's IP address.
+
+??? info "Automatically launching the Brokenithm server when starting the game"
+
+ **This will only work if you extracted `brokenithm_server.exe` to `App\bin\` as previously instructed.**
+
+ You can edit the launch script to launch the Brokenithm server when starting the game.
+ Edit `App\bin\launch.bat` to add a line above the existing commands:
+
+ ```batch hl_lines="5"
+ @echo off
+
+ pushd %~dp0
+
+ start /min brokenithm_server
+ start /min inject_x64 -d -k chusanhook_x64.dll amdaemon.exe -c config_common.json config_server.json config_client.json config_cvt.json config_sp.json config_hook.json
+ inject_x86 -d -k chusanhook_x86.dll chusanApp.exe
+ taskkill /f /im amdaemon.exe > nul 2>&1
+
+ echo.
+ echo Game processes have terminated
+ pause
+ ```
+
+??? info "Improving latency"
+
+ You can improve latency by running Brokenithm with your Android device tethered to
+ your computer. However, this requires a little extra setup:
+
+ - Connect your Android device to your computer with a USB cable.
+ - If you haven't enabled Developer options on your device, do it by navigating to
+ the "About" page in your phone's settings, then tap "Build number" seven times.
+ This varies by device, so if unsure, look up the instructions for your specific
+ one.
+ - Navigate to Developer options and enable USB debugging.
+ - On your computer, download and extract [Android SDK Platform Tools](https://dl.google.com/android/repository/platform-tools-latest-windows.zip)
+ to your `App\bin\` folder.
+ - Navigate to the `App\bin\platform-tools` folder in File Explorer, click on the
+ address bar, type `cmd`, and hit Enter to open a command prompt.
+ - In the command prompt, type the following command:
+
+ ```batch
+ adb reverse tcp:52468 tcp:52468
+ ```
+
+ - Start brokenithm_server in TCP mode with the -T command line flag, `brokenithm_server.exe -T`.
+ - On your Android device, open Brokenithm, and change the address to `0.0.0.0`.
+ - If the text box to the left of the "SETTINGS" button say "UDP", tap on it
+ once to switch to "TCP" mode.
+ - Tap on "START", and you will now be connected via the USB cable.
+ - You can now start the game as normal.
+
+ The next time you play the game, you only need to run the `adb reverse ...` command
+ again. To do this automatically when the game starts, add a line to the `launch.bat`
+ script **before** the `brokenithm_server` line:
+
+ ```batch hl_lines="5 6"
+ @echo off
+
+ pushd %~dp0
+
+ start /min platform-tools\adb reverse tcp:52468 tcp:52468
+ start /min brokenithm_server -T
+ start /min inject_x64 -d -k chusanhook_x64.dll amdaemon.exe -c config_common.json config_server.json config_client.json config_cvt.json config_sp.json config_hook.json
+ inject_x86 -d -k chusanhook_x86.dll chusanApp.exe
+ taskkill /f /im amdaemon.exe > nul 2>&1
+
+ echo.
+ echo Game processes have terminated
+ pause
+ ```
+
+#### iOS/iPadOS
+
+!!! tip ""
+
+ - Install Brokenithm on your iOS/iPadOS device by joining the [Brokenithm TestFlight](https://testflight.apple.com/join/U6kwvETm) ^^(iOS 18 only)^^.
+ - If your iOS/iPadOS device doesn't have iOS 18, you will need to sideload a different [IPA](https://redive.estertion.win/ipas/Brokenithm-iOS-build-10.ipa) with [Sideloadly](https://sideloadly.io/).
+ - If you have iTunes and/or iCloud installed from the Microsoft Store on your computer, **uninstall it.**
+ - Install the **non-Microsoft Store** version of iTunes from the [website](https://www.apple.com/itunes/download/win64).
+ - Download the latest version of [Brokenithm-Evolved-iOS server](https://redive.estertion.win/ipas/Brokenithm/Brokenithm-Evolved-iOS-v0.3.7z)
+ and extract it to `App\bin\Brokenithm-Server`.
+ - Download the latest version of [Brokenithm-Evolved IO DLLs](https://gitea.tendokyu.moe/Dniel97/Brokenithm-Evolved/releases) and extract the DLL files to your `App\bin\` folder.
+ - Edit your `App\bin\segatools.ini` to reference the extracted DLLs:
+
+ ```ini hl_lines="2"
+ [aimeio]
+ path=aime_brokenithm.dll
+ ```
+
+ ```ini hl_lines="2 3"
+ [chuniio]
+ path32=brokenithm_x86.dll
+ path64=brokenithm_x64.dll
+ ```
+
+ - Run `App\bin\Brokenithm-Server\Brokenithm-Evolved-iOS.exe`. A command prompt window
+ should open, saying that it is waiting for a device.
+ - On your iOS/iPadOS device, open Brokenithm, and connect it to your computer with a
+ USB cable.
+ - Run the game as normal.
+
+??? info "Automatically launching the Brokenithm server when starting the game"
+
+ **This will only work if you extracted the server to `App\bin\Brokenithm-Server` as previously instructed.**
+
+ You can edit the launch script to launch the Brokenithm server when starting the game.
+ Edit `App\bin\launch.bat` to add a line above the existing commands:
+
+ ```batch hl_lines="5"
+ @echo off
+
+ pushd %~dp0
+
+ start /min Brokenithm-Server\Brokenithm-Evolved-iOS.exe
+ start /min inject_x64 -d -k chusanhook_x64.dll amdaemon.exe -c config_common.json config_server.json config_client.json config_cvt.json config_sp.json config_hook.json
+ inject_x86 -d -k chusanhook_x86.dll chusanApp.exe
+ taskkill /f /im amdaemon.exe > nul 2>&1
+
+ echo.
+ echo Game processes have terminated
+ pause
+ ```
+
+### TASOLLER
+
+!!! warning
+
+ This guide only covers TASOLLERs running the v2.0 touch firmware. If you've purchased the
+ controller after January 2022, the update should have already been applied.
+
+ If you've purchased the controller before then, you will need to update the touch
+ firmware by following the instructions on [DJ-DAO's support page](https://www.dj-dao.com/en/support/11.html).
+
+!!! tip ""
+
+ - Install the [custom IO4 firmware](https://gitea.tendokyu.moe/tasoller/host-aprom/releases) to your controller.
+ - Follow the `segatools.ini` config on the [gitea page](https://gitea.tendokyu.moe/tasoller/host-aprom).
+ - Connect the controller to your computer, and then start the game.
+
+??? tip "Legacy"
+
+ - Backup TASOLLER setup if IO4 cfw is not working.
+ - Install the [custom Host and LED firmware](https://pixeldrain.com/u/DajSPEoa) to your controller.
+ Instructions on how to do so is provided in the linked archive.
+ - Download TASOLLER IO DLLs and extract to your `App\bin` folder.
+ - [chuniio-rs](https://gitea.tendokyu.moe/beerpsi/chuniio-rs/releases) (download `chusan.zip`)
+ - Edit your `App\bin\segatools.ini` to reference the extracted DLLs:
+
+ ```ini
+ [chuniio]
+ path32=chuniio_tasoller_v2_x86.dll
+ path64=chuniio_tasoller_v2_x64.dll
+ ```
+
+ - Connect the controller to your computer, and then start the game.
+
+### TASOLLER PLUS
+
+!!! tip ""
+
+ - Switch your TASOLLER PLUS to WINUSB mode. You can do so in TASOLLER Options
+ found on the djdao [support page](https://www.dj-dao.com/en/support/22.html).
+ - Download TASOLLER PLUS IO DLLs and extract to your `App\bin` folder.
+ - [chuniio-rs](https://gitea.tendokyu.moe/beerpsi/chuniio-rs/releases) (download `chusan.zip`)
+ - Edit your `App\bin\segatools.ini` to reference the extracted DLLs:
+
+ ```ini
+ [chuniio]
+ path32=chuniio_tasoller_plus_x86.dll
+ path64=chuniio_tasoller_plus_x64.dll
+ ```
+
+ - Connect the controller to your computer, and then start the game.
+
+### YubiDeck
+
+!!! tip ""
+
+ - Switch your YubiDeck to HID output mode. Instructions on how to do so are provided
+ in the [YubiDeck manual](https://drive.google.com/file/d/11KVlKbg3zGCRwI7R-30t2IJc6OQwDEgo/view).
+ - Download the latest version of [YubiDeck IO DLLs](https://gitea.tendokyu.moe/beerpsi/chuniio-yubideck/releases)
+ and extract it to your `App\bin` folder.
+ - Edit your `App\bin\segatools.ini` to reference the extracted DLLs:
+
+ ```ini
+ [chuniio]
+ path32=chuniio_yubideck_chusan.dll
+ path64=chuniio_yubideck_amdaemon.dll
+ ```
+
+ - Optionally, reference the included AimeIO DLL to use the controller's
+ built-in card reader:
+
+ ```ini
+ [aimeio]
+ path=aimeio_yubideck.dll
+ ```
+
+ - Connect the controller to your computer, and then start the game.
+
+### Laverita 3
+
+!!! tip ""
+
+ - Switch your Laverita to IO mode. You can do so in ConfigApp
+ found in the yuancon [discord](https://discord.gg/4ncuRrq).
+ - Change the COM port of your controller. You can do so in
+ Device manager by looking for `USB Serial Device` you may need to unplug and replug your controller to properly idetify which one is the Laverita.
+ - Double click on it
+ - Go to Port Settings
+ - Click on Advanced
+ - From the dropdown select COM1
+ - Restart to ensure changes took effect and saved
+ - Edit your `App\bin\segatools.ini` to disable io emulation and set led:
+
+ ```ini
+ [led]
+ ; Output billboard LED strip data to a named pipe called "\\.\pipe\chuni_led"
+ cabLedOutputPipe=0
+ ; Output billboard LED strip data to serial
+ cabLedOutputSerial=1
+
+ ; Output slider LED data to the named pipe
+ controllerLedOutputPipe=0
+ ; Output slider LED data to the serial port
+ controllerLedOutputSerial=1
+ ; Use the OpeNITHM protocol for serial LED output
+ controllerLedOutputOpeNITHM=0
+
+ ; Serial port to send data to if using serial output. Default is COM5.
+ serialPort=COM1
+ ; Baud rate for serial data (set to 115200 if using OpeNITHM)
+ serialBaud=9600
+
+ [slider]
+ ; Enable slider emulation. If you have real AC slider, set this to 0.
+ ; Slider serial port must be COM1.
+ enable=0
+
+ [io4]
+ enable=0
+ ```
+
+ - Then start the game.
+
+??? tip "Legacy"
+
+ - Backup Laverita 3 setup if IO4 mode is not working.
+ - Switch your Laverita to HID mode. You can do so in ConfigApp
+ - Download Laverita IO DLLs and extract to your `App\bin` folder.
+ - [chuniio-rs](https://gitea.tendokyu.moe/beerpsi/chuniio-rs/releases) (download `chusan.zip`)
+ - Edit your `App\bin\segatools.ini` to reference the extracted DLLs:
+
+ ```ini
+ [chuniio]
+ path32=chuniio_laverita_v3_x86.dll
+ path64=chuniio_laverita_v3_x64.dll
+ ```
+
+ - Connect the controller to your computer, and then start the game.
+
+### Arcade hardware and other controllers
+
+!!! tip ""
+
+ If you're interested in using a cabinet slider and air sensors, or possibly even
+ making your own controller, the [Cons&Stuff website](https://consandstuff.github.io/)
+ and Discord community is a great place to start!
diff --git a/docs/games/sega/chunithm/common/chusan/setup.md b/docs/games/sega/chunithm/common/chusan/setup.md
new file mode 100644
index 0000000..b45a215
--- /dev/null
+++ b/docs/games/sega/chunithm/common/chusan/setup.md
@@ -0,0 +1,184 @@
+# Game Setup
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+--8<-- "docs/snippets/sega/common/data_old.md"
+
+## Preparing data
+
+--8<-- "docs/snippets/sega/common/data_driveletter.md"
+
+--8<-- "docs/snippets/common/data_readonly.md"
+
+--8<-- "docs/snippets/sega/common/data_preparation.md"
+
+ ```
+ 📂bin
+ 📂data
+ 📂firm
+ 📂license
+ 📄firewall.cfg
+ ▶️game.bat
+ ▶️pwGetHwinfo.exe
+ 📝pxGetHwInfo.ini
+ 📄system_config.json
+ ```
+
+--8<-- "docs/snippets/sega/common/data_bad.md"
+
+## Updating data
+
+--8<-- "docs/snippets/sega/common/data_updating.md"
+
+## Installing option data
+
+--8<-- "docs/snippets/sega/chunithm/data_options.md"
+
+## Installing unprotected executables
+
+!!! tip ""
+
+ CHUNITHM executables are protected and will not run on a regular computer.
+
+ Obtain unprotected (also called "unpacked" or "decrypted" by the community) copies of `chusanApp.exe` and `amdaemon.exe` for your game version.
+
+ - Copy `chusanApp.exe` and `amdaemon.exe` to data's `App\bin` folder
+ - Agree to overwrite when asked
+
+## Installing ICFs
+
+--8<-- "docs/snippets/sega/common/data_icfs.md"
+
+## Patching the game
+
+--8<-- "docs/snippets/sega/common/patching.md"
+
+| Patch | Recommendation | Description |
+|------------------------------|----------------|-------------|
+| Force shared audio mode | Either | Force the game to use shared mode audio output, letting you listen to other audio sources while the game is running **at the cost of audio latency.**
+| Force 2 channel audio output | Either | Try enabling this patch if you don't get audio output at all. |
+| Disable song select timer | Either | Disables the song select timer. |
+| No encryption | ON | Disable encrypting network requests. **Required if you plan to run a local server.** |
+| No TLS | ON | Disable checking if the server is `HTTPS` or not. **Required if you plan to run a local server.** |
+| Bypass 1080p monitor check | Either | Disable checking if the monitor is 1080p when enabling 120FPS. Enable if you cannot set your monitor to 1080p. |
+| Bypass 120 Hz monitor check | Either | Disable checking if the monitor is **exactly 120 Hz** when enabling 120FPS. Enable if you cannot set your monitor to 120 Hz. |
+
+## Installing segatools
+
+--8<-- "docs/snippets/sega/common/segatools_install.md"
+ - Find `chusan.zip` and extract it to your data's `App\bin` folder
+
+ You should now have these files added to your `App\bin` directory:
+
+ ```
+ 📂DEVICE
+ ⚙️chusanhook_x64.dll
+ ⚙️chusanhook_x86.dll
+ 📄config_hook.json
+ ▶️inject_x64.exe
+ ▶️inject_x86.exe
+ 📝segatools.ini
+ ▶️launch.bat
+ ```
+
+## Configuring segatools
+
+--8<-- "docs/snippets/sega/common/segatools_preamble_bin.md"
+
+=== "[vfs]"
+
+--8<-- "docs/snippets/sega/common/segatools_relativepaths.md"
+
+--8<-- "docs/snippets/sega/common/segatools_vfs.md"
+
+=== "[system]"
+
+ !!! tip ""
+
+ - If you have a 120 Hz monitor, set `dipsw2` and `dipsw3` to 0:
+
+ ```ini
+ [system]
+ dipsw2=0
+ dipsw3=0
+ ```
+
+ - If you have a 60 Hz monitor, set `dipsw2` and `dipsw3` to 1:
+
+ ```ini
+ [system]
+ dipsw2=1
+ dipsw3=1
+ ```
+
+=== "[gfx]"
+
+--8<-- "docs/snippets/sega/chunithm/segatools_gfx.md"
+
+## Configuring audio
+
+--8<-- "docs/snippets/common/audio_48khz.md"
+
+## Connecting to a network
+
+--8<-- "docs/snippets/sega/common/network_preamble.md"
+
+--8<-- "docs/snippets/sega/common/network_remote.md"
+
+--8<-- "docs/snippets/sega/common/network_local.md"
+
+## Installing VCRedist & DirectX
+
+--8<-- "docs/snippets/common/setup_vcredist_directx.md"
+
+## Before playing
+
+--8<-- "docs/snippets/common/before_playing.md"
+
+## First launch
+
+--8<-- "docs/snippets/sega/common/service_jp_googlelens.md"
+
+!!! tip ""
+
+ If you've followed all instructions correctly, you're now finally ready to launch the game!
+
+ Start the game by running `App\bin\launch.bat`. Let the game load until it reaches the screen below.
+
+ 
+
+ Press your `Test` button (default `F1`) to enter the service menu. Use the `Service` button
+ (default `F2`) to navigate the menu, and `Test` button to select an option.
+
+ Navigate to **ゲーム設定** (`GAME ASSIGNMENTS`, the fourth option).
+
+ 
+
+ Select **グループ内基準機設定** (`SET STANDARD IN GROUP`, the second option)
+ and toggle this setting to **基準機** (`STANDARD`).
+
+ 
+
+ Select **終了** (`EXIT`, the last option) to exit to the main service menu.
+
+ Navigate to **閉店設定** (`CLOSE SETTING`, the tenth option).
+
+ 
+
+ Navigate to **時** (`HOUR`, the second option) and use the `Service` button
+ to toggle the setting until it says **全時刻** (`ALL TIME`).
+
+ 
+
+ Select **終了** (`EXIT`, the last option) to exit to the main service menu, then select **終了**
+ (also the last option) in the main menu to exit the service menu.
+
+ If you're stuck at the `Waiting for Distribution Server` screen below, close the game and relaunch.
+
+ 
+
+--8<-- "docs/snippets/sega/common/success.md"
+
+## Help
+
+--8<-- "docs/snippets/common/help.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/common/chusan/troubleshooting.md b/docs/games/sega/chunithm/common/chusan/troubleshooting.md
new file mode 100644
index 0000000..d9c1283
--- /dev/null
+++ b/docs/games/sega/chunithm/common/chusan/troubleshooting.md
@@ -0,0 +1,117 @@
+# Troubleshooting
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+### My game crashes on launch!
+
+!!! tip ""
+
+ Could be due to **many** things, the most common of which are:
+
+ - `amdaemon` crashing in the background. Make sure that the `config_*.json` files
+ have valid syntax, your ICF files are correct.
+ - Using the incorrect dipswitch settings for your refresh rate (e.g. `dipsw3=0` on
+ a 60 Hz screen). Refer to the game setup guide to fix it.
+ - Enabling 120FPS on a monitor that is not **exactly 120 Hz** or **exactly 1080p**.
+ If you cannot set your monitor's refresh rate to 120 Hz, apply the "Bypass 120 Hz
+ monitor check"/"Bypass 1080p monitor check" on a CHUNITHM web patcher (see [Resources](/resources.md#web-patchers)).
+
+??? info "Capturing logs from `amdaemon` for troubleshooting"
+
+ To assist with troubleshooting, a script can be used to capture logs from `amdaemon`. Create a file named
+ `amdaemontest.bat` in `App\bin`, then paste the code block below into the file.
+
+ ```batch
+ @echo off
+ cls
+ echo Attempting to run AM Daemon ...
+ echo Window should close after 30 seconds
+ echo Log will be generated at amdaemontest.txt
+ call :sub >amdaemontest.txt
+ exit /b
+
+ :sub
+ pushd %~dp0
+ start /b "AM Daemon" /min inject_x64 -d -k chusanhook_x64.dll amdaemon.exe -c config_common.json config_server.json config_client.json config_cvt.json config_sp.json config_hook.json
+ ping 127.0.0.1 -n 31 > nul && taskkill /im amdaemon.exe
+ ```
+
+ Double-click it to run. The script should run for 30 seconds, and you will get a file
+ named `amdaemontest.txt` in `App\bin`, which you can send to help people troubleshoot your issue.
+
+### My game takes a long time to boot!
+
+!!! tip ""
+
+ CHUNITHM game files consist of thousands of small XML files, which Windows Defender
+ takes a long time to scan through. Add your game folder to the Windows Defender
+ exclusion list.
+
+!!! danger
+
+ Doing this will prevent Windows Defender from scanning your game folder for viruses.
+ Only do this if you trust the source of the data.
+
+### My game is running too slow/fast
+
+!!! tip ""
+
+ The game could be running under or over its required refresh rate.
+
+ - Make sure V-Sync isn't disabled in your graphics settings (called "Vertical sync"
+ in NVIDIA Control Panel and "Wait for Vertical Refresh" in AMD Control Panel.)
+ - Make sure your monitor's refresh rate is set to 60 Hz or 120 Hz.
+
+ It could also be that your computer's performance isn't good enough to keep
+ a steady framerate.
+
+### My game is stuttering
+
+!!! tip ""
+
+ For NVIDIA users, create an override for `chusanApp.exe` in NVIDIA Control Panel
+ and change "Power management mode" to "**Prefer maximum performance**".
+
+### My game crashes when I tab out of fullscreen!
+
+!!! tip ""
+
+ As the game is intended to run on arcade hardware, it doesn't like being minimized.
+
+ One workaround for this is to use DXVK. Download the latest version from [releases](https://github.com/doitsujin/dxvk/releases/latest).
+ This will be a `dxvk-x.y.z.tar.gz` file, which you can open using [7zip](https://www.7-zip.org/).
+ Navigate to the `x32` folder, and copy the `d3d9.dll` file to your game's `App\bin` folder, agreeing
+ to overwrite when asked.
+
+ You should now be able to tab out of fullscreen without crashing the game.
+
+!!! warning
+
+ The game will not ignore inputs when out of focus.
+
+ This means any controller inputs will still be accepted, so try not to lean onto
+ your slider whilst tabbed out!
+
+ This also means that you can accidentally enter the service menu by hitting your
+ `Test` key even if the game is minimised. If you were in the middle of a credit,
+ **your scores will be lost.**
+
+### When I run the game all other audio is gone!
+
+!!! tip ""
+
+ CHUNITHM uses [WASAPI exclusive mode](https://docs.microsoft.com/en-us/windows/win32/coreaudio/exclusive-mode-streams)
+ for audio to get better latency.
+
+ You can apply the "Shared Audio" patch on a CHUNITHM web patcher (see [Resources](/resources.md#web-patchers))
+ to hear audio outside of the game at the cost of audio latency.
+
+### Cabinet-to-Cabinet(c2c) Fixes
+
+!!! tip ""
+
+ c2c can have many problems but you can fix most of them by applying the "Patch for head-to-head play" and disabling "Set all timers to 999" on a CHUNITHM web patcher (see [Resources](/resources.md#web-patchers)).
+
+ If the above does not work then please ensure both machines have the exact same data and can communicate with each other if they cannot then you can try disabling firewalls or changing the c2c group.
+
+ If clicking the c2c button does nothing, you can fix it by resetting the network settings in Windows.
diff --git a/docs/games/sega/chunithm/crystal/c2c.md b/docs/games/sega/chunithm/crystal/c2c.md
new file mode 100644
index 0000000..0a748b0
--- /dev/null
+++ b/docs/games/sega/chunithm/crystal/c2c.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chuni/c2c.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/crystal/controllers.md b/docs/games/sega/chunithm/crystal/controllers.md
new file mode 100644
index 0000000..46997ae
--- /dev/null
+++ b/docs/games/sega/chunithm/crystal/controllers.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chuni/controllers.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/crystal/setup.md b/docs/games/sega/chunithm/crystal/setup.md
new file mode 100644
index 0000000..5d58cec
--- /dev/null
+++ b/docs/games/sega/chunithm/crystal/setup.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chuni/setup_belowcrystal.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/crystal/troubleshooting.md b/docs/games/sega/chunithm/crystal/troubleshooting.md
new file mode 100644
index 0000000..95f6e2e
--- /dev/null
+++ b/docs/games/sega/chunithm/crystal/troubleshooting.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chuni/troubleshooting.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/crystalplus/c2c.md b/docs/games/sega/chunithm/crystalplus/c2c.md
new file mode 100644
index 0000000..047b623
--- /dev/null
+++ b/docs/games/sega/chunithm/crystalplus/c2c.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chuni/c2c.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/crystalplus/controllers.md b/docs/games/sega/chunithm/crystalplus/controllers.md
new file mode 100644
index 0000000..313b2be
--- /dev/null
+++ b/docs/games/sega/chunithm/crystalplus/controllers.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chuni/controllers.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/crystalplus/setup.md b/docs/games/sega/chunithm/crystalplus/setup.md
new file mode 100644
index 0000000..3ff6e2d
--- /dev/null
+++ b/docs/games/sega/chunithm/crystalplus/setup.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chuni/setup.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/crystalplus/troubleshooting.md b/docs/games/sega/chunithm/crystalplus/troubleshooting.md
new file mode 100644
index 0000000..767b590
--- /dev/null
+++ b/docs/games/sega/chunithm/crystalplus/troubleshooting.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chuni/troubleshooting.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/luminous/c2c.md b/docs/games/sega/chunithm/luminous/c2c.md
new file mode 100644
index 0000000..53a9121
--- /dev/null
+++ b/docs/games/sega/chunithm/luminous/c2c.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chusan/c2c.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/luminous/controllers.md b/docs/games/sega/chunithm/luminous/controllers.md
new file mode 100644
index 0000000..7008cf3
--- /dev/null
+++ b/docs/games/sega/chunithm/luminous/controllers.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chusan/controllers.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/luminous/setup.md b/docs/games/sega/chunithm/luminous/setup.md
new file mode 100644
index 0000000..d55a289
--- /dev/null
+++ b/docs/games/sega/chunithm/luminous/setup.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chusan/setup.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/luminous/troubleshooting.md b/docs/games/sega/chunithm/luminous/troubleshooting.md
new file mode 100644
index 0000000..e9b4756
--- /dev/null
+++ b/docs/games/sega/chunithm/luminous/troubleshooting.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chusan/troubleshooting.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/luminousplus/c2c.md b/docs/games/sega/chunithm/luminousplus/c2c.md
new file mode 100644
index 0000000..a24a074
--- /dev/null
+++ b/docs/games/sega/chunithm/luminousplus/c2c.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chusan/c2c.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/luminousplus/controllers.md b/docs/games/sega/chunithm/luminousplus/controllers.md
new file mode 100644
index 0000000..f6add40
--- /dev/null
+++ b/docs/games/sega/chunithm/luminousplus/controllers.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chusan/controllers.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/luminousplus/setup.md b/docs/games/sega/chunithm/luminousplus/setup.md
new file mode 100644
index 0000000..eb5cff4
--- /dev/null
+++ b/docs/games/sega/chunithm/luminousplus/setup.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chusan/setup.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/luminousplus/troubleshooting.md b/docs/games/sega/chunithm/luminousplus/troubleshooting.md
new file mode 100644
index 0000000..85f8236
--- /dev/null
+++ b/docs/games/sega/chunithm/luminousplus/troubleshooting.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chusan/troubleshooting.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/new/c2c.md b/docs/games/sega/chunithm/new/c2c.md
new file mode 100644
index 0000000..6b17963
--- /dev/null
+++ b/docs/games/sega/chunithm/new/c2c.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chusan/c2c.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/new/controllers.md b/docs/games/sega/chunithm/new/controllers.md
new file mode 100644
index 0000000..60679d8
--- /dev/null
+++ b/docs/games/sega/chunithm/new/controllers.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chusan/controllers.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/new/setup.md b/docs/games/sega/chunithm/new/setup.md
new file mode 100644
index 0000000..ea0a88d
--- /dev/null
+++ b/docs/games/sega/chunithm/new/setup.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chusan/setup.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/new/troubleshooting.md b/docs/games/sega/chunithm/new/troubleshooting.md
new file mode 100644
index 0000000..e67e47b
--- /dev/null
+++ b/docs/games/sega/chunithm/new/troubleshooting.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chusan/troubleshooting.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/newplus/c2c.md b/docs/games/sega/chunithm/newplus/c2c.md
new file mode 100644
index 0000000..d3418b7
--- /dev/null
+++ b/docs/games/sega/chunithm/newplus/c2c.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chusan/c2c.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/newplus/controllers.md b/docs/games/sega/chunithm/newplus/controllers.md
new file mode 100644
index 0000000..a308d20
--- /dev/null
+++ b/docs/games/sega/chunithm/newplus/controllers.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chusan/controllers.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/newplus/setup.md b/docs/games/sega/chunithm/newplus/setup.md
new file mode 100644
index 0000000..9a0d6c4
--- /dev/null
+++ b/docs/games/sega/chunithm/newplus/setup.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chusan/setup.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/newplus/troubleshooting.md b/docs/games/sega/chunithm/newplus/troubleshooting.md
new file mode 100644
index 0000000..492f50d
--- /dev/null
+++ b/docs/games/sega/chunithm/newplus/troubleshooting.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chusan/troubleshooting.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/paradise/c2c.md b/docs/games/sega/chunithm/paradise/c2c.md
new file mode 100644
index 0000000..b5592fc
--- /dev/null
+++ b/docs/games/sega/chunithm/paradise/c2c.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chuni/c2c.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/paradise/controllers.md b/docs/games/sega/chunithm/paradise/controllers.md
new file mode 100644
index 0000000..ad50168
--- /dev/null
+++ b/docs/games/sega/chunithm/paradise/controllers.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chuni/controllers.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/paradise/setup.md b/docs/games/sega/chunithm/paradise/setup.md
new file mode 100644
index 0000000..cc1598f
--- /dev/null
+++ b/docs/games/sega/chunithm/paradise/setup.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chuni/setup.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/paradise/troubleshooting.md b/docs/games/sega/chunithm/paradise/troubleshooting.md
new file mode 100644
index 0000000..e1f570a
--- /dev/null
+++ b/docs/games/sega/chunithm/paradise/troubleshooting.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chuni/troubleshooting.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/paradiselost/c2c.md b/docs/games/sega/chunithm/paradiselost/c2c.md
new file mode 100644
index 0000000..475d2c0
--- /dev/null
+++ b/docs/games/sega/chunithm/paradiselost/c2c.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chuni/c2c.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/paradiselost/controllers.md b/docs/games/sega/chunithm/paradiselost/controllers.md
new file mode 100644
index 0000000..7d826d2
--- /dev/null
+++ b/docs/games/sega/chunithm/paradiselost/controllers.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chuni/controllers.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/paradiselost/setup.md b/docs/games/sega/chunithm/paradiselost/setup.md
new file mode 100644
index 0000000..27ec028
--- /dev/null
+++ b/docs/games/sega/chunithm/paradiselost/setup.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chuni/setup.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/paradiselost/troubleshooting.md b/docs/games/sega/chunithm/paradiselost/troubleshooting.md
new file mode 100644
index 0000000..2919df9
--- /dev/null
+++ b/docs/games/sega/chunithm/paradiselost/troubleshooting.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chuni/troubleshooting.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/plus/c2c.md b/docs/games/sega/chunithm/plus/c2c.md
new file mode 100644
index 0000000..614c322
--- /dev/null
+++ b/docs/games/sega/chunithm/plus/c2c.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chuni/c2c.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/plus/controllers.md b/docs/games/sega/chunithm/plus/controllers.md
new file mode 100644
index 0000000..34a0182
--- /dev/null
+++ b/docs/games/sega/chunithm/plus/controllers.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chuni/controllers.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/plus/setup.md b/docs/games/sega/chunithm/plus/setup.md
new file mode 100644
index 0000000..8fc7f97
--- /dev/null
+++ b/docs/games/sega/chunithm/plus/setup.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chuni/setup_belowcrystal.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/plus/troubleshooting.md b/docs/games/sega/chunithm/plus/troubleshooting.md
new file mode 100644
index 0000000..da4eb8d
--- /dev/null
+++ b/docs/games/sega/chunithm/plus/troubleshooting.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chuni/troubleshooting.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/star/c2c.md b/docs/games/sega/chunithm/star/c2c.md
new file mode 100644
index 0000000..6e0b8c0
--- /dev/null
+++ b/docs/games/sega/chunithm/star/c2c.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chuni/c2c.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/star/controllers.md b/docs/games/sega/chunithm/star/controllers.md
new file mode 100644
index 0000000..3f8a7ac
--- /dev/null
+++ b/docs/games/sega/chunithm/star/controllers.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chuni/controllers.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/star/setup.md b/docs/games/sega/chunithm/star/setup.md
new file mode 100644
index 0000000..cf1955e
--- /dev/null
+++ b/docs/games/sega/chunithm/star/setup.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chuni/setup_belowcrystal.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/star/troubleshooting.md b/docs/games/sega/chunithm/star/troubleshooting.md
new file mode 100644
index 0000000..d125510
--- /dev/null
+++ b/docs/games/sega/chunithm/star/troubleshooting.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chuni/troubleshooting.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/starplus/c2c.md b/docs/games/sega/chunithm/starplus/c2c.md
new file mode 100644
index 0000000..d2123bf
--- /dev/null
+++ b/docs/games/sega/chunithm/starplus/c2c.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chuni/c2c.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/starplus/controllers.md b/docs/games/sega/chunithm/starplus/controllers.md
new file mode 100644
index 0000000..811ee15
--- /dev/null
+++ b/docs/games/sega/chunithm/starplus/controllers.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chuni/controllers.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/starplus/setup.md b/docs/games/sega/chunithm/starplus/setup.md
new file mode 100644
index 0000000..72d843b
--- /dev/null
+++ b/docs/games/sega/chunithm/starplus/setup.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chuni/setup_belowcrystal.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/starplus/troubleshooting.md b/docs/games/sega/chunithm/starplus/troubleshooting.md
new file mode 100644
index 0000000..0f84bf9
--- /dev/null
+++ b/docs/games/sega/chunithm/starplus/troubleshooting.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chuni/troubleshooting.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/sun/c2c.md b/docs/games/sega/chunithm/sun/c2c.md
new file mode 100644
index 0000000..211a09c
--- /dev/null
+++ b/docs/games/sega/chunithm/sun/c2c.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chusan/c2c.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/sun/controllers.md b/docs/games/sega/chunithm/sun/controllers.md
new file mode 100644
index 0000000..7e784e5
--- /dev/null
+++ b/docs/games/sega/chunithm/sun/controllers.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chusan/controllers.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/sun/setup.md b/docs/games/sega/chunithm/sun/setup.md
new file mode 100644
index 0000000..f18d0f5
--- /dev/null
+++ b/docs/games/sega/chunithm/sun/setup.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chusan/setup.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/sun/troubleshooting.md b/docs/games/sega/chunithm/sun/troubleshooting.md
new file mode 100644
index 0000000..f184bd0
--- /dev/null
+++ b/docs/games/sega/chunithm/sun/troubleshooting.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chusan/troubleshooting.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/sunplus/c2c.md b/docs/games/sega/chunithm/sunplus/c2c.md
new file mode 100644
index 0000000..592c593
--- /dev/null
+++ b/docs/games/sega/chunithm/sunplus/c2c.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chusan/c2c.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/sunplus/controllers.md b/docs/games/sega/chunithm/sunplus/controllers.md
new file mode 100644
index 0000000..fefd58a
--- /dev/null
+++ b/docs/games/sega/chunithm/sunplus/controllers.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chusan/controllers.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/sunplus/setup.md b/docs/games/sega/chunithm/sunplus/setup.md
new file mode 100644
index 0000000..e0b25c7
--- /dev/null
+++ b/docs/games/sega/chunithm/sunplus/setup.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chusan/setup.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/sunplus/troubleshooting.md b/docs/games/sega/chunithm/sunplus/troubleshooting.md
new file mode 100644
index 0000000..b5e6104
--- /dev/null
+++ b/docs/games/sega/chunithm/sunplus/troubleshooting.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chusan/troubleshooting.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/verse/c2c.md b/docs/games/sega/chunithm/verse/c2c.md
new file mode 100644
index 0000000..2f413cd
--- /dev/null
+++ b/docs/games/sega/chunithm/verse/c2c.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chusan/c2c.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/verse/controllers.md b/docs/games/sega/chunithm/verse/controllers.md
new file mode 100644
index 0000000..bd0361f
--- /dev/null
+++ b/docs/games/sega/chunithm/verse/controllers.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chusan/controllers.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/verse/setup.md b/docs/games/sega/chunithm/verse/setup.md
new file mode 100644
index 0000000..ee5e9e5
--- /dev/null
+++ b/docs/games/sega/chunithm/verse/setup.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chusan/setup.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/verse/troubleshooting.md b/docs/games/sega/chunithm/verse/troubleshooting.md
new file mode 100644
index 0000000..4c38041
--- /dev/null
+++ b/docs/games/sega/chunithm/verse/troubleshooting.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/chunithm/common/chusan/troubleshooting.md"
\ No newline at end of file
diff --git a/docs/games/sega/chunithm/x-verse-x/c2c.md b/docs/games/sega/chunithm/x-verse-x/c2c.md
new file mode 100644
index 0000000..38cf89c
--- /dev/null
+++ b/docs/games/sega/chunithm/x-verse-x/c2c.md
@@ -0,0 +1,3 @@
+
+--8<-- "docs/games/sega/chunithm/common/chusan/c2c.md"
+
diff --git a/docs/games/sega/chunithm/x-verse-x/controllers.md b/docs/games/sega/chunithm/x-verse-x/controllers.md
new file mode 100644
index 0000000..ef6e878
--- /dev/null
+++ b/docs/games/sega/chunithm/x-verse-x/controllers.md
@@ -0,0 +1,3 @@
+
+--8<-- "docs/games/sega/chunithm/common/chusan/controllers.md"
+
diff --git a/docs/games/sega/chunithm/x-verse-x/setup.md b/docs/games/sega/chunithm/x-verse-x/setup.md
new file mode 100644
index 0000000..f18d42c
--- /dev/null
+++ b/docs/games/sega/chunithm/x-verse-x/setup.md
@@ -0,0 +1,3 @@
+
+--8<-- "docs/games/sega/chunithm/common/chusan/setup.md"
+
diff --git a/docs/games/sega/chunithm/x-verse-x/troubleshooting.md b/docs/games/sega/chunithm/x-verse-x/troubleshooting.md
new file mode 100644
index 0000000..31962c2
--- /dev/null
+++ b/docs/games/sega/chunithm/x-verse-x/troubleshooting.md
@@ -0,0 +1,3 @@
+
+--8<-- "docs/games/sega/chunithm/common/chusan/troubleshooting.md"
+
diff --git a/docs/games/sega/chunithm/x-verse/c2c.md b/docs/games/sega/chunithm/x-verse/c2c.md
new file mode 100644
index 0000000..bef03e0
--- /dev/null
+++ b/docs/games/sega/chunithm/x-verse/c2c.md
@@ -0,0 +1,3 @@
+
+--8<-- "docs/games/sega/chunithm/common/chusan/c2c.md"
+
diff --git a/docs/games/sega/chunithm/x-verse/controllers.md b/docs/games/sega/chunithm/x-verse/controllers.md
new file mode 100644
index 0000000..2cd7a99
--- /dev/null
+++ b/docs/games/sega/chunithm/x-verse/controllers.md
@@ -0,0 +1,3 @@
+
+--8<-- "docs/games/sega/chunithm/common/chusan/controllers.md"
+
diff --git a/docs/games/sega/chunithm/x-verse/setup.md b/docs/games/sega/chunithm/x-verse/setup.md
new file mode 100644
index 0000000..177a6dc
--- /dev/null
+++ b/docs/games/sega/chunithm/x-verse/setup.md
@@ -0,0 +1,3 @@
+
+--8<-- "docs/games/sega/chunithm/common/chusan/setup.md"
+
diff --git a/docs/games/sega/chunithm/x-verse/troubleshooting.md b/docs/games/sega/chunithm/x-verse/troubleshooting.md
new file mode 100644
index 0000000..c45d0d8
--- /dev/null
+++ b/docs/games/sega/chunithm/x-verse/troubleshooting.md
@@ -0,0 +1,3 @@
+
+--8<-- "docs/games/sega/chunithm/common/chusan/troubleshooting.md"
+
diff --git a/docs/games/sega/maimaidx/buddies/controllers.md b/docs/games/sega/maimaidx/buddies/controllers.md
new file mode 100644
index 0000000..d8dd268
--- /dev/null
+++ b/docs/games/sega/maimaidx/buddies/controllers.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/maimaidx/common/controllers.md"
\ No newline at end of file
diff --git a/docs/games/sega/maimaidx/buddies/setup.md b/docs/games/sega/maimaidx/buddies/setup.md
new file mode 100644
index 0000000..036b3ac
--- /dev/null
+++ b/docs/games/sega/maimaidx/buddies/setup.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/maimaidx/common/setup.md"
\ No newline at end of file
diff --git a/docs/games/sega/maimaidx/buddies/troubleshooting.md b/docs/games/sega/maimaidx/buddies/troubleshooting.md
new file mode 100644
index 0000000..d91a47e
--- /dev/null
+++ b/docs/games/sega/maimaidx/buddies/troubleshooting.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/maimaidx/common/troubleshooting.md"
\ No newline at end of file
diff --git a/docs/games/sega/maimaidx/buddiesplus/controllers.md b/docs/games/sega/maimaidx/buddiesplus/controllers.md
new file mode 100644
index 0000000..f04e207
--- /dev/null
+++ b/docs/games/sega/maimaidx/buddiesplus/controllers.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/maimaidx/common/controllers.md"
\ No newline at end of file
diff --git a/docs/games/sega/maimaidx/buddiesplus/setup.md b/docs/games/sega/maimaidx/buddiesplus/setup.md
new file mode 100644
index 0000000..664d0c8
--- /dev/null
+++ b/docs/games/sega/maimaidx/buddiesplus/setup.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/maimaidx/common/setup.md"
\ No newline at end of file
diff --git a/docs/games/sega/maimaidx/buddiesplus/troubleshooting.md b/docs/games/sega/maimaidx/buddiesplus/troubleshooting.md
new file mode 100644
index 0000000..f892eab
--- /dev/null
+++ b/docs/games/sega/maimaidx/buddiesplus/troubleshooting.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/maimaidx/common/troubleshooting.md"
\ No newline at end of file
diff --git a/docs/games/sega/maimaidx/circle/controllers.md b/docs/games/sega/maimaidx/circle/controllers.md
new file mode 100644
index 0000000..5884854
--- /dev/null
+++ b/docs/games/sega/maimaidx/circle/controllers.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/maimaidx/common/controllers.md"
\ No newline at end of file
diff --git a/docs/games/sega/maimaidx/circle/setup.md b/docs/games/sega/maimaidx/circle/setup.md
new file mode 100644
index 0000000..e1b9864
--- /dev/null
+++ b/docs/games/sega/maimaidx/circle/setup.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/maimaidx/common/setup.md"
\ No newline at end of file
diff --git a/docs/games/sega/maimaidx/circle/troubleshooting.md b/docs/games/sega/maimaidx/circle/troubleshooting.md
new file mode 100644
index 0000000..980fd18
--- /dev/null
+++ b/docs/games/sega/maimaidx/circle/troubleshooting.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/maimaidx/common/troubleshooting.md"
\ No newline at end of file
diff --git a/docs/games/sega/maimaidx/common/controllers.md b/docs/games/sega/maimaidx/common/controllers.md
new file mode 100644
index 0000000..175ba44
--- /dev/null
+++ b/docs/games/sega/maimaidx/common/controllers.md
@@ -0,0 +1,83 @@
+# Controllers
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+!!! tip ""
+
+ segatools, by default, only accepts keyboard input and does not recognize any
+ controllers. However, it can be configured with IO DLLs to add support for controllers.
+
+ The controller you plan on using should also be provided with these IO DLLs. If unsure,
+ check the support section for your controller, or contact the vendor directly. Alternate
+ options for the most common controllers are listed below.
+
+ These IO DLLs should be copied to your game's `App\Package` folder and referenced in
+ `segatools.ini` under the `[mai2io]` section.
+
+!!! tip ""
+
+ If you have a single DLL, uncomment the `path=` line by removing the leading semicolon (`;`),
+ then add your DLL's file name after the `=`:
+
+ ```ini hl_lines="5"
+ [mai2io]
+ ; To use a custom maimai DX IO DLL enter its path here.
+ ; Leave empty if you want to use Segatools built-in keyboard input.
+ ;(1)!
+ path=controller.dll
+ ```
+
+ 1. Note that there is no leading semicolon.
+
+### Keyboard/Touchscreen
+
+!!! tip ""
+
+ Keyboard/Touchscreen is the default input method
+
+ The default layout uses `QWEDCXZA` for physical buttons (each key representing the physical button's location relative to the center screen)
+
+ If you wish to change the default keybinds, an explanation on how to set these is included
+ above the `[io4]` section in your `segatools.ini`.
+
+ Touch input should automatically work after connecting a touch-screen display
+
+### ADX Controller
+
+!!! tip ""
+
+ First, you will need to purchase a compatible monitor if your controller did not come with one. A list of compatible monitors can be found on [this spreadsheet](https://docs.google.com/spreadsheets/d/1WN50pyJEPpXR32UTsEzsKe4Qm-EUAQgwmkCBX3kWB1Q)
+
+ Plug your controller in and open `Device Manager`.
+
+ Under the `Ports (COM & LPT)` section, ensure the correct ports are set for both the Touch Panel and Button LED.
+
+ - (Touch Panel) USB Serial Device: `COM3`
+ - (Button LED) USB-SERIAL CH340: `COM21`
+
+ If they are different change the port of the device by `Right Clicking on the Device -> Properties -> Port Settings -> COM Port Number`
+
+ Finally ensure the `mai2.ini` file in your data's `App/Package` folder has the following values set under the `[AM]` section
+ ```
+ [AM]
+ Target=0
+ DummyTouchPanel=0
+ DummyLED=0
+ ```
+
+ This gets your controller working with keyboard inputs. Its highly recommended that you also view [this setup guide](https://github.com/maimai-dx/ADX-Controller-Guide/blob/master/document/Setup.md) which provides more detailed instructions, improved drivers, and help with adjusting touch panel sensitivity.
+
+!!! warning
+ You **DO NOT** need to follow the Network Setup steps in the linked guide above if you've already done so while setting up game data
+
+ You **DO NOT** need to follow the Aime Reader setup in the linked guide above if you do not own one.
+
+
+
+### Arcade hardware and other controllers
+
+!!! tip ""
+
+ If you're interested in using a cabinet, or possibly even
+ making your own controller, the [Cons&Stuff website](https://consandstuff.github.io/)
+ and Discord community is a great place to start!
diff --git a/docs/games/sega/maimaidx/common/setup.md b/docs/games/sega/maimaidx/common/setup.md
new file mode 100644
index 0000000..c22bd87
--- /dev/null
+++ b/docs/games/sega/maimaidx/common/setup.md
@@ -0,0 +1,194 @@
+# Game Setup
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+--8<-- "docs/snippets/sega/common/data_old.md"
+
+## Preparing data
+
+--8<-- "docs/snippets/sega/common/data_driveletter.md"
+
+--8<-- "docs/snippets/common/data_readonly.md"
+
+--8<-- "docs/snippets/sega/common/data_preparation.md"
+
+ ```
+ 📂license
+ 📂package
+ 📄firewall.cfg
+ ▶️game.bat
+ ▶️pwGetHwinfo.exe
+ 📝pxGetHwInfo.ini
+ 📄system_config.json
+ ```
+--8<-- "docs/snippets/sega/common/data_bad.md"
+
+## Updating data
+
+--8<-- "docs/snippets/sega/common/data_updating.md"
+
+## Installing option data
+
+!!! tip ""
+
+ SEGA games receive content updates through option folders rather than direct game file updates.
+
+ - maimai DX JPN(SDEZ): each new release of maimai DX increments the first letter of the Options (ie. `H???` for BUDDiES, `I???` BUDDiES+)
+ - maimai DX EXP(SDGA): Options will always begin with the letter `A` (i.e `A???`)
+ - `???` represents a sequence of numbers
+
+ After downloading option files, extract them into your game's `Option` folder.
+
+ ```
+ 📂amfs
+ 📂App
+ 📂AppData
+ 📂Option
+ ┣━📂H005
+ ┣━📂H011
+ ┣━📂H031
+ ┗━ etc.
+ ```
+
+!!! info "Option numbers don't always follow a sequential pattern
+
+ Press your `Test` button (default `F1`) to enter the service menu. Use the `Service` button
+ (default `F2`) to navigate the menu, and `Test` button to select an option.
+
+ Navigate to **ゲーム設定** (`GAME ASSIGNMENTS`, the 7th option).
+
+ 
+
+ Select **店内マッチングの設定** (`IN-STORE MATCHING SETUP`, the first option)
+ and toggle this setting to **OFF**.
+
+ 
+
+ Select **終了** (`EXIT`, the last option) to exit to the main service menu.
+
+--8<-- "docs/snippets/sega/common/success.md"
+
+## Help
+
+--8<-- "docs/snippets/common/help.md"
\ No newline at end of file
diff --git a/docs/games/sega/maimaidx/common/troubleshooting.md b/docs/games/sega/maimaidx/common/troubleshooting.md
new file mode 100644
index 0000000..dcf8dd2
--- /dev/null
+++ b/docs/games/sega/maimaidx/common/troubleshooting.md
@@ -0,0 +1,68 @@
+# Troubleshooting
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+### My game crashes on launch/stuck on "Starting System Process"
+
+!!! tip ""
+
+ Could be due to **many** things, the most common of which are:
+
+ - `amdaemon` crashing in the background. Make sure that the `config_*.json` files
+ have valid syntax, your ICF files are correct.
+
+??? info "Capturing logs from `amdaemon` for troubleshooting"
+
+ To assist with troubleshooting, a script can be used to capture logs from `amdaemon`. Create a file named
+ `amdaemontest.bat` in `App\bin`, then paste the code block below into the file.
+
+ ```batch
+ @echo off
+ cls
+ echo Attempting to run AM Daemon ...
+ echo Window should close after 30 seconds
+ echo Log will be generated at amdaemontest.txt
+ call :sub >amdaemontest.txt
+ exit /b
+
+ :sub
+ pushd %~dp0
+ start /b "AM Daemon" /min inject -d -k mai2hook.dll amdaemon.exe -f -c config_common.json config_server.json
+ ping 127.0.0.1 -n 31 > nul && taskkill /F /im amdaemon.exe
+ ```
+
+ Double-click it to run. The script should run for 30 seconds, and you will get a file
+ named `amdaemontest.txt` in `App\bin`, which you can send to help people troubleshoot your issue.
+
+### My game is stuck on a black screen at launch!
+
+!!! tip ""
+
+ This could also be due to **many** things, the most common of which are:
+
+ - You have one or more incorrect/broken DLL(s) in `App\Package\Sinmai_Data\Managed`
+
+ This is likely to be `Assembly-CSharp.dll`, `Assembly-CSharp-firstpass.dll`, and/or `AMDaemon.NET.dll`.
+ You can try replacing the DLLs or re-downloading data from elsewhere.
+
+ - An ill-formed keychip is defined in `segatools.ini`
+
+### My game is stuck on a blue and black screen!
+
+!!! tip ""
+ You need to run the data using unprotected/unpacked files. Please refer to the setup guide to find which ones you need and obtain them.
+
+ If you believe you've already done this. You might be missing a try installing the latest [vcredist](https://www.techpowerup.com/download/visual-c-redistributable-runtime-package-all-in-one/)
+
+### My game is running too slow/fast or the notes are out of sync!
+
+!!! tip ""
+
+ The game could be running under or over its required refresh rate.
+
+ - Make sure V-Sync isn't disabled in your graphics settings (called "Vertical sync"
+ in NVIDIA Control Panel and "Wait for Vertical Refresh" in AMD Control Panel.)
+ - Limit `Sinmai.exe` to run at 60 FPS using a tool like [RivaTuner](https://www.guru3d.com/download/rtss-rivatuner-statistics-server-download) or a patch.
+
+ It could also be that your computer's performance isn't good enough to keep
+ a steady framerate.
diff --git a/docs/games/sega/maimaidx/prism/controllers.md b/docs/games/sega/maimaidx/prism/controllers.md
new file mode 100644
index 0000000..f84d251
--- /dev/null
+++ b/docs/games/sega/maimaidx/prism/controllers.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/maimaidx/common/controllers.md"
\ No newline at end of file
diff --git a/docs/games/sega/maimaidx/prism/setup.md b/docs/games/sega/maimaidx/prism/setup.md
new file mode 100644
index 0000000..34dad91
--- /dev/null
+++ b/docs/games/sega/maimaidx/prism/setup.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/maimaidx/common/setup.md"
\ No newline at end of file
diff --git a/docs/games/sega/maimaidx/prism/troubleshooting.md b/docs/games/sega/maimaidx/prism/troubleshooting.md
new file mode 100644
index 0000000..6033683
--- /dev/null
+++ b/docs/games/sega/maimaidx/prism/troubleshooting.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/maimaidx/common/troubleshooting.md"
\ No newline at end of file
diff --git a/docs/games/sega/maimaidx/prismplus/controllers.md b/docs/games/sega/maimaidx/prismplus/controllers.md
new file mode 100644
index 0000000..4a5184c
--- /dev/null
+++ b/docs/games/sega/maimaidx/prismplus/controllers.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/maimaidx/common/controllers.md"
\ No newline at end of file
diff --git a/docs/games/sega/maimaidx/prismplus/setup.md b/docs/games/sega/maimaidx/prismplus/setup.md
new file mode 100644
index 0000000..f0ed472
--- /dev/null
+++ b/docs/games/sega/maimaidx/prismplus/setup.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/maimaidx/common/setup.md"
\ No newline at end of file
diff --git a/docs/games/sega/maimaidx/prismplus/troubleshooting.md b/docs/games/sega/maimaidx/prismplus/troubleshooting.md
new file mode 100644
index 0000000..1baac9c
--- /dev/null
+++ b/docs/games/sega/maimaidx/prismplus/troubleshooting.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/maimaidx/common/troubleshooting.md"
\ No newline at end of file
diff --git a/docs/games/sega/ongeki/brightmemory/c2c.md b/docs/games/sega/ongeki/brightmemory/c2c.md
new file mode 100644
index 0000000..8e65ef2
--- /dev/null
+++ b/docs/games/sega/ongeki/brightmemory/c2c.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/ongeki/common/c2c.md"
\ No newline at end of file
diff --git a/docs/games/sega/ongeki/brightmemory/controllers.md b/docs/games/sega/ongeki/brightmemory/controllers.md
new file mode 100644
index 0000000..f0634f5
--- /dev/null
+++ b/docs/games/sega/ongeki/brightmemory/controllers.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/ongeki/common/controllers.md"
\ No newline at end of file
diff --git a/docs/games/sega/ongeki/brightmemory/setup.md b/docs/games/sega/ongeki/brightmemory/setup.md
new file mode 100644
index 0000000..96c9fa3
--- /dev/null
+++ b/docs/games/sega/ongeki/brightmemory/setup.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/ongeki/common/setup.md"
\ No newline at end of file
diff --git a/docs/games/sega/ongeki/brightmemory/troubleshooting.md b/docs/games/sega/ongeki/brightmemory/troubleshooting.md
new file mode 100644
index 0000000..043d6e4
--- /dev/null
+++ b/docs/games/sega/ongeki/brightmemory/troubleshooting.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/ongeki/common/troubleshooting.md"
\ No newline at end of file
diff --git a/docs/games/sega/ongeki/common/c2c.md b/docs/games/sega/ongeki/common/c2c.md
new file mode 100644
index 0000000..0910f9e
--- /dev/null
+++ b/docs/games/sega/ongeki/common/c2c.md
@@ -0,0 +1,45 @@
+# Cab-to-Cab over Internet
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+!!! danger "You are most likely to have success with Multiplayer when all users are using the SAME data and options, from the same sources. Verify that each person can run the game normally before attempting to network them together"
+
+## Initial setup
+
+!!! tip "Network"
+
+ Every machine needs to be on the same LAN.
+ If you wish to achieve that over the internet, follow the [ZeroTier setup guide](/extras/zerotier.md).
+
+!!! tip "GAME ASSIGNMENTS"
+
+ - Open the Service Menu and navigate to **ゲーム設定** (`GAME ASSIGNMENTS`, the 6th option)
+ 
+
+ - Make sure all machines are on the same group (Group A for example)
+ 
+
+ - Set one machine to `STANDARD`, and all other machines to `FOLLOW THE STANDARD`
+ 
+ 
+
+ Exit the Service Menu and load into Attract Mode. If the game passes the Group Check then chances are you're good to go! You can now login to a credit and open a cab-to-cab link request to check if the connection is working properly.
+
+## How to link?
+
+!!! Info "If you're new to O.N.G.E.K.I. and have never tried link-play before and you have no idea how, keep reading"
+
+ - Login to a credit
+
+ - If you're hosting a cab-to-cab session, choose a song first, then scroll to the far left and press `Confirm`
+ The cab-to-cab request is now open
+ 
+
+ - If you're connecting, navigate to the `Cabinet-to-Cabinet Play` tab and wait for other players to create a session
+ 
+
+ If you are able to see each other's session, congrats! You can now enjoy some cab-to-cab chain action!
+
+## Help
+
+--8<-- "docs/snippets/common/help.md"
\ No newline at end of file
diff --git a/docs/games/sega/ongeki/common/controllers.md b/docs/games/sega/ongeki/common/controllers.md
new file mode 100644
index 0000000..9dfad34
--- /dev/null
+++ b/docs/games/sega/ongeki/common/controllers.md
@@ -0,0 +1,126 @@
+# Controllers
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+!!! tip ""
+
+ segatools, by default, only accepts keyboard input and XInput Controllers.
+ However, it can be configured with IO DLLs to add support for other controllers.
+
+ The controller you plan on using should also be provided with these IO DLLs. If unsure,
+ check the support section for your controller, or contact the vendor directly. Alternate
+ options for the most common controllers are listed below.
+
+ These IO DLLs should be copied to your game's `App\package` folder and referenced in
+ `segatools.ini` under the `[mu3io]` section.
+
+!!! tip ""
+
+ If you have a single DLL, uncomment the `path=` line by removing the leading semicolon (`;`),
+ then add your DLL's file name after the `=`:
+
+ ```ini hl_lines="5"
+ [mu3io]
+ ; To use a custom O.N.G.E.K.I. IO DLL enter its path here.
+ ; Leave empty if you want to use Segatools built-in keyboard/gamepad input.
+ ;(1)!
+ path=controller.dll
+ ```
+
+ 1. Note that there is no leading semicolon.
+
+## Keyboard and Mouse
+
+!!! tip ""
+
+ Keyboard and Mouse is the default input method.
+
+ To enable mouse lever emulation ensure that the `mouse` option is set to `1` in the `[io4]`
+ section of your `segatools.ini`:
+
+ ```ini hl_lines="3"
+ [io4]
+ ; Set "1" to enable mouse lever emulation, "0" to use XInput
+ mouse=1
+ ```
+
+ The default layout use `ASD` for the left 3 buttons, and `JKL` for the right 3 buttons.
+ `Mouse Left/Right Click` are used for the left and right bumper buttons.
+
+ If you wish to change the default keybinds, an explanation on how to set these is included
+ above the `[io4]` section in your `segatools.ini`.
+
+## XInput Controller
+
+!!! tip ""
+
+ XInput controllers are supported by segatools. To enable XInput, ensure that the `mouse` option
+ is set to `0` in the `[io4]` section of your `segatools.ini`:
+
+ ```ini hl_lines="3"
+ [io4]
+ ; Set "1" to enable mouse lever emulation, "0" to use XInput
+ mouse=0
+ ```
+
+ If you wish to change the default keybinds, an explanation on how to set these is included
+ above the `[io4]` section in your `segatools.ini`.
+
+## Mageki
+
+!!! tip ""
+
+ Mageki allows you to use a mobile device as a O.N.G.E.K.I. controller. It replicates the layout
+ of an arcade O.N.G.E.K.I. controller on your mobile device.
+
+ Mageki supports both Android and iOS devices. For installation instructions, please refer to
+ the [English User Manual on the Mageki GitHub Repository](https://github.com/Sanheiii/Mageki/wiki/Mageki-User-Manual).
+
+!!! warning "Configuring ongeki-io and MU3-input.dll"
+
+ When moving the zipped contents of `MU3Input`, move all folders **EXCEPT** the `segatools.ini` file into your `App\package` folder in a way that matches its file structure.
+ Modify the `[mu3io]` and `[aimeio]` sections of your existing `segatools.ini` file to look like the following:
+
+ ```ini hl_lines="2 5"
+ [mu3io]
+ path=MU3Input.dll
+
+ [aimeio]
+ path=MU3Input.dll
+ ```
+ If these sections do not exist, add them to the end of your `segatools.ini` file.
+
+!!! info "IOConfig doesn't launch for me/This application requires the Windows App Runtime"
+
+ Download and extract the contents of the [Windows App Runtime Version 1.5 Redistributable](https://aka.ms/windowsappsdk/1.5/1.5.240802000/Microsoft.WindowsAppRuntime.Redist.1.5.zip)
+ In the `WindowsAppSDK-Installer-x64` folder run `WindowsAppRuntimeInstall-x64.exe`
+
+ If IOConfig still fails to launch, try using the [SelfContained version of ongeki-io](https://github.com/Sanheiii/ongeki-io/releases)
+
+## ONTROLLER
+
+!!! tip ""
+
+ - Navigate to [Mu3IO.NET releases](https://github.com/jujuforce/Mu3IO.NET/releases/) and download `mu3io.dll`. Put this file in your `App\package` folder.
+ - Edit your `segatools.ini` to reference the DLL:
+
+ ```ini hl_lines="4"
+ [mu3io]
+ ; To use a custom O.N.G.E.K.I. IO DLL enter its path here.
+ ; Leave empty if you want to use Segatools built-in keyboard/gamepad input.
+ path=mu3io.dll
+ ```
+
+## YUANGEKI
+
+!!! tip ""
+
+ This controller does not support IO4 mode. Instead, refer to the [Keyboard and Mouse](#keyboard-and-mouse) section.
+
+## Arcade hardware and other controllers
+
+!!! tip ""
+
+ If you're interested in using a cabinet slider and air sensors, or possibly even
+ making your own controller, the [Cons&Stuff website](https://consandstuff.github.io/)
+ and Discord community is a great place to start!
diff --git a/docs/games/sega/ongeki/common/setup.md b/docs/games/sega/ongeki/common/setup.md
new file mode 100644
index 0000000..659ad51
--- /dev/null
+++ b/docs/games/sega/ongeki/common/setup.md
@@ -0,0 +1,214 @@
+# Game Setup
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+--8<-- "docs/snippets/sega/common/data_old.md"
+
+## Preparing data
+
+--8<-- "docs/snippets/sega/common/data_driveletter.md"
+
+--8<-- "docs/snippets/common/data_readonly.md"
+
+--8<-- "docs/snippets/sega/common/data_preparation.md"
+
+ ```
+ 📂license
+ 📂package
+ 📄firewall.cfg
+ ▶️game.bat
+ ▶️pxGetHwinfo.exe
+ 📝pxGetHwInfo.ini
+ ▶️RotateDisplay.exe
+ 📄system_config.json
+ ```
+
+--8<-- "docs/snippets/sega/common/data_bad.md"
+
+## Updating data
+
+--8<-- "docs/snippets/sega/common/data_updating.md"
+
+## Installing option data
+
+!!! tip ""
+
+ SEGA games receive content updates through option folders rather than direct game file updates.
+
+ For O.N.G.E.K.I., official options are named `A???`, where `???` represents a sequence of numbers.
+ Community-created options often use letters instead of numbers to differentiate them from official releases.
+
+ After downloading option files, extract them into your game's `Option` folder.
+
+ ```
+ 📂amfs
+ 📂App
+ 📂AppData
+ 📂Option
+ ┣━📂A001
+ ┣━📂A002
+ ┣━📂A012
+ ┗━ etc.
+ ```
+
+!!! info "Option numbers don't always follow a sequential pattern
+
+ Press your `Test` button (default `F1`) to enter the service menu. Use the `Service` button
+ (default `F2`) to navigate the menu, and `Test` button to select an option.
+
+ Navigate to **ゲーム設定** (`GAME ASSIGNMENTS`, the 6th option).
+
+ 
+
+
+ Select **グループ内基準機の設定** (`SET STANDARD IN GROUP`, the second option)
+ and toggle this setting to **基準機** (`STANDARD`).
+
+ 
+
+
+ Select **終了** (`EXIT`, the last option) to exit to the main service menu.
+
+
+
+ Navigate to **閉店設定** (`CLOSE SETTING`, the 10th option).
+
+ 
+
+
+ Navigate to **時** (`HOUR`, the 2nd option) and use the `Service` button
+ to toggle the setting until it says **全時刻** (`ALL TIME`).
+
+ 
+
+
+ Select **終了** (`EXIT`, the last option) to exit to the main service menu, then select **終了**
+ (also the last option) in the main menu to exit the service menu.
+
+--8<-- "docs/snippets/sega/common/success.md"
+
+## Help
+
+--8<-- "docs/snippets/common/help.md"
diff --git a/docs/games/sega/ongeki/common/troubleshooting.md b/docs/games/sega/ongeki/common/troubleshooting.md
new file mode 100644
index 0000000..727babd
--- /dev/null
+++ b/docs/games/sega/ongeki/common/troubleshooting.md
@@ -0,0 +1,76 @@
+# Troubleshooting
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+### My game crashes on launch/stuck on "Starting System Process"
+
+!!! tip ""
+
+ Could be due to **many** things, the most common of which are:
+
+ - `amdaemon` crashing in the background. Make sure that the `config_*.json` files
+ have valid syntax, your ICF files are correct.
+
+??? info "Capturing logs from `amdaemon` for troubleshooting"
+
+ To assist with troubleshooting, a script can be used to capture logs from `amdaemon`. Create a file named
+ `amdaemontest.bat` in `App\bin`, then paste the code block below into the file.
+
+ ```batch
+ @echo off
+ cls
+ echo Attempting to run AM Daemon ...
+ echo Window should close after 30 seconds
+ echo Log will be generated at amdaemontest.txt
+ call :sub >amdaemontest.txt
+ exit /b
+
+ :sub
+ pushd %~dp0
+ start /b "AM Daemon" /min inject -d -k mu3hook.dll amdaemon.exe -f -c config_common.json config_server.json
+ ping 127.0.0.1 -n 31 > nul && taskkill /F /im amdaemon.exe
+ ```
+
+ Double-click it to run. The script should run for 30 seconds, and you will get a file
+ named `amdaemontest.txt` in `App\bin`, which you can send to help people troubleshoot your issue.
+
+### My game is stuck on a black screen at launch!
+!!! tip ""
+
+ This could also be due to **many** things, the most common of which are:
+
+ - You have one or more incorrect/broken DLL(s) in `App\package\mu3_Data\Managed`
+
+ This is likely to be `Assembly-CSharp.dll`, `Assembly-CSharp-firstpass.dll`, and/or `AMDaemon.NET.dll`.
+ You can try replacing the DLLs or re-downloading data from elsewhere.
+ - An ill-formed keychip is defined in `segatools.ini`
+
+### My game is running too slow/fast or the notes are out of sync!
+
+!!! tip ""
+
+ The game could be running under or over its required refresh rate.
+
+ - Make sure V-Sync isn't disabled in your graphics settings (called "Vertical sync"
+ in NVIDIA Control Panel and "Wait for Vertical Refresh" in AMD Control Panel.)
+ - Limit `mu3.exe` to run at 60 FPS using a tool like [RivaTuner](https://www.guru3d.com/download/rtss-rivatuner-statistics-server-download) or a patch.
+
+ It could also be that your computer's performance isn't good enough to keep
+ a steady framerate.
+
+### My lever controls aren't working!
+!!! tip ""
+
+ You may need to calibrate your lever.
+
+ From the `TEST MENU` select **レバー設定** (`LEVER SETTINGS`) and then move the lever left to
+ right ensuring that the game detects the full range of motion.
+
+ Then save by selecting **終了** (`EXIT`) and then **保存する** (`SAVE`).
+
+### My game is stuttering
+
+!!! tip ""
+
+ For NVIDIA users, create an override for `mu3.exe` in NVIDIA Control Panel
+ and change "Power management mode" to "**Prefer maximum performance**".
\ No newline at end of file
diff --git a/docs/games/sega/ongeki/refresh/c2c.md b/docs/games/sega/ongeki/refresh/c2c.md
new file mode 100644
index 0000000..d8a86cc
--- /dev/null
+++ b/docs/games/sega/ongeki/refresh/c2c.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/ongeki/common/c2c.md"
\ No newline at end of file
diff --git a/docs/games/sega/ongeki/refresh/controllers.md b/docs/games/sega/ongeki/refresh/controllers.md
new file mode 100644
index 0000000..d6a81ca
--- /dev/null
+++ b/docs/games/sega/ongeki/refresh/controllers.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/ongeki/common/controllers.md"
\ No newline at end of file
diff --git a/docs/games/sega/ongeki/refresh/setup.md b/docs/games/sega/ongeki/refresh/setup.md
new file mode 100644
index 0000000..0262153
--- /dev/null
+++ b/docs/games/sega/ongeki/refresh/setup.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/ongeki/common/setup.md"
\ No newline at end of file
diff --git a/docs/games/sega/ongeki/refresh/troubleshooting.md b/docs/games/sega/ongeki/refresh/troubleshooting.md
new file mode 100644
index 0000000..ef1d173
--- /dev/null
+++ b/docs/games/sega/ongeki/refresh/troubleshooting.md
@@ -0,0 +1,2 @@
+
+--8<-- "docs/games/sega/ongeki/common/troubleshooting.md"
\ No newline at end of file
diff --git a/docs/games/sega/wacca/reverse/controllers.md b/docs/games/sega/wacca/reverse/controllers.md
new file mode 100644
index 0000000..4769329
--- /dev/null
+++ b/docs/games/sega/wacca/reverse/controllers.md
@@ -0,0 +1,88 @@
+
+# Controllers
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+!!! tip ""
+
+ segatools, by default, only accepts keyboard input and XInput Controllers.
+ However, it can be configured with IO DLLs to add support for other controllers.
+
+ The controller you plan on using should also be provided with these IO DLLs. If unsure,
+ check the support section for your controller, or contact the vendor directly. Alternate
+ options for the most common controllers are listed below.
+
+ These IO DLLs should be copied to your game's `App\bin` folder and referenced in
+ `segatools.ini` under the `[mercuryio]` section.
+
+!!! tip ""
+
+ If you have a single DLL, uncomment the `path=` line by removing the leading semicolon (`;`),
+ then add your DLL's file name after the `=`:
+
+ ```ini hl_lines="5"
+ [mercuryio]
+ ; To use a custom WACCA IO DLL enter its path here.
+ ; Leave empty if you want to use Segatools built-in keyboard input.
+ ;(1)!
+ path=controller.dll
+ ```
+
+ 1. Note that there is no leading semicolon.
+
+## Touch screen / Mobile device
+
+!!! tip ""
+
+ Both Any2WACCAi and Toucca allows you to use a touch screen or a mobile device as a WACCA controller.
+ It replicates the layout of an arcade WACCA cab.
+
+!!! info "Installation instructions"
+
+ [Any2WACCAi](https://gitea.tendokyu.moe/Dniel97/SEGAguide/wiki/SDFE#any2waccai-installation)
+ [Toucca](https://github.com/BlueGlassBlock/toucca/?tab=readme-ov-file#setup)
+
+ !!! warning "com0com issues"
+
+ If you're getting errors such as `Could not find file 'COM5'`, and particularly if you're on Windows 11, com0com v3 may be causing issues.
+ Install [com0com v2](https://sourceforge.net/projects/com0com/files/com0com/2.2.2.0/com0com-2.2.2.0-x64-fre-signed.zip/download) instead.
+
+## WACVR
+
+!!! tip ""
+
+ WACVR allows you to use a VR Headset to replicate a WACCA cab and use it as a controller.
+
+!!! tip "Setting up WACVR"
+
+ Download WACVR from [here](https://github.com/xiaopeng12138/WACVR/releases/latest) and extract to a folder of your choice.
+ Copy the `mercuryio.dll` file to the the `App/bin` folder in your data folder.
+
+ Edit your `segatools.ini` like this:
+
+ ```ini hl_lines="4"
+ [mercuryio]
+ ; To use a custom WACCA IO DLL enter its path here.
+ ; Leave empty if you want to use Segatools built-in keyboard input.
+ path=mercuryio.dll
+ ```
+
+ Start up your VR software as well as SteamVR, then launch WACCA and `WACVR.exe`.
+ WACVR should set up with WACCA automatically.
+
+!!! warning
+
+ If you're experiencing a warped screen in WACVR, make sure your monitor is set to portrait mode and
+ check the `Full display capture` box in WACVR.
+
+## Arcade hardware and other controllers
+
+!!! tip ""
+
+ If you want to run the game on a real cab, check the [reDIVE World website](https://redive.world/)
+
+!!! tip ""
+
+ If you're interested in using a cabinet slider, or possibly even
+ making your own controller, the [Cons&Stuff website](https://consandstuff.github.io/)
+ and Discord community is a great place to start!
\ No newline at end of file
diff --git a/docs/games/sega/wacca/reverse/setup.md b/docs/games/sega/wacca/reverse/setup.md
new file mode 100644
index 0000000..6bc4454
--- /dev/null
+++ b/docs/games/sega/wacca/reverse/setup.md
@@ -0,0 +1,140 @@
+
+# Game Setup
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+--8<-- "docs/snippets/sega/common/data_old.md"
+
+!!! warning "Wireless Device"
+
+ The Chinese SDJE Version requires a custom piece of hardware that will likely not work with known tools.
+
+ If you're having issues with a "Wireless Device" during boot or network testing, you likely need a different version of the game data.
+
+## Preparing data
+
+--8<-- "docs/snippets/sega/common/data_driveletter.md"
+
+--8<-- "docs/snippets/common/data_readonly.md"
+
+--8<-- "docs/snippets/sega/common/data_preparation.md"
+
+ ```
+ 📂bin
+ 📂pxbin
+ 📂WindowsNoEditor
+ 📄firewall.cfg
+ ▶️game.bat
+ ▶️pxGetHwinfo.exe
+ 📝pxGetHwInfo.ini
+ 📄system_config.json
+ ```
+
+--8<-- "docs/snippets/sega/common/data_bad.md"
+
+## Updating data
+
+--8<-- "docs/snippets/sega/common/data_updating.md"
+
+## Installing ICFs
+
+--8<-- "docs/snippets/sega/common/data_icfs.md"
+
+## Patching the game
+
+--8<-- "docs/snippets/sega/common/patching.md"
+
+## Installing segatools
+
+--8<-- "docs/snippets/sega/common/segatools_install.md"
+ - Find `mercury.zip` and extract it to your data's `App\bin` folder
+
+ You should now have these files added to your `App\bin` directory:
+
+ ```
+ 📂DEVICE
+ ▶️inject.exe
+ ⚙️mercuryhook.dll
+ 📝segatools.ini
+ ▶️launch.bat
+ ```
+
+## Configuring segatools
+
+--8<-- "docs/snippets/sega/common/segatools_preamble_bin.md"
+
+=== "[vfs]"
+
+--8<-- "docs/snippets/sega/common/segatools_relativepaths.md"
+
+--8<-- "docs/snippets/sega/common/segatools_vfs.md"
+
+## Configuring audio
+
+--8<-- "docs/snippets/common/audio_48khz.md"
+
+## Connecting to a network
+
+--8<-- "docs/snippets/sega/common/network_preamble.md"
+
+--8<-- "docs/snippets/sega/common/network_remote.md"
+
+--8<-- "docs/snippets/sega/common/network_local.md"
+
+## Installing FTDI LEDs driver
+
+!!! tip ""
+
+ - Download the [FTDI drivers](https://ftdichip.com/wp-content/uploads/2023/09/CDM-v2.12.36.4-WHQL-Certified.zip)
+ - Extract them
+ - Copy `CDM-v2.12.36.4-WHQL-Certified/amd64/ftd2xx64.dll`
+ to `/App/WindowsNoEditor/Mercury/Binaries/Win64/`
+ - Rename the file to `ftd2xx.dll`
+
+## Installing VCRedist & DirectX
+
+--8<-- "docs/snippets/common/setup_vcredist_directx.md"
+
+## Before playing
+
+--8<-- "docs/snippets/common/before_playing.md"
+
+## First launch
+
+!!! tip ""
+
+ If you've followed all instructions correctly, you're now finally ready to launch the game!
+
+ Set your display orientation to portrait mode.
+
+ Start the game by running `App\bin\launch.bat`.
+
+ Press your `Test` button (default `F1`) to enter the service menu. Use the `Service` button
+ (default `F2`) to navigate the menu, and `Test` button to select an option.
+
+ You can also use the Volume buttons (default `UP` and `DOWN` keys) to navigate
+ and the `ENTER` key to select.
+
+ Navigate to **SYSTEM SETTING**.
+
+ 
+
+ Navigate to **CLOSING TIME SETTINGS**.
+
+ 
+
+ Navigate to **ALL DAYS OF THE WEEK** and use the `Service` button
+ to toggle the setting until it says **OFF**.
+
+ 
+
+ Select **APPLY SETTINGS AND RE-BOOT** to save the settings.
+
+ Note that this will close your game and you will have to start it again
+ with `launch.bat`.
+
+--8<-- "docs/snippets/sega/common/success.md"
+
+## Help
+
+--8<-- "docs/snippets/common/help.md"
diff --git a/docs/games/taito/tetoteconnect/setup.md b/docs/games/taito/tetoteconnect/setup.md
new file mode 100644
index 0000000..08ef0f4
--- /dev/null
+++ b/docs/games/taito/tetoteconnect/setup.md
@@ -0,0 +1,131 @@
+
+# Game Setup
+
+--8<-- "docs/snippets/common/data_warning.md"
+
+## Preparing data
+
+--8<-- "docs/snippets/common/data_readonly.md"
+
+ The **complete game data** should be approximately **5 GB or larger**.
+
+ Here's what the expected data structure should look like:
+
+ ```
+ 📂[SYSTEM]
+ 📂MonoBleedingEdge
+ 📂System Volume Information
+ 📂Vision_Data
+ ▶️game.exe
+ 📄game.inf
+ ▶️RunVisionProd.bat
+ ▶️Setting.bat
+ ▶️UnityCrashHandler64.exe
+ ⚙️UnityPlayer.dll
+ ▶️Vision.exe
+ ⚙️WinPixEventRuntime.dll
+ ```
+
+## Installing BepInEx
+
+!!! tip ""
+
+ - Download the most recent [BepInEx 5 release](https://github.com/BepInEx/BepInEx/releases) (`BepInEx_win_x64_5.x.y.z.zip`)
+
+ !!! warning "We need BepInEx 5 since as of writing, BepInEx 6 does not support the required plugin"
+
+ - Extract the archive to the root folder of your game data
+
+ You should now have these files added to your directory:
+
+ ```
+ 📂BepInEx
+ 📄.doorstop_version
+ 📄changelog.txt
+ 📝doorstop_config.ini
+ ⚙️winhttp.dll
+ ```
+
+## Installing tetoco
+
+!!! tip ""
+
+ - Head over to [tetoco releases](https://github.com/Redcrafter/tetoco/releases)
+ - Download `tetoco.dll`
+ - Create a folder called `plugins` in the `BepInEx` folder
+ - Move the dll file to that newly created folder
+
+ You should end up with a file structure as follows:
+
+ ```
+ 📂BepInEx
+ ┗ 📂plugins
+ ┗⚙️tetoco.dll
+ ```
+
+## Installing VCRedist & DirectX
+
+--8<-- "docs/snippets/common/setup_vcredist_directx.md"
+
+## Monitor orientation
+
+!!! info "With tetoco installed, the game won't automatically rotate to portrait mode when starting it"
+
+ The game can be played in landscape mode but a lot of the play area will be lost, it's best to set your monitor to portrait mode before launching the game.
+
+??? tip "Manually rotating"
+
+ - Right click on your Desktop
+ - Select `Display settings`
+ - Look for `Display orientation` and set it to `Portrait` or `Portrait (flipped)`
+ - Rotate your monitor 90°
+
+??? tip "Automatically rotating"
+
+ Right click on [this link](https://raw.githubusercontent.com/gmiwoj/Windows-Display-Orientation-Script/main/windows-display-orientation-script.ps1)
+ then `Save Link As` and place the `windows-display-orientation-script.ps1` file in your game's directory.
+
+ Create a new `start.bat` file, and set its content to this, it will set your monitor as **Portrait (flipped)**, and automatically rotate it back once you close the game.
+
+ ```ini
+ powershell.exe -ExecutionPolicy Bypass -File "windows-display-orientation-script.ps1" 0 90
+ Vision.exe
+ powershell.exe -ExecutionPolicy Bypass -File "windows-display-orientation-script.ps1" 0 0
+ ```
+
+ Alternatively, you can set it to **Portrait** *(not flipped)* by changing `90` to `270`.
+
+ ```ini
+ powershell.exe -ExecutionPolicy Bypass -File "windows-display-orientation-script.ps1" 0 270
+ Vision.exe
+ powershell.exe -ExecutionPolicy Bypass -File "windows-display-orientation-script.ps1" 0 0
+ ```
+
+## First launch
+
+!!! tip ""
+
+ If you've followed all instructions correctly, you're ready to launch the game.
+
+ Start the game by running `Vision.exe`, or `start.bat` if you followed [the automatic monitor rotation part](#monitor-orientation).
+
+!!! tip ""
+
+ You're all done! The game should load up properly now.
+
+ You can use the **Login as Local** button to use your local save profile.
+
+ The `T` key can be pressed to access the service menu.
+
+## Connecting to a network
+
+!!! info "By default, tetoco uses its own local network and saves data locally"
+
+ Please follow this step only if you have a network to connect to.
+
+??? tip "Remote (Online Network)"
+
+ - Open the automatically created configuration file `BepInEx\config\tetoco.cfg`
+ - Set `UseLocalServer` to **false**
+ - Then, set `RemoteServer` to the address provided by your network
+ - Finally, set the `CardId` provided by your network
\ No newline at end of file
diff --git a/docs/img/common/audio_16_441.webp b/docs/img/common/audio_16_441.webp
new file mode 100644
index 0000000000000000000000000000000000000000..bd41aaa5bdf6f75d8cfb37073a2c80d009afd056
GIT binary patch
literal 6082
zcmV;z7d_}wNk&Gx7XScPMM6+kP&iDk7XSb+kAZOj72$sNf0ZLS=W_pnFei76ZME-0
zm-!F4<@Pc&Gcz+YGcz;v@F>j8i^DVL_xXN*r|SHw>eNtK