tamaized / tammodized Goto Github PK

Crash with Sponge present: https://gist.github.com/LXGaming/27221c7988538504942bbb8cb2e66d49
Crash without Sponge present: https://gist.github.com/LXGaming/ac95a1a3be52ab92d4d9745fa29784f1

Mods:

• forge-1.12.2-14.23.2.2631
• spongeforge-1.12.2-2611-7.1.0-BETA-2975
• TamModized-1.12.1-0.15.5
• VoidCraft-1.12-0.26.10

TamModized version 1.12.2-0.15.6 causes most of Voidcraft's items to be unlocalized.

Perhaps create public final methods in AbstractProxy that invoke these and 3 other abstract methods for the normal proxy initializations. Only call the 3 public final methods within TamModBase.

We can also make the TamRegistryHandler field private and pass it along to the AbstractProxy methods, this can prevent other mods from invoking the AbstractProxy methods with the correct TamRegistryHandler that gets used for Models during registration.

Probably due to lighting issues.

Example: 0x000000FF is invisible even though the alpha value is 1.0F

To remove copy pasta

• TamItemShield class
• Hook into LivingAttackEvent and handle shield damage, use a List from the registry
• Have a parent JSON model maybe? Unsure.

Voidcraft was the only mod of mine that required it, but it can now handle this sort of thing on its own. There isn't a need to keep it here.

Add one for yourself that toggles server wide and have another option to disable them all together for your client alone. (Done in 3e0e371)

This is to avoid using supers

https://github.com/Tamaized/VoidCraft/issues/105

I would put something here on how to reproduce it but I'm a sad panda.

Forge: 2107
TamModized-1.10.2-0.2.2
VoidCraft-1.10.2-0.9.8
crash-2016-10-22_05.33.12-client.txt

to avoid supers

I18n.format(String, new Object[0]).toString().trim();

Move it here over from AoV

Tamaized.TamModized.helper.RayTraceHelper.getPlayerTraceVec(RayTraceHelper.java:22)