stencyl-engine VS Cocos2d

as for my 2D engine I am using Stencyl as it has a way to use blocks for programming and you could write out the code if you wanted to, it can create games that can be put in market places as well.

Stencyl is a really easy game engine to use. https://www.stencyl.com/ you can probably bang out a few quick games with it as you follow their tutorials.

Try Stencyl .

He used Stencyl

Stencyl! Build on Scratch but way more capable.

For an easy start in game developing, I would suggest to try GDevelop or Stencyl. Both are an easy option to start from 0. Once you get a grasp on programming logic and how to do some basic things, you can move to other engines if you want to do things in 3D.

Never heard of stencil.. but I have heard of stencyl. Maybe it is a variation of it?

If you're not the sociable type (you'll have to work on that because game making is first and foremost team work, but I understand it might be hard if you feel like you're not skilled enough), a lot of solutions exist to easily make your own games on your own, like Stencyl, or Adventure Game Studio. They'll barely require any technical knowledge, but if you really want to focus on writing, then you can even go with text-only tools such as Twine or Ink/Inky.

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.