News for hackers. Stuff that matters.
Re:How does a game engine work? an overview (2016) by flohofwoe on Sunday November 07, 2021 @06:57AM (#29138689)
I like to call the Unity approach a "Photoshop for games" (which can be a good or a bad thing, depending on perspective and requirements).

It's essentially a game-maker UI tool with some support for scripting/coding. The runtime that's dangling off the end of the asset pipeline and editor is much less important (even if this hurts the pride of hardcore engine coders) ;)

PS: a standalone "bring your own engine" hackable Unity editor would be great, but I guess that doesn't quit fit into Unity's business model

Re:How does a game engine work? an overview (2016) by meheleventyone on Sunday November 07, 2021 @07:15AM (#29138809)
> PS: a standalone "bring your own engine" hackable Unity editor would be great, but I guess that doesn't quit fit into Unity's business model

I’ve been thinking about this a lot as I want to write more standalone games with minimalist runtimes but also don’t want to give up the QoL you get with a decent scene editor with runtime inspection and “fiddling”.

One thing that intrigues me is the recent rash of tools made with Godot as it has a pretty good UI system that is used to make their own editor: https://itch.io/c/651672/tools-made-with-godot-engine

I could see a decent open-source game editor made this way as well. But don’t have the energy to actually do it myself.