Support parameter mapping

[BlueStaggo]

Describe the enhancement
Allow the deobfuscator to give parameters names based on the mappings given just like it did in older versions. It has been like this for a while and I'm surprised there hasn't been an issue for this already.

Current behavior
Function parameters are called var1, var2, var3... regardless of whether mappings are provided for them.

RetroMCP Version
v1.2

Additional context
My test setup uses merged Feather mappings for 1.2.5 which does provide parameter names.

[PhoenixVX]

This is an RDI bug, not RetroMCP-Java.

I mentioned it a while back but haven't yet had time to look into it.

[PhoenixVX]

Started bisecting this issue more closely...

RetroMCP v1.0 was the version that stopped remapping parameters. v1.0-pre3 and before do correctly remap them. RDI is still adding the debug info in v1.0 and newer. Looking at the Fernflower options, it seems that ump (Reconstruct parameter names from debug info) does not appear to be in the Fernflower version used by v1.0 and newer.

Fernflower versions:
v1.0: Lassebq/Fernflower@3488141 (latest commit)
v1.0-pre3: Lassebq/Fernflower@d2244e1

The commit after v1.0-pre3's Fernflower version appears to have either moved a significant number of classes or is based off of a different version of Fernflower.

Attempting to replace latest commit of Fernflower with the one used in v1.0-pre3 leads to an exception. I will update as I know more.

[Reckobot]

words cannot describe my anguish