Merge branch 'main' of https://git.hudsonriggs.systems/HRiggs/ProgressionMods

.gitignore

@@ -0,0 +1,203 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+#   in version control.
+#   https://pdm.fming.dev/#use-with-ide
+.pdm.toml
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be added to the global gitignore or merged into this project gitignore.  For a PyCharm
+#  project, it is recommended to ignore the entire .idea directory.
+.idea/
+
+# VS Code
+.vscode/
+
+# macOS
+.DS_Store
+.AppleDouble
+.LSOverride
+
+# Windows
+Thumbs.db
+Thumbs.db:encryptable
+ehthumbs.db
+ehthumbs_vista.db
+*.tmp
+*.temp
+Desktop.ini
+$RECYCLE.BIN/
+*.cab
+*.msi
+*.msix
+*.msm
+*.msp
+*.lnk
+
+# Linux
+*~
+
+# Temporary files
+*.swp
+*.swo
+*~
+
+# Logs
+*.log
+
+# Application specific
+# Keep art assets but ignore any generated thumbnails or cache
+art/cache/
+art/thumbnails/
+
+# Steam Workshop related (if any cache files are generated)
+workshop_cache/
+*.cache

README.md

@@ -1,80 +1,9 @@
-# Steam Workshop Collection Manager
+# Progression: Loader
 
-A Python GUI application for extracting Steam Workshop mod IDs from RimWorld mod collections with configurable settings.
+This project pulls from the three steam workshop collections of Progression, then it searches through your installed mods, in the workshop folder and matches the steam id to a package id, and Formal name, then it takes those names, package ids and steam ids and creates the modloader modslist, thats a mouth full, and save it to your modslist fodler so all you have to do is launch the game. The merge button will take your currently ENABLED mods and merge them with the latest progression pack to give you a new modslist called progresisonhomebrew which you can sort and load.
 
-## Features
 
-- Dark themed Windows-style GUI
-- Configurable collection URLs via .env file
-- Automatic workshop path derivation from RimWorld game path
-- ModsConfig.xml integration for active mod tracking
-- Real-time output display with scrollable text areas
-- Local mod folder listing and comparison
-
-## Installation
-
-1. Make sure you have Python 3.6+ installed
-2. Install required dependencies:
-   ```
-   pip install -r requirements.txt
-   ```
-
-## Configuration
-
-The application uses a `.env` file for configuration. You can modify the default settings:
-
-```env
-# Default Collection URLs
-CORE_COLLECTION_URL=https://steamcommunity.com/workshop/filedetails/?id=3521297585
-CONTENT_COLLECTION_URL=steam://openurl/https://steamcommunity.com/sharedfiles/filedetails/?id=3521319712
-COSMETICS_COLLECTION_URL=steam://openurl/https://steamcommunity.com/sharedfiles/filedetails/?id=3637541646
-
-# ModsConfig.xml Path Template
-MODSCONFIG_PATH_TEMPLATE=%USERPROFILE%\AppData\LocalLow\Ludeon Studios\RimWorld by Ludeon Studios\Config\ModsConfig.xml
-```
-
-## Usage
-
-1. Run the application:
-   ```
-   python steam_workshop_gui.py
-   ```
-
-2. **Set RimWorld Path**: 
-   - Right-click RimWorld in Steam → Manage → Browse local files
-   - Copy and paste that path into the "RimWorld Game Folder" field
-   - The workshop path will automatically derive to `steamapps\workshop\content\294100`
-
-3. **ModsConfig.xml**: 
-   - The path is automatically detected
-   - You can manually edit if needed
-   - Click "Load Active Mods" to see currently enabled mods
-
-4. **Collection Analysis**:
-   - Modify collection URLs or use defaults from .env
-   - Click "Extract Workshop IDs" to process collections
-   - See which mods are [INSTALLED] or [MISSING]
-
-5. **Local Mod Management**:
-   - Click "List Local Mod Folders" to see downloaded workshop mods
-   - Compare with collection requirements and active mods
-
-## File Structure
-
-- `steam_workshop_gui.py` - Main application
-- `.env` - Configuration file
-- `requirements.txt` - Python dependencies
-- `README.md` - This file
-
-## URL Formats Supported
-
-- Standard Steam Workshop URLs: `https://steamcommunity.com/workshop/filedetails/?id=XXXXXXXXX`
-- Steam protocol URLs: `steam://openurl/https://steamcommunity.com/sharedfiles/filedetails/?id=XXXXXXXXX`
-
-## Notes
-
-- All paths are editable in the GUI
-- Configuration URLs are loaded from .env file on startup
-- Workshop path auto-derives from RimWorld path (steamapps\common\RimWorld → steamapps\workshop\content\294100)
-- Processing may take a few seconds depending on collection size
-- Workshop IDs are extracted from HTML content of collection pages
+DLC detection is based on NotOwned_x.png if the user doesnt the same package NAME as the not owned png it doesnt proceed. 
+.envs populate pre loaded data, only change if their is an update to collection url
+Doesnt sort so the current guidence to autosort from base game mod manager will still apply.
+Art by ferny

requirements.txt

@@ -1,3 +1,4 @@
 requests>=2.25.1
 python-dotenv>=0.19.0
-pyglet>=1.5.0
+pyglet>=1.5.0
+Pillow>=8.0.0