Differences

This shows you the differences between two versions of the page.

--- tutorial:mixin_accessors [2025/11/30 20:07] – Applied TargetClassAccessor naming convention to all examples, removed the modid$ suffix for static accessor/invoker handlers. gauntrecluse
+++ tutorial:mixin_accessors [2026/06/30 12:27] (current) – Add redirect header to new Docs page gauntrecluse
@@ Line 1: / Line 1: @@
+~~REDIRECT>https://docs.fabricmc.net/develop/mixins/accessors~~
 ====== Accessor Mixins ======
@@ Line 8: / Line 10: @@
 ''@Accessor''s and ''@Invoker''s can infer the field/method name if they are called ''getFieldName'' / ''call/invokeMethodName'', omitting the requirement for the ''value'' attribute to be specified, however, all non-static handlers should be prefixed as so: ''modid$getFieldName'' instead. This is because when the **Accessor Mixin** is merged the handler will remain unchanged and if there is a problem related to the handler, it's useful to know who owns it. Additionally, if another mod decides to create a Duck interface with a method called ''getFieldName'', when that is merged alongside your **Accessor Mixin** whichever one applies last will overwrite the other and you end up with a conflict that may crash or cause unintended behaviour.\\
-Prefixing handlers is not necessary if they are static, as those may not conflict, and the stacktrace provides the Mixin class whose handlers are involved in errors, thus making it sufficient without needing to prefix with the modid.
+Prefixing accessor or invoker handlers is not necessary if they are static, as those may not conflict, and the stacktrace provides the Mixin class whose handlers are involved in errors, thus making it sufficient without needing to prefix with the modid.
 ===== Accessor =====