# .minecraft Folder (Location, Structure)

Minecraft stores all its essential game files, assets, configurations, logs, saved worlds, resource packs, shader packs, and importantly, **mods**, within a primary directory commonly referred to as the **`.minecraft`** folder.

* **Default Location:** By default, on Windows, this folder is located in the user's roaming AppData directory: `C:\Users\{username}\AppData\Roaming\.minecraft`. This path can often be accessed quickly via the Run dialog (Win+R) using the environment variable shortcut `%appdata%\.minecraft`.
* **Variable Location:** **CRITICAL:** The location of the `.minecraft` folder used by the _active_ game instance is **NOT FIXED** and should **NEVER** be assumed to be the default path without verification. As mentioned, custom launchers or manual user configuration can place the game directory almost anywhere on the system's storage devices (e.g., `D:\Games\MinecraftInstances\MyModpack`, `C:\MultiMC\Instances\Forge1.8.9\.minecraft`). Blindly checking only the default `%appdata%\.minecraft` path is a common mistake that leads to **missed evidence and ineffective screenshares.**
* **Finding the Correct `.minecraft` Folder During a Screenshare:** Identifying the _actual_ game directory being used by the running Minecraft instance is paramount. The most reliable methods are:
  1. **In-Game Method (Recommended First Step):**
     * While Minecraft is running, navigate to _Options..._ (or equivalent).
     * Select _Resource Packs..._.
     * Click the _Open Pack Folder_ button (or similar wording depending on version/language).
     * This action will open the `resourcepacks` subfolder within the currently active game directory.
     * Navigate **one level up** from the `resourcepacks` folder to its parent directory. **This parent directory is the correct `.minecraft` (or equivalent root game folder) being used by that specific instance.** Note this path carefully.
  2. **System Informer (Process Analysis - Advanced/Confirmation):**
     * Run System Informer with administrator privileges (ensure Kernel-Mode Driver is enabled if needed).
     * Find the specific `javaw.exe` process belonging to the Minecraft instance.
     * Right-click the process > Properties > Memory tab > Strings button.
     * Configure the search (e.g., Min length 5, Mapped & Private selected).
     * Click the Filter button and use a "Contains (case-insensitive)" filter.
     * Search for strings containing common subdirectory names like `\mods` or `\versions` or `\resourcepacks`.
     * Examine the resulting full paths found in the process memory. These paths will reveal the exact directories the running game is actively accessing, confirming the correct `.minecraft` location and its subfolders like `mods`.
* **Structure and Relevant Subdirectories:** Within the correct root game folder, several subdirectories are particularly relevant for cheat detection:
  * `versions/`: Contains subfolders for each installed Minecraft version (vanilla or modded like Forge/Fabric). Inside these, you find the core game `.jar` files (which can be targets for Javaedit) and associated libraries.
  * `mods/`: This is where Forge or Fabric mods (`.jar` files) are placed to be loaded by the game. This folder is a primary target for analysis.
  * `libraries/`: Stores essential Java libraries required by Minecraft and Forge/Fabric. Occasionally, modified or malicious libraries might be placed here.
  * `logs/`: Contains log files generated by the game and Forge/Fabric (e.g., `latest.log`, `debug.log`). These can show errors, loaded mods, and sometimes runtime information useful for context.
  * `config/`: Often contains configuration files (`.cfg`, `.toml`, `.json`) for installed mods, which might reveal suspicious settings.
  * `resourcepacks/` & `shaderpacks/`: While typically containing cosmetic assets, examining modification dates or unusual file types here can occasionally be relevant.
