haykam821

Messages sent from Telegram incorrectly format strong emphasis

1

CommonMark [defines `**` as indicating strong emphasis](https://spec.commonmark.org/0.30/#can-open-strong-emphasis): > 5. A double ** [can open strong emphasis](https://spec.commonmark.org/0.30/#can-open-strong-emphasis) iff it is part of a [left-flanking delimiter run](https://spec.commonmark.org/0.30/#left-flanking-delimiter-run). However, Matterbridge instead uses `*`...

Map the RedstoneConstants class

3

This is likely to be a class holding redstone constants for the following reasons: - Redstone is one of the two major mechanics that could be considered large enough to...

Two classes extend the `SpriteAtlasHolder` class: `PaintingManager` and `StatusEffectSpriteManager`. The former name is very unclear as it doesn't imply that the class deals with textures at all, and is inconsistent...

Droppers should be fully documented in `getDroppedStacks`, `LootContext.Builder`, and `LootContext.Dropper`.

Vector classes have inconsistent multiplication method naming

1

I consider the `Vec3d` class the baseline for vector naming, so I will list deviations from its standards: - `Vec3f#multiplyComponentwise(FFF)` should match `Vec3d#multiply(DDD)` - `Vec3f#scale(F)` should match `Vec3d#multiply(D)` If the...

Tessellation is misspelled as 'tesselation'

1

The `RenderSystem.RENDER_THREAD_TESSELATOR` field and `RenderSystem.renderThreadTesselator` method both misspell 'tesselation'. While the crash report message makes this same mistake, other Yarn names, such as the `Tessellator` class, fix this typo.