We want to help you get the most out of WOG Dump! This document provides guidance on how to get support for any issues you might encounter.
Please try these steps first:
- Check the README - The
README.mdcontains comprehensive installation and usage instructions - Search Existing Issues - Check if your question or issue has already been reported in our GitHub Issues
- Read the Documentation - Browse through our project documentation
- Check the Troubleshooting Section - Common issues and solutions are documented in the README
When reporting a bug or issue, please include:
- Operating System: (e.g., Windows 10, Ubuntu 22.04, macOS 13.0)
- Python Version: Run
python --versionorpython3 --version - WOG Dump Version: Run
wog-dump --version - Installation Method: (pip, uv, git clone)
- What you were trying to do: Clear description of your goal
- What you expected to happen: Expected behavior
- What actually happened: Actual behavior with error messages
- Steps to reproduce: Exact commands and actions that led to the issue
- Full error message: Copy the complete error output
- Log files: Include relevant log files from the
logs/directory - Screenshots: If applicable, especially for CLI output
**Environment:**
- OS: Ubuntu 22.04
- Python: 3.12.1
- WOG Dump: 2.3.2
**Description:**
When running `wog-dump download-assets`, the tool crashes with a connection error.
**Expected Behavior:**
Assets should download successfully.
**Actual Behavior:**Error: Connection timeout after 30 seconds Traceback (most recent call last): ...
**Steps to Reproduce:**
1. Run `wog-dump download-weapons`
2. Run `wog-dump download-assets`
3. Error occurs
**Additional Context:**
- Internet connection is stable
- First time using the tool
- Bug Reports: Create a new issue
- Feature Requests: Create a new issue with the "enhancement" label
- Questions: Browse existing discussions or create a new issue
- Search First: Use GitHub's search to find similar issues
- Be Specific: Provide detailed information to help others help you
- Be Patient: This is an open-source project maintained by volunteers
Q: I get "command not found" when running wog-dump
A: Make sure you've installed the package and it's in your PATH. Try:
pip install -e .oruv pip install -e .- Check if
~/.local/binis in your PATH (Linux/macOS)
Q: Import errors about missing modules A: Install all dependencies:
pip install -r requirements.txt # or uv pip install -e .Q: Downloads are very slow or timing out A: Try these solutions:
- Use fewer threads:
wog-dump --max-threads 2 download-assets - Check your internet connection
- Try downloading specific weapons instead of all at once
Q: Decryption fails with "Invalid key" error A: Update your keys:
wog-dump download-assets --update-keysQ: UnityPy errors during unpacking A: Make sure you have the latest version:
pip install --upgrade UnityPyQ: How can I contribute to the project?
A: See our CONTRIBUTING.md guide for detailed instructions.
Q: Can I use this in my own project?
A: Yes! WOG Dump is MIT licensed. See LICENSE for details.
# Check configuration and system status
wog-dump info --verbose
# Test with debug logging
wog-dump --debug info
# Verify installation
python -c "import wog_dump; print('Installation OK')"WOG Dump creates log files in the logs/ directory:
wog_dump.log- General application logsdebug.log- Detailed debug information (when using--debug)
Clear cache and restart:
rm -rf runtime/cache/ # Linux/macOS
rmdir /s runtime\cache # WindowsReinstall dependencies:
pip uninstall wog-dump
pip install -e .Reset configuration:
rm -f config.json # Will regenerate with defaults- Project Maintainer: InzGIBA
- Email: inzgiba@gmail.com
- GitHub: @inzgiba
- Bug Reports: We aim to respond within 48 hours
- Feature Requests: We'll evaluate and respond within a week
- Security Issues: Please email directly for faster response
If you're an experienced user, you can help the community by:
- Answering questions in GitHub Issues
- Improving documentation
- Contributing code fixes
- Testing new features
Remember, every contribution helps make WOG Dump better for everyone!
Note: For security-related issues, please email inzgiba@gmail.com directly instead of creating a public issue.