From dc885fffae17bd32ef3c8396f789b3eba641f720 Mon Sep 17 00:00:00 2001 From: zaaarf Date: Sat, 14 Dec 2024 23:17:19 +0100 Subject: [PATCH] docs: mention mapper in readme --- README.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 3d2266e..530a63e 100644 --- a/README.md +++ b/README.md @@ -151,7 +151,7 @@ Most if not all of this (although I have not tested it) should apply to local cl ### Hybrid setups Sometimes, you may want to manually write IInjectors yourself in a project which also uses the processor. In these cases, you don't want to create the service provider (the `META-INF/services/ftbsc.lll.IInjector` file) yourself, to -void conflicts. Simply add the annotation `@RegisterBareInjector` on top of the IInjector class(es) you wrote. +avoid conflicts. Simply add the annotation `@RegisterBareInjector` on top of the IInjector class(es) you wrote. ### Obfuscation support You may pass a mappings file to the processor by adding this to your `build.gradle`: @@ -161,9 +161,7 @@ compileJava { //mappings for lillero-processor options.compilerArgs << '-AmappingsFile=remote_url_or_local_path' } ``` - -This feature is in a very early stage, and currently only works with TSRG files (Minecraft MCP to SRG mappings). More -formats will be added in the future - possibly as a separate library the processor will rely on. +This feature is powered by [Lillero-mapper](https://github.com/zaaarf/lillero-mapper). It supports multiple formats; my personal recommendation is `tinyv2`, but see the project's README for more information. ### Other processor arguments In the same way you pass mappings, you may pass `false` or `0` to the boolean arguments `badPracticeWarnings` and