Standardize usage of final classes, private constructors, @SuppressWarnings, and @ApiStatus about plume HOT 3 OPEN

@SuppressWarnings

Having worked by myself for a while, my usage of this is kind of instinctive, but the basis is 'if it's creating an unnecessary warning, add a suppression'

• if it's a block/item etc that's made to be used by other mods, @SuppressWarnings("unused")
• if there's a deprecation, and it's one of Mojang's weird formatting deprecations or quite frankly anywhere actually, ew, get it out of here, @SuppressWarnings("deprecation")
• if there's some mixin-based confusion with an editor, like casting, suppress the warning
• or essentially anything that's giving you unnecessary warnings that you don't want to disable inspections for completely

from plume.

Do you generally look at warnings when writing code? I've grown to just institutionally ignore them, but I do get where you're coming from

from plume.

I'm one for a clean warnings gutter lmao

from plume.