Easy way to disable individual core commands about klasa HOT 5 CLOSED

In master, you can use disableCorePieces: ['commands'] in client options to disable all built-in commands, you can transfer what you want to keep enabled.

from klasa.

There are ~16 core commands, and only ~2 commands I want to disable. That doesn't seem very ideal. Though it is a possible work around, though. Thanks.

from klasa.

Yeah, it's not a perfect solution, but you're not gonna get an option to disable specific commands only with this framework, they want you to transfer everything :/

from klasa.

I am not too keen on this idea, since it is one thing to skip walking a directory, but another to do O(n^2) searches on every piece loaded to see if it's not supposed to load, instead of the more OOP way where the piece knows if it should load or not (via the enabled property).

Generally speaking, the preferred way of accomplishing this right now is transferring the piece, disabling it (optionally you can remove everything but the constructor portion of the class), and optionally moving it to a disabled folder, so it's out of sight/out of mind.

from klasa.

But in a disabled folder, it's not exactly out of sight. I understand what you mean in terms of OOP, but you can't change the prop for it without moving it into the working directory.
I don't mind anymore though, I used ShayBox's solution, it's all good now.

from klasa.