cal/claude-home
1
0
Fork 0
Code Issues 3 Pull Requests Actions Packages Projects Releases Wiki Activity
b50808eb8e
claude-home/gaming/CONTEXT.md
Cal Corum 48efafe217 docs: reorganize gaming into per-game directories, add tabletop section 
Move Ready or Not configs/scripts into gaming/ready-or-not/, Stackmon into
gaming/stackmon/, add Palworld client and server docs. Move Vagabond RPG
PDFs to new tabletop/ directory with Age of Ashes GM reference.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-04 21:50:13 -06:00

3.0 KiB
Raw Blame History

Gaming Configuration Context

Technology Overview

Steam Tinker Launch (STL) provides advanced configuration options for running Windows games on Linux through Steam's Proton compatibility layer. This directory contains configurations, scripts, and documentation for gaming setups.

Key Components

Steam Tinker Launch (STL)

  • Purpose: Advanced Proton configuration and game-specific tweaks
  • Config Location: ~/.config/steamtinkerlaunch/
  • Game Configs: ~/.config/steamtinkerlaunch/gamecfgs/
  • Global Settings: ~/.config/steamtinkerlaunch/global.conf

Hardware

  • CPU: AMD Ryzen 7 7800X3D (8C/16T)
  • GPU: NVIDIA GeForce RTX 4080 SUPER (16GB VRAM)
  • Display (primary): 2560x1440 @ 120Hz OLED with HDR
  • Display (secondary): 2560x1440 @ 60Hz (no HDR)

Configuration Patterns

Standard Baseline (all games)

PROTON_ENABLE_NVAPI="1"           # Required for GPU detection
PROTON_HIDE_NVIDIA_GPU="0"        # MUST be 0 - do NOT hide GPU
DXVK_ASYNC="1"                    # Reduce shader compilation stuttering
USEGAMEMODERUN="1"                # Enable GameMode
USEMANGOHUD="1"                   # Performance monitoring
WAITEDITOR="0"                    # Skip STL popup - edit configs via Claude Code

For per-game settings (RT, DLSS, HDR, retro games), see the steam-game-setup skill: .claude/skills/steam-game-setup/SKILL.md

Directory Structure

/gaming/
├── CONTEXT.md              # This file - technology overview
├── troubleshooting.md      # Error handling and debugging
├── stl-config-changes.txt  # STL config change log
├── palworld/               # Palworld (1623730)
│   ├── stl-config.md      # Client STL configuration
│   └── server.md          # Dedicated server (LXC 230)
├── ready-or-not/           # Ready or Not (1144200)
│   ├── examples/          # Working configs and setup scripts
│   └── scripts/           # Game-specific scripts
├── stackmon/               # Stackmon (3729550)
│   └── stl-config.md     # Client STL configuration
└── scripts/               # General gaming automation scripts
    └── CONTEXT.md         # Script-specific documentation

Best Practices

Configuration Management

  • Keep per-game docs in gaming/<game-name>/
  • Document hardware-specific settings clearly
  • Test one setting at a time when troubleshooting
  • Backup working configurations before changes

Performance Optimization

  • Start with GE-Proton for best compatibility
  • Enable GameMode for CPU scheduling
  • Use GameScope for resolution/scaling control
  • Monitor GPU usage with MangoHUD

Troubleshooting Approach

  1. Verify base Proton compatibility
  2. Test without STL modifications first
  3. Add settings incrementally
  4. Document working combinations
  5. Check hardware-specific requirements

Integration Points

  • Monitoring: Use MangoHUD for performance metrics
  • Scripts: Automate common gaming tasks
  • Networking: Configure for multiplayer gaming