I should have made it clear from the beginning since that word is very tied to garbling code form. Obfuscation can also be achieved in simpler ways, where the specific function, body, or logic changes with each iteration - not necessarily encoding it. You can change the function name to different variations of the same name, you can split the function into two or more code blocks instead of having it all in one, changing the position in the code, etc. It’s a lighter obfuscation than what the word is usually used for, and it wouldn’t go against AMO’s rules, and would make it harder for blind copy-cats to patch it every single time.
I see, so it’s the opposite of what I interpreted, applications is legacy, not V3. Thanks for making that clear.