diff options
author | zaaarf <zaaarf@proton.me> | 2023-08-22 12:31:51 +0200 |
---|---|---|
committer | zaaarf <zaaarf@proton.me> | 2023-08-22 12:32:07 +0200 |
commit | 2201a9fe81881c2e5e84ae938ec4783921bffbce (patch) | |
tree | ad02e3e65e44fd473e7b7ae4eba3ebb7342f512f | |
parent | cd39918dd3fa2befa8ffc20c9351c0a1ebb94155 (diff) |
chore: readme update
-rw-r--r-- | README.md | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -30,13 +30,13 @@ dependencies { You are going to need an appropriate loader to use Lillero patches: **this is just a library and does nothing by itself**. You need to make it work by loading services implementing the `IInjector` interface, and by calling their `inject(ClassNode, MethodNode)` methods with the appropriate parameters. -Finally, know that you can spare yourself some trouble, by using this [annotation processor](https://git.fantabos.co/lillero-processor/) to reduce boilerplate to a minimum. +Finally, know that you can spare yourself some trouble, by using this [annotation processor](https://github.com/zaaarf/lillero-processor/) to reduce boilerplate to a minimum. #### Tips specific to Minecraft patching * You want to be using Notch (fully obfuscated) names whenever you are told to reference a class or method by name, since those are the ones that exist at runtime. - Use MCP (AKA unobfuscated) names if you are running from ForgeGradle's runClient task. - If you are using our loader (see below), use Searge (obfuscated but unique) names in every place you are told to use a name - ModLauncher will do the rest. -* Use our [loader](https://git.fantabos.co/lillero-loader/) that hooks into Forge's ModLauncher if you're writing a Forge mod. +* Use our [loader](https://github.com/zaaarf/lillero-loader/) that hooks into Forge's ModLauncher if you're writing a Forge mod. * Make sure to dunk on all the naysayers who tried to force you to use Mixin! #### Example Minecraft patch |