After the cosmetics pr is complete, we should standardize the uses of these language features.

Final Classes

I'm for removing all our final class uses. It's pointless to use imo.

Private constructors

I think that all of our static-only method classes should have a private no argument constructor.

@SuppressWarnings

I usually don't ever use these, so I'd like feedback on how we should standardize its usage. Right now it feels like @andantedevs is adding them kinda at random rather than every time they could be used.

@ApiStatus

I think we should take full use of this annotation. I think it might break compatibility with non-jetbrains editors, but I'm not too worried for that tbh

Expected Behavior

The donkey pack texture should be custom per modded chest.

Current Behavior

The vanilla donkey pack texture is rendered.

Possible Solution

Use stored modded chest variable from an implemented #7 in the donkey renderer to render a different texture.

• config file loading
• config screen functionality, syncing between client/server
  • can be client-only/server-only

Expected Behavior

If you equip a modded chest to a donkey, the donkey should drop the modded chest when killed.

Current Behavior

A vanilla chest drops when the donkey is killed.

Possible Solution

Store the chest type in the donkey entity.

Feature Description

When a modded chest with the wooden_chests tag is fired from a dispenser with a donkey in front, the donkey should be equipped with the modded chest.