When comparing Monkey X vs jMonkey3, the Slant community recommends Monkey X for most people. In the question“What are the best 100% free and easy game engines for beginners?” Monkey X is ranked 14th while jMonkey3 is ranked 21st. The most important reason people chose Monkey X is:
Monkey X has a selection of great [built-in modules](http://www.monkey-x.com/Monkey/modules.php). * Graphics * Audio * Input * Data and Filesystems * Networking * Math * Text and Strings * Collections * Online Services
Ranked in these QuestionsQuestion Ranking
Pro Built-in modules for quickly building games
Monkey X has a selection of great built-in modules.
- Data and Filesystems
- Text and Strings
- Online Services
Pro Native code support
Developers can make native calls directly from Monkey code. This allows access to any native functionality and platform-specific features.
Pro You can create custom targets
The language gives you the possibility to build your own targets. You are not limited to the targets officially supported.
Pro Low cost license fee
All target platforms for a fair one off license fee.
Pro Native module support
You are not restricted only to the modules you get from the official release. You can build your own stuff. Even build your own "app" module. It feels limitless. In comparison with other cross platform solutions, you actually get the translated source code and you can play with it if you want.
Pro Easy to learn
With it's Object orientation and clean syntax its a brilliant language to learn if you have never done any programming before and yet still has all the power it needs to make full games and apps.
Pro Uses a great, easy to learn language
Monkey X uses a custom programming language (called Monkey) for all its scripting needs. Monkey is rather easy to learn, it's object-oriented which will help most programmers with understanding it. It's also statically typed and uses a garbage collector, helping to avoid manual memory management.
Pro Partly open-source
The entirety of the base-language itself is open source. Commercial modules such as Mojo for non-free platforms cost a one-time fee. Though Mojo is not free for all targets, the targets for these platforms are, meaning it is possible to implement other frameworks for these targets.
The Desktop (GLFW and C++ based) and HTML5 implementations of Mojo are currently free and open source.
The language's development is completely public, and is managed via GitHub.
Pro Free HTML5 and Desktop (GLFW) target platform
The free version of Monkey X lets you compile to HTML5 or Desktop (GLFW). Other platforms such as iOS, Android (and OUYA), XNA, Flash and Windows 8 (Phone) require the paid version of Monkey X Pro.
Monkey X is a cross-platform game engine. It allows developers to run the same code on multiple platforms, including iOS, Android, Windows Mobile, Flash, Windows, Mac OS and Linux.
The development environment supports Windows, OS X, and Linux.
Pro Not running in its own VM
Unlike other multi-platform engines (Unity3D, Corona, etc), Monkey-X games do not run explicitly in their own virtual machines. Your code is translated into the native languages of each target platform, and then compiled as a native executable. However, just as native games, on platforms such as Android (Currently), and HTML5, games will be ran through the targeted platform's usual VM(s). That being said, you won't be dealing with a proprietary virtual machine, so you won't experience any real overhead when compared to a native game.
Pro Made by the Mark Sibly Factor
The Mark Sibly Factor denotes that a programming language will be easy to learn, fun to learn and allow any age group ( within Cognitive Reason ) to program games and great games. The Mark Sibly Factor denotes also that the games programming language you purchase will be backed by decades of compiler programming experience, game making tool programming and finally a Game Programming Language that kicks Ass.
Pro Free for commercial releases
With the free version of Monkey you are still able to create commercial HTML5 and Desktop games.
Pro Many community modules available
Pro Drawing Commands
Drawing commands are easier to read and edit than is manipulating scene graphs. You can immediately see in your code what's going to be drawn and in what order. Transformations are a no-brainer too.
Pro Lots of great examples
Monkey X includes over 50 examples ranging from complete sample games to demos of single features.
Pro Object oriented programming
MonkeyX is an object-oriented dialect of BASIC that's easy, clean and powerful.
Pro Free and open-source
jMonkey is completely free, meaning it's possible to develop and release a game with no fees or royalties. Because it is open-source, jMonkey has plenty of people fixing bugs and, adding to the engine as well as creating a variety of plugins that can be used in the engine.
Pro Not limited to using its own IDE
Unlike some engines, jMonkey doesn't force its own IDE. You can use its Netbeans-based IDE, but you can also set up a project to work in another IDE such as Eclipse. You can still use the special tools from jMonkey's IDE in such projects.
Pro Engine modifications can be made using Java
Because jMonkey is implemented in Java, the same language its apps are typically developed in, developers will have an easier time modifying the engine to their needs.
Pro Java is a great development platform
Java is a well-optimized just-in-time compiled language. It's faster than languages without an effective native-code compiler such as Python or Ruby, similar in speed to other just-in-time compiled languages such as C#, while slightly slower than compiled languages such as C or C++ (with some low-level and numeric benchmarks being similar to C++).
Java also has a wide variety of high-class IDEs available.
Pro Ease of extensibility
Engine is modifiable.
Pro Freedom of choice for architecture
The user is not compelled to use any programming architecture nor standard in order to make a project working. JME allows the freedom to use what is best for a game.
Pro Offers both low-level and high-level ways of editing shaders
Modifying shaders can be done either via a visual tool called Shader Nodes or via GLSL that allow you to make your own shaders without the engine getting in the way or having to hack around to do so.
Pro Multiplatform support
Code can be ported to mobile (iOS is in the works) and other Android supported devices with minor changes to the code (just change some implementations that vary on the platform such as inputs and user interface). It can even run on certain Raspberry Pi devices.
Pro Has everything
jMonkey3 handles input from computers and mobile devices. It handles networking, physics, rendering, terrain, and cinematics.
Con The documentation is not very thorough
The documentation contains a reasonably detailed language overview, and a somewhat-generated list of the included modules, classes, and methods. Module descriptions are rather lax, but usually present. Method descriptions tend to be short, and a majority of them contain no usage snippets; most parameters have very minimal descriptions. And there are no community collaboration features to help improve it, besides GitHub.
Con The included IDE is poor
Although better IDE'S are availabe for a price, the default one is bare bones and lacks functionality
Con No real asset store
Untangling how to keep assets in the ".data" requires attention and a filenaming convention.
Con You'll have to learn a new programming language
Even though Monkey is rather easy to learn and borrows a lot of concepts from more popular languages, having to learn a new language develop games is a lot of friction for people that already know how to program in other languages..
Con limited OS export targets with free version
Free version only targets Desktop (macOS, Windows, Linux) and HTML5, not mobile.
Con Not an engine for total beginners
While it's clear that you need to know Java first before using this engine, it is recommended that you have some programming experience as well. Most performance issues and memory leaks are more due to bad programming practices than the engine itself.
Con Slow release cycle
jMonkey3 lacks manpower to have a fast and decent release cycle.
Con Relies on archaic tool chain
jMonkey Engine uses Apache Ant for build automation, which is archaic and backwards, even by Java standards.
Con Terrible API reference
The methods are not defined.