reone VS Cocos2d

Reone, an open source engine for KotOR 1 and 2, has made a lot of progress the last few years. Looks like new development is on hold for a codebase cleanup, but the dev has been at it for a long time, so I imagine he'll finish eventually.

If you can read C++, you can read the reimplemented stuff in the xoreos-tools or xoreos itself. There's also a similar reimplementation project just for KotOR, reone.

I would suggest keeping an eye out on this project: https://github.com/seedhartha/reone It's a remake of the kotor engine, and they have a real-time combat mod planned for it, but it might take quite a while.

As you may know, reone is an open-source reimplementation of KotOR and TSL, that has been in development since summer, 2020. It has recently reached its first major milestone, which is making the Endar Spire level completable (but beware of bugs!). Here's the projects YouTube channel, where you can see the engine in action.

https://xoreos.org/ and https://github.com/seedhartha/reone

kotor got an open source engine built for it on github not quite a remake though

There is xoreos and reone, but I'm not sure how far along they are.

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.