Framework Overhead

[asofold]

It is important to keep the "runtime overhead" of the framework as small as possible.

The registration may cost a little more, but things like getting check-specific config/data and accessing their properties, exemption checking, violation handling and processing listeners must perform pretty well.

[MyPictures]

Experiments and test will show :P

[SuperSpyTX]

Are we looking to sacrifice RAM for this? Or are we trying to use as little RAM as possible?

Because caching sounds like the best way to go.

[asofold]

We do have to keep an eye on RAM as well. Though in the contexct of java and anti-cheat stuff for Minecraft i would rather sacrifice a little RAM to gain speed, since we have to do a lot of per-player calculations in real-time.

For often used objects for astraction layers we could consider using caching or better: pools.

It must be 100% clear from the API / typical use which objects are not to be stored (e.g. a moving event container) and how to obtain objects for local storage.