Choonster
Moderators
-
Joined
-
Last visited
Everything posted by Choonster
-
Use the static methods in ResourceLocation to create an instance. -
Duplicate of the following topic:
-
-
Try using 1.20.6-50.0.5, it just fixed an issue related to enchanting: https://github.com/MinecraftForge/MinecraftForge/commit/0e829630da67c91d2b5a91ea4b65eb033f868e76
-
This has been released as 49.0.49.
-
This PR may fix the remaining issues here. It's still under review and hasn't been released yet, but may be merged and released in the next few days or so.
-
Try using 49.0.47 or later, it fixed an issue like this: If that still doesn't work, post your logs as described in the FAQ at the top of the forum.
-
Duplicate of the following topic:
-
Please don't post your email address publicly. I've removed it from your post.
-
Duplicate of the following topic:
-
Duplicate topic.
-
-
The bots have been banned.
-
Duplicate of this topic:
-
Read Paint_Ninja's message again, there's an additional requirement that you're not meeting.
-
Use DamageSource#getDirectEntity to get the projectile entity.
-
The debug.log includes the crash report and other information, there's no need to post crash reports separately. Regardless, 1.16.3 is no longer supported on this forum.
-
It's entirely possible for crafting table recipes to customise their output (including setting NBT/damage) by overriding IRecipe#assemble. I have a recipe that does a similar thing for armour here.
-
ServerChatEvent was overhauled in the 1.19.1 update to support the secure chat system, it's probably not going to be possible to fix this without updating to 1.19.1 or 1.19.2.
-
If you look at the loot table for cows, you'll see that it checks whether the entity is on fire to determine whether to drop steak; not whether the tool has Fire Aspect.
-
I never found a way to ignore the errors; but I eventually replaced HWYLA with Jade, which doesn't have this issue.
-
Instead of using an interface and extending the vanilla entity classes, could you use a capability? You could have a base class with the shared logic and then entity-specific implementations attached to different entity classes. If you need to do stuff every tick, you'd need to use LivingUpdateEvent.
-
ObfuscationReflectionHelper methods always take SRG names, even in the development environment. In development, the SRG name is automatically remapped to the corresponding MCP name.
-
The second argument of withExistingParent is the path to a model file to use as a parent, not a texture. For basic block items, the model normally uses the block model as the parent, rather than specifying individual textures. I use this helper method in my BlockStateProvider implementation to generate block item models that simply extend the block model. You can see an example of this here. On a side note, the DeferredRegister instance should always be created in the same class as it's used in; don't put the DeferredRegister and RegistryObject fields in separate classes.
-
NBTIngredient doesn't have an of method itself, you're actually calling Ingredient.of. You need to create an instance of NBTIngredient directly (or a class that extends it, since the constructor is protected).
