Accessors

@Accessors allow us to get and set private target fields without needing to use an access widener or access transformer in most cases.

Say the following class existed:

public class Dummy {
    private int dummyField;
    ...
}

We can create accessors for both getter and setters as so:

@Mixin(Dummy.class)
public interface AccessorMixin { // accessor classes are interfaces!!!
    @Accessor("dummyField") // specifying the field is not stricly required if we follow the naming convention below
    int modid$getDummyField(); // we should always name getters as get[NAME]

    @Accessor("dummyField") // specifying the field is not stricly required if we follow the naming convention below
    void modid$setDummyField(int value); // we should always name setters as set[NAME]
}

We can then use these like so:

public void myMethod() {
    // Getting the field
    int i = ((AccessorMixin) Dummy.getInstance()).modid$getDummyField();

    // Setting the field
    ((AccessorMixin) Dummy.getInstance()).modid$setDummyField(i + 1);
}

If we can't getInstance, we can cast to Object instead.

public void myMethod(Dummy dummy) {
    // Getting the field
    int i = ((AccessorMixin) (Object) dummy).modid$getDummyField();

    // Setting the field
    ((AccessorMixin) (Object) dummy).modid$setDummyField(i + 1);
}

Remember that we can only have one method with the same name, parameters, and return type in a class. This is why we prefix our invoker field with "get" or "set" as these are the only two prefixes Mixin supports as mentioned in the comments. If we wanted, we can get around this by specifying the field in the annotation. While prefixing accessors with our modid is not strictly required if they are static or if the name you chose doesn't already exist in the target method or any other mods that may add it, it is the best way to ensure that there are no collisions, and I recommend you add them unless you know they are not required.

Also, make note again that the class type is an Interface for the accessor Mixin. This means that even if we already have a Mixin for this class for regular injections, we would need a second Mixin for this class for accessors.

This page is directly based off of dblsaiko's Mixin Cheat Sheet page for Accessors.