Closed ZeLarpMaster closed 3 years ago
A simple fix I'd see is removing the .resolve()
in remove_path.
The path literally comes from a pop of the list at the given index, so I don't see why we'd need to resolve it again. If remove_path is called from elsewhere, it should be giving a valid path already (and otherwise will receive an exception).
Command bugs
TL;DR: Answer to this is yes, because, when removing it, this causes this to not find the path.
Command name
[p]removepath
What cog is this command from?
CogManagerUI
What were you expecting to happen?
The specified path to be removed
What actually happened?
How can we reproduce this issue?
[p]addpath <valid Windows path>
[p]paths
[p]removepath
with the number of the Windows path