Leaderboard

Hi I think I read somewhere that Forge states have been removed, your documentation may be out of date (that happens a lot) Ah yeah here's the link https://gist.github.com/williewillus/30d7e3f775fe93c503bddf054ef3f93e -TGG

Hi In that case I think the easier way will probably be to recreate the functionality in PlayerEntity::attackTargetEntityWithCurrentItem() i.e. copy and paste and remove the bits that aren't relevant or that actually do the damage Not ideal because you will need to update it every time Minecraft updates a version, but you'll be doing that for half your code base anyway. -TGG

Everything you want to do is possible, but I’m general it causes bad things to happen and is highly discouraged. If you want to do what you’ve mentioned right and compatibly it will require quite a bit of work to do right as you will need to deal with situations where objects haven’t been registered when a client connects to a sever. How are you planning on handling this? You’re also going to need to handle all assets (models, textures) and data (recipes) in a compatible way that allows them to be overriden by resource and data packs. If you’re trying to register objects only if another mod is present, there are other, more compatible ways of adding mod-specific content. You’ve been meant to use the registry events since 1.7.10. If everybody used the registry events correctly, dynamic registration would be possible, but people don’t and therefore supporting universal dynamic registration becomes impossible. If you were a bit more clear about what you were doing and why you might find that people were more helpful. For example instead of saying “I want to do something that is discouraged because of how difficult it is to do right and incompatible with badly made mods it is” you could lay out why you want to do this, what you plan on doing in your mod and how you’re planning on handling edge cases (such as unregistered objects on connection) to ensure that everything continues to work properly.

Based on knowing for sure it was a ForgeGradle bug, I was able to binary-search for a working version. Changing the ForgeGrade version in the classpath dependencies at the top of the build.gradle file from '3.+' to '3.0.145' makes it work again, in 1.13.2 and 1.14.3 (and presumably 1.14.2). This is the last version that works, 3.0.146 is the Maven version that first includes the bug.

1.8 is no longer supported on this forum. Please update to a modern version of Minecraft to receive support.