When comparing Leadwerks vs ct.js, the Slant community recommends ct.js for most people. In the question“What are the best game engines for beginners and non-programmers?” ct.js is ranked 23rd while Leadwerks is ranked 36th. The most important reason people chose ct.js is:
ct.js is bundled with examples, docs, and easy to follow tutorials. Documentation and tutorials are available in a side panel on every screen.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Very good entity system, did have GUI functions, easy to use terrain editor with vegetation system.
Good API tutoials, workshop elements which can be loaded from steam.
Pro Both Windows and Linux supported
Pro Built-in level editor
Has an acceptable 3D map editor that is easy to use.
Pro Versatile flow diagram script model
Leadwerks's flowgraphs resemble flowcharts where each box represents a function or value, with connections between them representing program flow. This provides a better at-a-glance indication of game logic than a simple list of events, and makes complex behaviors easier to accomplish.
Pro Community forum offers plenty of support
It makes game developing much easier if you have someone backing you up when you run into a bug or other issues, and get replies within hours .
Pro Decently sized library of tutorials for both Lua and C++
Pro Very clean and easy C++ API
Pro Lua scripting support
Pro Reasonably priced
Standard edition of Leadwerks costs 92,99€. Additionally, it often goes on sale on Steam.
Pro C++ scripting support
Pro Terrain editor
The terrain editor allows sculpting, paint, vegetation placement and importing of external maps. Especially the painting is done very well and can lead quickly to very professional looking results.
Pro Easy to use API and scripting language
Pro Beginner-friendly
ct.js is bundled with examples, docs, and easy to follow tutorials. Documentation and tutorials are available in a side panel on every screen.
Pro Skeletal animations with DragonBones support
You can import skeletal sprites and animations from DragonBones, which is also free. Skeletal animations are added to objects through code; developers can listen to marked events in animation, and ct.js automatically associates sounds in a DragonBones project with the game's assets.
Pro Good code editor
The built-in code editor comes with error checking, type checks, code completions accompanied with docs, multiple cursors support, and other modern features.
Pro Open source (MIT)
This means that no one will ever put any features behind a paywall and that you can reliably use ct.js in any projects without worrying about licensing. And you can hack on ct.js!
The repo is at https://github.com/ct-js/ct-js
Pro Tileset support
ct.js supports tiles in rooms, including collision checks and some extra editor tools, like bulk migration to a new tile layer or shifting by an exact value.
Pro WebGL and WebGL2 support
Starting with v1.0.0-next-1, you can now write WebGL games. WebGL support is based on Pixi.js.
Pro Modular approach
ct.js has a "Core" library that provides basic drawing functions, room and asset management, and mouse interactions. Any other functions are added to projects as "catmods", or simply modules. These modules can be enabled or disabled in one click, and can inject their code in different game loop stages, e.g. after drawing all the objects, leaving a room, or when a new object is created.
Pro Applicable to most genres
ct.js aims to be a general game engine and provides tools in making games of any genre.
Pro Dialogue and visual novel system with support for Yarn
A module ct.yarn allows developers to import a YarnSpinner project to create branching, data-driven dialogues and visual novels. An example is also bundled with ct.js.
The dialogue tree is made in a separate app, though.
Pro Real-time particle system editor
v1.3 brings a particle system editor, which displays a preview sprite for proper attachment of emitter to visual elements, and allows combining more than one emitter with different particles into one effect. With these, even the creation of complex, multi-step effects becomes easy. The editor comes with dozens ready-made textures for faster prototyping.
Cons
Con Little to no support
This product relies on community support, although some members are helpful and quite approachable they don't like to share their secrets with people that are new to programming.
The product is sold as a Full featured platform but it seems to more in the Alpha stage of development as a lot of the good aspects where taken out in previous versions.
Con Has a track record of broken promises
Con Forums are poorly run and censored
Con Highly misleading advertising
Con Only prefabs made with the Leadwerks IDE could be used.
The two main problems for me is that C++ is not as easy to use like LUA. The IDE should also support C++. The secons is that only prefabs can be used which are made with the IDE. So you can not easy made a game that can be modded by the user.
Con Weak out-of-the-box AI
The only AI movement function is going in a straight line.
Con Very buggy
Leadworks is a not complete, it's a work in progress. As such many parts of the engine are clunky, especially the level editor.
Con Tile editing is a chore
No live brushes with automatic corner drawing, no fills or rectangular/linear placement. All tiles should be placed by hand, with a "Shift" key to place multiple tiles at once. This will make you ragequit if you want to make sophisticated RPG scenes :D
Con Slower than native games
JavaScript and WebGL are fast, but they will always lose in performance if compared to native games, so it may be a bad choice for graphics-heavy games.