Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Polycode vs GameMaker Studio 2, the Slant community recommends Polycode for most people. In the question“What are the best 2D game engines?” Polycode is ranked 32nd while GameMaker Studio 2 is ranked 67th. The most important reason people chose Polycode is:
Polycode uses Lua and C++ to create native applications for Windows, Mac, and Linux. Mobile platforms are planned for the future.
Specs
Question Ranking
Pros
Pro Can create portable native applications
Polycode uses Lua and C++ to create native applications for Windows, Mac, and Linux. Mobile platforms are planned for the future.
Pro Free and open source
Polycode is free and open source (released under the MIT license). The source code is freely available on GitHub.
Pro IDE for 3D editing
Recently, the editor and its integrated tools have been released in compiled form. Features coding and scene editing in one application.
Pro C++/Lua
Polycode is distributed in a C++ form as well as with IDE. And there's an additional LUA-based scripting system.
Pro Quick prototyping
Pro Good user interface
Pro Well-optimized engine
Pro Has a trial version (but limited functions, can't export)
Pro Many unofficial tutorials
Most GMS1 tutorials are fine for GMS2
Pro Highly customizable IDE
Although users must work within the IDE and editor, GMS2 has many options to customize the look and feel
Pro Good documentation
Pro Huge, generous community
Cons
Con Abandoned
The project does not seem to be maintained anymore: there has been no new release nor commit since mid-2015.
Con No mobile support
Doesn't have support for Android or iOS.
Con Not the best scripting language out there
GML is just weird; if you want to learn programming, it is not the best because it teaches bad habits and has many odd shortcuts and shortcomings that won't transfer to a real language
Con HTML5 export is buggy, doesn't "just work"
Con Quite expensive
Windows ($100) + HTML5 ($140) + Mobile ($400) + UWP ($400) is $1,050, plus $800 anually for each console export separately. But doesn't do anything any of the free engines can't do, and the stability and tech support aren't great.
Con Unstable
Users frequently report crashes and hangs, particularly when working with assets, and the software uses a complicated underlying meta-file structure that may become corrupted and cannot be rebuilt
Con Limited support for OOP
Con Small development team
The core programming team is only 5-10 people, with about 30 employees total, so bug fixes can take a long time to be addressed, and there aren't many official tutorials
