Commands which should be active aren't active
Shotix opened this issue ยท 1 comments
Summary
Some commands which are already working are still in an inactive state.
Expected Behavior
The commands should be usable without the necessity to enable them first
Actual Behavior
You have to manually enable the commands for them to work
Environment
- CustomWhitelistV2 Version: 0.2.1
Fixed in fd42247