Closed cypai closed 1 year ago
That exception occurs when a mod's metadata file contains invalid XML. I'll publish a patch that will have rmm ignore mods with invalid metadata and release it by end of day so that rmm will be usable for you.
Do you have a list of what mods you have installed? I'd love to take a look at the file which is causing the issue.
I've published the changes. I'm going to close this because the issue is fixed but I'm still interested in the additional information. 630a9dfee5ebbdf7920bb0105c494a68917ec0dd
With regards to the dependencies with pyenv, rmm has a Pipfile in the source code. It is the recommended way to manage dependencies in Python right now, afaik. Install pipenv in your pyenv and then use pipenv install
Description None of the commands work. Logs below:
Was installed via the AUR. Needed to manually install dependencies with pip due to use of pyenv instead of system Python.
All 3 environment variables were set to their respective directories, and the ModsConfig.xml was set to the default no mods version by RimWorld.
Reproduction Run any command, above was
rmm list
.Info OS: Arch Linux RimWorld version: 1.3.3326 rev564