How to Get Community Support for RenoDX: Discord, GitHub, and Documentation Channels Explained

Users can access RenoDX community support through three primary channels: the official Discord server for real-time troubleshooting, GitHub Issues and Pull Requests for formal bug tracking, and the project's wiki and documentation for self-guided guides.

RenoDX is a community-driven mod-toolkit for DirectX games developed by clshortfuse. Whether you're building addons, debugging crashes, or setting up the development environment, understanding where to find help can save hours of frustration. This guide breaks down each support channel using actual source paths and community practices from the renodx repository.

Discord: The Primary Hub for Real-Time Support

The RenoDX Discord server serves as the main community gathering point. According to the source code, this is prominently linked throughout the project.

In src/web/static/index.html at line 104, the site footer contains a persistent "Discord" button that routes users directly to the community. The same invite appears in the README badge at line 3 of README.md. This design choice reflects Discord's role as the preferred channel for interactive, rapid-fire troubleshooting.

What Discord is best for:

• Live debugging of addon crashes or game-specific issues
• Quick feedback on work-in-progress mods
• Real-time discussion of devkit features and MCP bridge behavior

The CONTRIBUTING guide at docs/CONTRIBUTING.md (lines 18–20) explicitly directs contributors to Discord first for informal feedback before opening formal issues. This workflow prevents issue tracker noise and builds relationships between contributors.

# Quick reference: Discord invite as used in project scripts

$invite = "https://discord.gg/renodx"
Write-Host "Join the RenoDX Discord for live help: $invite"

GitHub Issues and Pull Requests: Structured Problem Tracking

For problems requiring a permanent record, GitHub Issues provides the formal support infrastructure. The repository at clshortfuse/renodx accepts bug reports, feature requests, and assistance requests through its issue tracker.

When reporting crashes, the community expects structured information. Below is a template pattern derived from common issue practices:

// Example: Reporting a crash via GitHub Issue
// Include this information in your issue description

**Title:** Crash on startup – [GameName] Add-on

**Environment:**
- RenoDX version: `git rev-parse HEAD` → `abcd1234`
- OS: Windows 10 10.0.19044
- DirectX version: D3D12 (feature level 12_1)

**Reproduction steps:**
1. Launch game with `renodx-devkit.addon64` loaded
2. Enable "HDR ReShade" toggle
3. Crash occurs after ~5 seconds

**Expected:** Game continues running with HDR overlay active
**Actual:** Immediate crash with error code `0xc0000005`

Pull requests follow a similar pattern. Contributors are encouraged to test changes against the CI pipelines in .github/workflows/ and discuss complex changes on Discord before submission.

Wiki and Documentation: Self-Service Resources

The RenoDX wiki hosts community-maintained addon listings and operational guides. The "Mods" wiki page catalogs third-party addons and links to their respective support resources.

Key documentation files include:

Document	Purpose	Location
docs/CONTRIBUTING.md	Contribution workflow, Discord routing	docs/CONTRIBUTING.md
docs/DEVKIT_MCP.md	Live-inspection devkit setup and troubleshooting	docs/DEVKIT_MCP.md
README.md	Project overview with Discord badge and CI status	README.md

The DEVKIT_MCP guide deserves particular attention for developers. It covers the Model Context Protocol (MCP) bridge used for live game inspection—a feature that generates many support questions. The document includes embedded troubleshooting notes for common connection failures.

Development Environment Setup Support

Before seeking help, verify your environment using the provided automation. The setup-dev-env.ps1 script in the scripts/ directory installs required tooling and can flag configuration issues early:

# Standard environment setup

.\scripts\setup-dev-env.ps1 -Install

# If issues persist after setup, create a GitHub issue with context

gh issue create --title "Build Failure After Setup" \
  --body "$(Get-Content .\environment_details.txt)"

CI pipeline failures in .github/workflows/ often trigger parallel Discord discussions. Checking both channels can reveal whether a build failure is local to your environment or affects the broader community.

Privacy and Data Handling

Users should note that src/web/static/privacy.html discloses Discord bot interactions as part of the support infrastructure. Automated tooling on the Discord server may process messages in public channels, though standard GitHub privacy practices apply to issue content.

Summary

• Discord (discord.gg/renodx) — fastest response for interactive troubleshooting; linked from README.md badge and src/web/static/index.html
• GitHub Issues — permanent record for bugs, crashes, and feature requests; use structured templates with version and environment details
• Wiki and docs — self-service guides including docs/DEVKIT_MCP.md for devkit operations and contributor onboarding via docs/CONTRIBUTING.md
• Setup scripts — scripts/setup-dev-env.ps1 automates environment validation before support requests

Frequently Asked Questions

Is there an official RenoDX Discord server?

Yes. The official Discord is linked through a badge in README.md at line 3 and a persistent button in src/web/static/index.html at line 104. The invite URL is https://discord.gg/renodx. The CONTRIBUTING guide at docs/CONTRIBUTING.md (lines 18–20) explicitly recommends Discord for initial support discussions.

Should I open a GitHub Issue or ask on Discord first?

For quick questions and live debugging, use Discord. For reproducible bugs, crashes with error codes, or feature requests that need tracking, open a GitHub Issue with environment details and reproduction steps. The CONTRIBUTING workflow directs contributors to Discord for informal feedback before formal issue creation.

Where can I find documentation for the RenoDX devkit?

The primary devkit documentation is in docs/DEVKIT_MCP.md, which covers the live-inspection tools and Model Context Protocol bridge. Additional operational details appear in docs/CONTRIBUTING.md. The project wiki also maintains a "Mods" page listing community addons with their support resources.

What information should I include in a support request?

Include your RenoDX version (from git rev-parse HEAD), Windows version, DirectX feature level, game title, and exact steps to reproduce. For crashes, provide the error code and whether the issue occurs with renodx-devkit.addon64 loaded. Mention any Discord discussion threads for context.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}