Epilogue creates duplicate NT entries in kotlin.

[falOn-Dev]

Describe the bug
When epilogue is used with kotlin, it generates two NT entries for every field. One is called field and one is called getField. For some reason even when kotlin gets compiled to bytecode with simple getters (just a function with return this.whatever) it still gets logged. I've been told that's not supposed to happen. For fields with no custom getter you can annotate @JvmField to fix this issue, but you can't utilize a custom getter, and epilogue, without duplicates.

To Reproduce

1. Set up a kotlin FRC project
2. Register epilogue with Kapt (to allow java annotation processors to process kotlin code)
3. Log some stuff

• Link to code: https://github.com/falOn-Dev/2025Reefscape_Epilogue

Expected behavior
I expected epilogue to not generate duplicate entries in NT when logging.

Desktop (please complete the following information):

• OS: Arch Linux
• Project Information: WPILib 2025.3.2, WPILib's 2025 JDK

Additional context
I understand if this issue gets closed nearly instantly, as kotlin is not officially supported. However I would really like to explore the use of epilogue in kotlin, and fixing this would be huge.

[falOn-Dev]

I think the easiest way to solve this would be: If a class has @Metadata (automatically part of all kotlin class files, unique to kotlin unless manually added to a java filed) then ignore fields, log the getter methods, and drop the get prefix

[falOn-Dev]

In general there seems to be tons of issues with detecting and logging things in kotlin. Tagging with @JvmSynthetic causes the duplicates to no longer appear, but it also makes some (but for some reason not all?) of the logged variables no longer update. Also, variables from an abstract parent class only get logged if they're overriden, even when both classes are tagged @Logged (might be intentional?)

[falOn-Dev]

The only way to avoid logging twice, and use custom getters (from what I've found), is to annotate with NotLogged for every field