So, you know how everybody wants MORE COLORS, or MORE tilemap features, like slopes, but I hear you richard, and how that’d be a very big change to makecode, so instead, Makecode Arcade +! Basically, its Makecode Arcade, but with MORE FEATURES! It would still have the arcade aesthetic, but in glorious 32 bits! and 32 colors! (including white). (I don’t expect this to actually get made, but its a concept)
good idea?
Try making a branch of the makecode arcade github folder, then modifying everything to fit your preferences.
Trust me it will be much more complicated than I made it sound.
If MakeCode is intended for CS education, then making an advanced version of Arcade and Microbit would be a good limbo of the casual versions and actual game engines.
For robotics, you use Microbit (though it might need to expand on hardwares), and for games, you use Arcade. Then you go from blocks to JavaScript and Python, then in the advanced versions, perhaps you could go to HTML, C++, or C#.
Along with these languages, there could be less strict abilities, such as file directories, sprite sheets, and importable sprites and audio. Maybe even push the user to program things from scratch, like movement. These would guide the user from beginner to actual game dev, maybe even with warnings of memory leakage and how to avoid it, instead of leaving the user hanging in those regards. This is trying to teach, not just be a game engine.
I’m trying to give reason to a wall. I know limitations create creativity, but sometimes limitations limit you! MakeCode Arcade is fairly unrealistic (which makes sense and is fine), and a transitional phase would be pretty convenient and educational.
Anyway, rant over.
It would be interesting to make a system like this especially designed for games to be released on Steam or other platforms.
but at that point just use godot or love2d or something because makecode wasn’t made for things like that.