Scan functions for variables with the "in_" prefix and add them to parameters if found

[H-A-M-G-E-R]

The decompiler can miss input registers, e.g. "in_x8" in arm64 (mobile game smash hit)

[gemesa]

You can edit the function signature and fix it manually (according to the calling convention), e.g.:

[H-A-M-G-E-R]

but i want to automate that process

[DualTachyon]

Ghidra follows calling conventions for function arguments, the in_XXX means whatever code is using a different calling convention than is the default and it is your job to add the new calling convention to the project. You can manually edit it like gemesa suggested, or you can create a new calling convention spec file and import it to Ghidra.

[H-A-M-G-E-R]

this means that code using that function can't be recompiled, and i call them "invisible parameters"

[gemesa]

What do you mean? By fixing the function signature (and defining the necessary types, e.g. replacing undefined8 with the actual type) you can help the decompiler generate code that is nearly compilable. You might need to manually add some includes, declarations, etc.

[H-A-M-G-E-R]

compilers think that "in_" variables are uninitialized variables instead of parameters

[DualTachyon]

That's because Ghidra follows the calling convention applied to a function, and it doesn't know about the particular convention your binary is using. You can easily add a new compiler convention that supports your binary, and no fixes to Ghidra are necessary.