Closed Taskeren closed 2 months ago
Yes, it should be regulated by the naming style. The entire point is that using simple names will cause conflicts between mods. Both the name in your interface and in your mixin need to be prefixed.
Yes, it should be regulated by the naming style. The entire point is that using simple names will cause conflicts between mods. Both the name in your interface and in your mixin need to be prefixed.
Sorry, I'm not very good at Mixin. How can I make the implement methods naming in that style without errors? Is that @Implementation
annotation? I don't see any document about Mixin use it.
Both the name in your interface and in your mixin need to be prefixed.
You put your modid or similar in front of their names.
But what if the interface is not MY custom one, but in other dependencies?
It's likely not advisable to implement interfaces from other dependencies into Minecraft classes, in case other mods try to do the same thing. If you are having this problem a lot, you can go into the settings for this inspection and disable the option for inherited methods.
Thanks for answering! I see the recommended way to do this.
But can it be inspected separately, like have different options for methods from interface and methods injecting?
Minecraft Development for IntelliJ plugin version
2024.2-1.8.1
IntelliJ version
2024.2.0.2
Operating System
Windows 11
Target platform
Mixins
Description of the bug
getSomeString
is defined in the custom interfaceISomeInterface
, which is used for Interface Injection.It should not be regulated by the naming style.