Riru VS Cocos2d

https://github.com/RikkaApps/Riru it is the precursor to zygisk. It should still work since the developer is still releasing modules that support it

That's not the best solution, but try Riru version of LSPosed. It requires an additional module (https://github.com/RikkaApps/Riru/releases), but if that would work for you, it's better than nothing.

Install Riru-Core: https://github.com/RikkaApps/Riru/releases.

Riru

(Get the Riru version if you are gonna use magisk v23, but you must install riru's main module before that: https://github.com/RikkaApps/Riru/releases ) (Get the Zygisk version if you are gonna use magisk v24)

Riru: https://github.com/RikkaApps/Riru/releases/tag/v26.1.3LSPosed : https://github.com/LSPosed/LSPosed/releases/tag/v1.6.0

Download the latest version of the Magisk module with an interesting name Riru and install it via Magisk

Xposed wont be updated after Android 7.0. So I use edxposed instead;Edxposed depends on Riru-core so install Riru-core first: https://github.com/RikkaApps/Riru/releases after downlad copy it into the phone install it by Magisk then restart(重启) download EdXposed https://github.com/ElderDrivers/EdXposed/releases/ Install EdXposedin the same way as installing Riru-core

That's all I can really tell you from what you've posted. The original version without the Blowfish encryption is open source (eg. https://github.com/cocos2d/cocos2d-x/blob/v4/cocos/scripting/lua-bindings/manual/CCLuaStack.cpp) , and I don't really understand how why you have so much symbol information available if what you're trying to disassemble isn't also probably open source

As others have pointed out, the biggest difference you're seeing is likely due to the _version_ of OpenGL (and hence GLSL) version. That said, there are still important differences. I'd recommend looking at a comparison between the same shader in a project that supports both OpenGL & OpenGLES. For example, here's a shader from cocos2d-x https://github.com/cocos2d/cocos2d-x/blob/v4/cocos/renderer/shaders/positionColor.vert. Note the only difference in this case is the additional precision qualifier (lowp) for v_fragmentColor. Note too how cocos uses preprocessor macros to handle this, so they don't have to maintain separate shader sources. Depending on your goals, you might be interested in tools like Nvidia cg or nvFX that allow for creating shaders in a dialect agnostic way, but ymmv.

Speaking about markdown files on GitHub, I know that there are some repositories that have very stunning README markdown files, such as this one for Cocos2d-x, whcih includes images in conjunction with text. I might do the same for my repository as well. Considering VS Code have an extension for .md files, this might come in handy when I consider using VS Code to contribute to my game projects.