Introduction
Sn0w uses a YAML-based configuration system to save and load module settings, keybinds, and client preferences. All configuration files are stored in theSn0w folder in your Minecraft directory.
Configuration Directory Structure
Configuration System
Main Folder Location
The configuration directory is located at:- Path:
<Minecraft Directory>/Sn0w/ - Auto-created: The folder is automatically created on first launch if it doesn’t exist
Configuration Types
1. Feature Configs (Auto-save)
Individual module configurations are automatically saved inSn0w/features/:
- Each module has its own
.ymlfile - Automatically saved on client shutdown
- Contains module state, settings, and values
2. User Configs (Manual save/load)
Complete configuration snapshots saved inSn0w/configs/:
- Created using the
configcommand - Contains all modules and their settings
- Can be shared and loaded on demand
- Supports multiple configuration presets
Config Command Usage
Save Configuration
configs/<name>.yml
Example:
Load Configuration
configs/<name>.yml, including enabled states and keybinds.
Example:
Loading a config will enable/disable modules and update all settings to match the saved configuration.
Soft Load Configuration
- Render and HUD modules
- Client modules (except AntiCheat)
- Keybinds (preserves current binds)
- Colors (preserves current color settings)
List Available Configs
Delete Configuration
Open Config Folder
Sn0w/configs/ folder in your system file explorer.
Configuration Format
Configs use YAML format with the following structure:Common Settings
Every module configuration includes these base settings:| Setting | Type | Description |
|---|---|---|
enabled | Boolean | Whether the module is enabled |
bind | Integer/String | Keybind (key code or MOUSE_X) |
chatNotify | Boolean | Show chat notification on toggle |
visible | Boolean | Show in module list |
name | String | Display name for the module |
Savable System
The configuration system implements theISavable interface:
Feature, which implements this interface for automatic serialization.
Config Loading Process
- Startup: Client loads individual feature configs from
features/folder - Runtime: User can load preset configs using
.config load <name> - Shutdown: Client automatically saves all feature configs
The configuration system uses SnakeYAML with pretty printing enabled for human-readable files.
Best Practices
Backup Important Configs
Before making major changes, save your current setup:Organize Multiple Configs
Create specialized configs for different scenarios:pvp.yml- Combat-focused settingsmining.yml- Mining and movementdefault.yml- Base configurationevent.yml- Event-specific setup
Share Configs
Config files can be shared with other users:- Navigate to
Minecraft/Sn0w/configs/ - Copy the
.ymlfile - Share with others to replicate your setup
Troubleshooting
Config Not Loading
Error: “Could not find config X.yml!”- Verify the file exists in
Sn0w/configs/ - Check for typos in the filename
- Use
.config listto see available configs
Settings Not Saving
- Ensure the client has write permissions to the Minecraft directory
- Check for corrupted YAML syntax if manually editing
- Verify the
Sn0wfolder exists and is not read-only
Corrupted Config File
If a config file becomes corrupted:- Delete the problematic
.ymlfile - Restart the client to regenerate defaults
- Reconfigure settings and save a new config
Advanced: Manual Editing
You can manually edit.yml files with a text editor:
- Navigate to
Minecraft/Sn0w/configs/ - Open
.ymlfile in a text editor - Edit values following YAML syntax
- Save file
- Use
.config load <name>in-game to apply changes
See Also
- Keybinds - Learn how to bind modules to keys
- Config Files - Detailed file format reference
- Commands - Full command reference