Workaround handling

[MyPictures]

Since NoCheat 4 will be easy to extend with new checks I was asking myself how we want to handle workarounds within checks of it.

Will we implement them directly into the checks or will they be separated from the checks and work/run in-depended if the check is active or not?

For example lostOnGround workaround in NoCheatPlus is still useful even if someone decides to remove the SurvivalFly check out of NoCheatPlus.

[asofold]

On-demand services can be removed if they are unused.

In general this is a somewhat interesting question, if we use with a digest-object for moving checks (so we would not need to check the same permissions three times etc.), then the lostground workaround might indeed be possible to split off survivalfly and put before it, so the workaround modifies the moving data.

[MyPictures]

I guess it makes sense to have workarounds on top of all checks then. okay.