jorphi

Just wanted to provide what I think should be a solution for this. I simply switched to a different container ("red-discordbot" by Selfhosters), which seems to have a persistent path. I haven't been able to test it with updates yet, but it actually creates a mapped folder in appdata with cogs and configs visibly inside it. I believe this should fix our issue and it is fundamentally the same container. (Just copy the same discord token from this container's template, delete this one, and input that token into the new container) EDIT: Upon testing after a redbot update. this alternative container does keep previous configs/cogs. Would recommend switching to it for now.

Also having this issue, all cogs and settings are reset upon updating. The redbot github page is no help, could this be due to the VENV that redbot is "required' to run in? Would really love a solution for a persistent data path since I keep having to re-load all cogs and settings after each update.