You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If REMOVE_OLD_MODS: "true" then the mod is added to the mods folder, but then it is deleted before the server starts. I don't think this deletion is correct, as the mod isn't "old"; it doesn't make sense to add then immediately remove that same mod. Perhaps I'm misunderstanding something.
Specific process to prove / reproduce:
In one terminal, run a command to see the changes in the files in the directory, filtered by biomes o plenty.
Describe the problem
Starting with a directory containing three files:
.env
includes the CF_API_KEY as usualcompose.yml
(below), andmanifest.json
(below)Container definition
Container logs
If
REMOVE_OLD_MODS: "true"
then the mod is added to the mods folder, but then it is deleted before the server starts. I don't think this deletion is correct, as the mod isn't "old"; it doesn't make sense to add then immediately remove that same mod. Perhaps I'm misunderstanding something.Specific process to prove / reproduce:
In one terminal, run a command to see the changes in the files in the directory, filtered by biomes o plenty.
Then in the other, start it up:
Wait for the server to finish booting, then ctrl-c on the docker compose, then ctrl-c on the watchmedo.
changes.log
looks like this (shows the creation and deletion):The text was updated successfully, but these errors were encountered: