I Made the Same Game in 8 Engines

Hard mode: make your own game engine

over a decade ago, i was trying to do different things out of boredom on the internet, one such thing was doing pixelarts. I joined forums, drew some simple stuff and then found this collab project where people would just make assets for a game engine. You can guess where I'm going with this, yes most of the "jungle" assets you used in the Game Maker section were actually drawn by me. I was shocked to see them in this video because i totally forgot about it until now. I didn't stick very long into that hobby

"I don't fear the man who makes eight games, I fear the man who makes the same game eight times"

Using a bowl of cheese puffs, a fortune cookie, and an ocean background in the same game is the most Scratch thing I’ve ever seen and I love it

0:53 Unity -> Famous and versatile 2:09 Unreal -> Better to make big games 4:07 Godot -> Lightweight and easy to use. 5:45 Game Maker -> Capable and polished 2d game engine 7:08 Construct 3 -> No code, is used on the browser, good to make smaller projects and prototypes. 8:39 GDevelop -> No code, good to start developing games 9:41 RPGMaker -> Great to make RPGs 11:05 Scratch -> Great to start

I love how every game but the one on Scratch has a logical theme and looks polished, then for Scratch, he just said, "I'm done, you're getting cheese puffs catching fortune cookies."

Thank you, every time I watch a video on game dev its "don't do this" or "Use this only" it creates an expectation of success and putting yourself above others rather than actually taking the time to learn and enjoy what you're doing.

You genuinely inspired me to learn scratch for one simple reason: I've wanted to teach my 5 year old to use it when she's old enough, now that I saw this example it seems that I'll be able to do so next year. She's asked me a lot of questions about how games are made in the past.

The choice to use cheese puffs and a fortune cookie underwater really left me scratching my head.

My intuition was that the reality of the different game engines is that it's a "right tool for the right job" kinda scenario, and I'm glad you acknowledged that. The summary you gave each engine highlighted their general strengths and weaknesses, without getting into the nitty-gritty details, low-level stuff, and edge cases--although, I'd be happy to sit through a 10-hour video essay that does so, if anyone on youtube has that much skill and knowledge. The idea of making a game in all the engines is a really cool project to learn the basics, but I don't think it fits the thesis of your video (fairly comparing the engines). No matter what kind of game you choose, some engines will be tailored for that genre and be made to look like flawless multi-tools (e.g. Construct in this case), and some will be so out of their league that they seem like bad engines (e.g. RPGmaker for a catcher game) I'd also love to see someone do a similar comparison of different frameworks in different programming languages, but that's probably apples and oranges given that the different languages will each have their own strengths and weaknesses as well as the frameworks for each.

I wish we could have a look at old dead engines and proprietary engines. I’ve been doing this since the 90’s and things have come so far. It’s impossible to get a hold of things like Renderware or internal engines that some classic games were built in. These engines have a ton of parallels with current tech but also an insane amount of specific work you had to do just to not have the whole project crap out on you. In many ways things were simpler, easier, but also more complex and harder. This is why as game tech gets better it just raises the bar and games remain really hard to make 😢 Awesome video

This influx of devs after unity's failure is gonna propel Godot's development speed alot. Looking forward to it.

Man. I've been an indie game enthusiast for 20 years and known a handful of indie devs over the years. But I had no idea how easy and flexible development has gotten. Based on this video, I might give some projects a try!

This is a neat way to showcase alot of engines, as well as their individual strengths and weaknesses! As someone who's mainly been wanting to get into Godot, it's pretty insightful to see what's going on with other engines. 👍

holy shit this aged well

This video is actually really good for people who want to start game development but don't know where to start. I've been wanting to create a story game for a while, but I didn't know where to start, This video showed me RPG Maker and that seems very promising! You earned a sub. 👍

I'm a non-game programmer in my day job and I've never really looked into game programming or how these engines work. The biggest thing that stands out to me is how (relatively) easy these engines seem to make it, at least when compared to what I had imagined game programming to be like. It seems like they streamline all the stuff that always seemed like it'd be incredibly difficult. I didn't realize you could literally just (for example) drop models into a scene with your mouse.

If anyone who knows C# is possibly hesitant on trying out Godot because it has it's own scripting language, Godot also allows you to write and use C# scripts instead. A lot of the online tutorials are still for GDScript, but are pretty easy to translate over. GDScript is pretty simple to learn, so if youre in this position i'd still advise giving it a shot to see how you feel about it. However it is not strictly necessary, and I thought that was worth a comment!

I love how every game looks atleast good and polished while the scratch version is just like: "Underwater bowl of cheeto with fotune cookies and a banana throwing octopus!!!"

Your diligence, authenticity, and genuinely positive nature is refreshing and uplifting. I'm happy I found your channel.