When comparing libGDX vs RPGMaker, the Slant community recommends libGDX for most people. In the question“What are the best 2D game engines?” libGDX is ranked 14th while RPGMaker is ranked 28th. The most important reason people chose libGDX is:
Lots of references, tutorials and open source code to learn from.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Lots of resources to learn from
Lots of references, tutorials and open source code to learn from.

Pro Great performance across devices
While it may not always have the best performance for a particular device or system, it's one of the few engines which consistently performs very well across different platforms.
Pro Fantastic UI toolkit (scene2d)
scene2d is a 2D scene graph, scene2d.ui is a UI toolkit on top of that. It enables very complex mobile and desktop UIs.
Pro Can use any JVM language
Since it's built with Java and runs on the JVM, any language that compiles to Java bytecode can be used to develop games with libGDX.

Pro Uses Box2D
A Java port of the Box2D physics engine is included in libGDX.

Pro Allows you to migrate from 2D to 3D within same framework
LibGDX supports both 2D and 3D game development. Allowing developers to migrate from 2D to 3D with ease without having to switch the engine they are using or having to learn a new API.
Pro Doesn't force a specific design
Unlike some engines, which only allow you to make your game in a few specific ways, libGDX allows you to design any type of game you wish as it is extremely customisable.

Pro Active and helpful community
The libGDX community, in the official libGDX forum is extremely helpful and approachable for any kind of question regardless of the its quality or difficulty.
The forums themselves are a very helpful resource for any issue or guide simply by searching past posts in there.
In addition to the forums, there's also the official #libgdx IRC channel on Freenode.
Pro Interfacing with platform specific code
Sometimes it is necessary to access platform specific APIs, e.g., adding advertisement services or leaderboard functionality provided by frameworks.
Pro Free, open source & permissive license
libGDX uses the Apache License 2.0.
Not only is libGDX free and open source but also it's license gives you a lot of power over the engine. As long as you provide a copy of the license, give credit, do not hold devs liable and do not use libGDX logo in any engine forks you can do pretty much anything you want.
Pro Kotlin support
It is written in Java so you can easily make games using Kotlin and Ktx project will help you get all advantages of this language.
Pro Very easy to customize
Pro Constantly improved
LibGDX itself is pretty mature, and get updates not quite frequently, but various libraries for it are actively updated.
Pro Across platform support
You can write once and run anywhere (Android, IOS, Desktop, Browser) also lately came with lib to deal with VR.
Pro Support for 3rd party tools
libGDX has built in support for many 3rd party tools, including (but not limited to) Bullet Physics, Box2DLights and the well-praised Tiled Map Editor.
Pro Lots of tutorials to get you going
Even though the official documentation might be lacking, there are many tutorials on YouTube for libGDX.
Pro Excellent font rendering support
Very good tools for rendering fonts.
Pro Similar to the Microsoft XNA framework
Old XNA users may like libGDX since it's API is actually very similar to XNA's.
Pro Focusing on object pool patterns, to control memory without pointers
Unlike Unity or other engine, it allows to optimize a language that uses garbage collector when using patterns of objects you can control the use of memory without needing a language like C / C ++, getting the same speed in a more productive language.
Pro Easy to jump into using an intuitive WYSIWYG editor
It's possible to create a game with absolutely no art or coding skills, so even complete beginners can make something.
Pro Large and active community
The engine has seen multiple iterations since 1995, so a large online community exists that is always willing to help each other out.
Pro Ruby / Javascript support provides depth to more experienced developers
With a script editor that uses a modified version of Ruby, it's possible to go well beyond the traditional RPG with this engine. Note: XP and VX use Ruby, the latest version "MV" uses Javascript for scripting.
Pro It's an open engine
It's possible to use custom editors from the community, edit libraries,include libraries,etc (MV Only)
Pro Multi-platform
MV supports HTML5 exports, so it is easier than ever to make your game work on iOS, android, OSX,Linux or Windows.
Pro Inbuilt database and multplayer plugins, providing you the scalfolding to customising your projects with ease
The inbuilt database which binds to game saves or can be made persist allows great power within your logic. Also a plugin called 'Alpha.net' provides multiplayer. This combination can allow great customisation of the engine, allowing a powerful 2D game to be made with little to no coding experience.
Pro Greater Map layers
MV Mapping uses an additional layer to create better depth.
Pro MV has HTML5 export
You can now HTML5 export your projects, so you could theoretically host your game on your webserver, and have your friends play the game without ever having to install a single thing.
Pro A cheap license that allows using the software commercially
There are several versions of RPG maker, with MV being the latest and most fully featured: MV ($79.99), VX Ace ($69.99), VX ($59.99) and XP ($24.99), 2003 ($19.99).
Cons
Con Not starter friendly
Even default applications fail to load in Android. It doesn't have any documentation on errors either.
Con Documentation could be better
Other than a brief installation / getting started overview, libGDX's documentation consists of an official wiki with several incomplete pages, and automated Javadocs. The community recognizes these shortcomings, and new users are encouraged to ask for help.

Con The project slowed down in development
The number of active developers has decreased, many open issues and pull requests.
Con Build system is clunky
LibGDX uses Gradle, which is very demanding of memory and makes IDEs freeze on anything if your computer is not powerful enough.

Con Does not create compiled code
LibGDX runs entirely on Java and does not create executable binaries.
Con A bit difficult to use
This engine is not well put together. Is made from various free modules each with their own peculiarities. At times it feels you need to learn a couple of libraries rather than just one. Is not an engine for beginners as it requires coding. Lots of coding. You need to be intermediate to advanced in Java to develop in LibGDX.
Con You have to code when you want something didn't built in
You know,RM series' default walk animation only has three frames.If you want to enhance,you have to code by yourself——especially majority of it's user are newbies.
Con No Hardware accelerate
You'll get a bad performance when you have big animations,especially in MV,which can easily change into higher resolution.
Con No 3D support
None of them have 3D support, it is possible only with manual scripting which could be difficult for beginners.
Con MV Does not have a "REAL" Android export.
MV has an export to HTML5 - which can run on any browser including android. It is however not a "native" app export.
Con Inconsistent included visual assets
Included visual assets within MV have inconsistent presentation. Though RPMMV does contain enough to make a small basic title, the visual assets don't often look like they should be mixed on-screen.
Con No built-in realtime battle system
RPG Maker series has only turn based battle systems, unless scripts/Plugins made by the community are used.
Con Conversion to MV difficult
Older iterations of RPG Maker use smaller sprite sizes that require manual conversion to use older RTP assets and older assets are more robust.
