Closed SerRipsen closed 7 months ago
Thanks for the heads up!
@DomicidalDesigns, could you look into this?
I have also removed the files for the program and redownloaded the latest release to be sure the files I'm using are not edited in any way, and I still have the same effect. I checked the output logs for the feature and it only seems to show the Add commands in the logs, not the Remove commands. However, the Remove commands do work, if I run a single set of Remove and then restart the server, it will correctly update the .ini file. Then after booting, running any command introduces the issue again. Very confused!
I am closing this issue as there have been no update for a long time.
Hey, I've run into a very strange bug whilst using this tool. When doing !add or !remove_workshop_mod, there appears to be a strange cache of 8 or so mods that are stuck in the system. I'll try to explain what's happening concisely.
I have a bunch of mods that seem to appear no matter what I do. This output below is contiguous, I have added spaces to denote each individual command.
The discord commands I used are the full commands with the links, I'm just abbreviating here for human reading.
The commands are; !add "TakeAnyAmount" !remove "MinimalDisplayBars;ScrapArmor(new version);ScrapGuns(new version);ScrapWeapons(new version);BetterExerciseEasy;CombatText" !add "TakeAnyAmount"
The important information to note here: When using !add "TakeAnyAmount" the first time, I had gone to the server.ini file and deleted ALL mods and workshop IDs. The starting server.ini file is empty. When using !remove for the list of items, it clearly shows these are all successfully removed. When using !add "TakeAnyAmount" for the second time, all those items have come back again.
Just to be plain here, if I choose to !remove half the mods, then !remove the other half, the second command's output will show the first half of the mods in the list again. It's like there is some sort of cache remembering the mods and bringing them back.
I have done several !stop_server and !restart_server to see if this resolves and no luck.