Support parameter mapping #229
Description
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.