>>3809712
Much more limited if only by the fact of the hardware you're using. It's easy to forget but the Game Boy was made in 1989, and the GBC, ignoring the colored graphics, only doubles the CPU clock speed and doubles the VRAM (graphical memory). While you don't need to be a sharp programmer to make a full game in Game Maker, I think you do need to know what you're doing with low-level programming to make something that runs well and plays well on GB hardware.

I would seriously recommend just using Game Maker and limiting your graphics and sound to what can be done on the GB, rather than trying to make it work on hardware, if you aren't willing to learn the nitty-gritty of ASM. To try and give a little perspective, consider how Toby Fox's code is sloppy but Undertale runs fine because it's a simple game that doesn't demand a lot from even cheap (modern) hardware. You don't have that luxury on a Game Boy. If you want to see what badly optimized code runs like, look up the leaked 1997 Spaceworld demo of Pokémon Gold; it's a frankensteined Gen 1 with shit built on top of it and its technical debt makes the game chug even when you just open a menu. The game had to be heavily redone before final release to clean shit up (something some people theorize was assisted by HAL, though officially HAL only gave Game Freak a better compression tool than they were using). You will quickly hit a ceiling using visual coding on such limited hardware and that limits the scope of what you can do