ok so i have a ton of questions that are stuck in my brain and i want them answered, how does a game engine work, and how do you make them?,
pineapple pizza aint that bad ngl
At 8/28/25 09:01 AM, JeanJuniorGames wrote:ok so i have a ton of questions that are stuck in my brain and i want them answered,
let's answer all of them
how does a game engine work,
game engines are one big software that solves several problems, covering the entire game development process from start to finish.
a game engine provides several things among:
- image editor
- sprite editor
- world editor
- panels to configure every element of your game
- code editor
- shader editor
- shader variant compilation
- shader translation
- GUI/HUD editor
- state machine editor
- physics engine
- sound engine
- particle engine
- automatic multiplayer
- automatic texture packing
- automatic shadows
- artificial intelligence
- reverse kinematics
- profiling
- debugging
- building the final executable (and packaging)
- platform integration
- plugin system to extend the game engine with third-party software
all those features are tightly integrated with each other, so that they make sense together.
and how do you make them?,
please, don't make a game engine. not even for learning purposes. I think that creating a game engine is biggest pitfall in the world of programming. I will die on this hill and I'm ready to fight anyone who says otherwise.
just use an existing game engine.
O prudente varão há de ser mudo,
Que é melhor neste mundo, mar de enganos,
Ser louco c’os demais, que só, sisudo
Game engine is a very broad term. It's code that other people have written so that you don't have to. The most common features are rendering 2D/3D graphics, processing controls input, loading files, and playing audio.
If you're interested in game development, you probably should use an existing engine unless you're interested in graphics, network, input and audio programming. If the engine is advanced, it might have tooling developed for it which involves desktop programming. All these luxuries are available to the masses for free nowadays, making game development much more accessible.
Start by learning graphics programming here: https://learnopengl.com/Getting-started/OpenGL
At 8/28/25 01:57 PM, detergent1 wrote:At 8/28/25 09:01 AM, JeanJuniorGames wrote:ok so i have a ton of questions that are stuck in my brain and i want them answered,
let's answer all of them
how does a game engine work,
game engines are one big software that solves several problems, covering the entire game development process from start to finish.
a game engine provides several things among:
all those features are tightly integrated with each other, so that they make sense together.
and how do you make them?,
please, don't make a game engine. not even for learning purposes. I think that creating a game engine is biggest pitfall in the world of programming. I will die on this hill and I'm ready to fight anyone who says otherwise.
:How Hard can it be?
pineapple pizza aint that bad ngl
At 8/28/25 02:43 PM, Jin wrote:Game engine is a very broad term. It's code that other people have written so that you don't have to. The most common features are rendering 2D/3D graphics, processing controls input, loading files, and playing audio.
If you're interested in game development, you probably should use an existing engine unless you're interested in graphics, network, input and audio programming. If the engine is advanced, it might have tooling developed for it which involves desktop programming. All these luxuries are available to the masses for free nowadays, making game development much more accessible.
Start by learning graphics programming here: https://learnopengl.com/Getting-started/OpenGL
what do you recommend?
pineapple pizza aint that bad ngl
At 8/28/25 04:03 PM, JeanJuniorGames wrote:At 8/28/25 01:57 PM, detergent1 wrote:How Hard can it be?At 8/28/25 09:01 AM, JeanJuniorGames wrote:ok so i have a ton of questions that are stuck in my brain and i want them answered,
let's answer all of them
how does a game engine work,
game engines are one big software that solves several problems, covering the entire game development process from start to finish.
a game engine provides several things among:
all those features are tightly integrated with each other, so that they make sense together.
and how do you make them?,
please, don't make a game engine. not even for learning purposes. I think that creating a game engine is biggest pitfall in the world of programming. I will die on this hill and I'm ready to fight anyone who says otherwise.
going out on your own to make a game engine is impossible.
current game engines are severely flawed, while being the result of the joint effort of hundreds of professionals over several years with lots of cash to back their work.
notice that a game engine is not required to create a game.
O prudente varão há de ser mudo,
Que é melhor neste mundo, mar de enganos,
Ser louco c’os demais, que só, sisudo
At 8/28/25 04:10 PM, detergent1 wrote:At 8/28/25 04:03 PM, JeanJuniorGames wrote:At 8/28/25 01:57 PM, detergent1 wrote:How Hard can it be?At 8/28/25 09:01 AM, JeanJuniorGames wrote:ok so i have a ton of questions that are stuck in my brain and i want them answered,
let's answer all of them
how does a game engine work,
game engines are one big software that solves several problems, covering the entire game development process from start to finish.
a game engine provides several things among:
all those features are tightly integrated with each other, so that they make sense together.
and how do you make them?,
please, don't make a game engine. not even for learning purposes. I think that creating a game engine is biggest pitfall in the world of programming. I will die on this hill and I'm ready to fight anyone who says otherwise.
going out on your own to make a game engine is impossible.
current game engines are severely flawed, while being the result of the joint effort of hundreds of professionals over several years with lots of cash to back their work.
notice that a game engine is not required to create a game.
I guess your right (another question: does it take a bunch of people to make a game engine?, does it require pyhton?, can it be written in lua?)
pineapple pizza aint that bad ngl
At 8/28/25 04:13 PM, JeanJuniorGames wrote:At 8/28/25 04:10 PM, detergent1 wrote:At 8/28/25 04:03 PM, JeanJuniorGames wrote:At 8/28/25 01:57 PM, detergent1 wrote:How Hard can it be?At 8/28/25 09:01 AM, JeanJuniorGames wrote:ok so i have a ton of questions that are stuck in my brain and i want them answered,
let's answer all of them
how does a game engine work,
game engines are one big software that solves several problems, covering the entire game development process from start to finish.
a game engine provides several things among:
all those features are tightly integrated with each other, so that they make sense together.
and how do you make them?,
please, don't make a game engine. not even for learning purposes. I think that creating a game engine is biggest pitfall in the world of programming. I will die on this hill and I'm ready to fight anyone who says otherwise.
going out on your own to make a game engine is impossible.
current game engines are severely flawed, while being the result of the joint effort of hundreds of professionals over several years with lots of cash to back their work.
notice that a game engine is not required to create a game.
I guess your right (another question: does it take a bunch of people to make a game engine?, does it require pyhton?, can it be written in lua?)
keep in mind this doesnt mean i wil make a game engine
pineapple pizza aint that bad ngl
At 8/28/25 04:13 PM, JeanJuniorGames wrote:At 8/28/25 04:10 PM, detergent1 wrote:At 8/28/25 04:03 PM, JeanJuniorGames wrote:At 8/28/25 01:57 PM, detergent1 wrote:How Hard can it be?At 8/28/25 09:01 AM, JeanJuniorGames wrote:ok so i have a ton of questions that are stuck in my brain and i want them answered,
let's answer all of them
how does a game engine work,
game engines are one big software that solves several problems, covering the entire game development process from start to finish.
a game engine provides several things among:
all those features are tightly integrated with each other, so that they make sense together.
and how do you make them?,
please, don't make a game engine. not even for learning purposes. I think that creating a game engine is biggest pitfall in the world of programming. I will die on this hill and I'm ready to fight anyone who says otherwise.
going out on your own to make a game engine is impossible.
current game engines are severely flawed, while being the result of the joint effort of hundreds of professionals over several years with lots of cash to back their work.
notice that a game engine is not required to create a game.
I guess your right (another question: does it take a bunch of people to make a game engine?
this question cannot be answered specific to game engines. so it is more general.
a single person will have total control over the software idealization, but this person can become out of touch and their efforts is still of one lone human
a large group produces more, but has to be managed, and bad management is... bad
a growing group suffers with time spent training newcomers to work with the rest of the team
the book The Mythical Man-Month deals a little about this
, does it require pyhton?, can it be written in lua?)
a game engine has a runtime, which is the software that actually runs the game and is shipped with the game in every platform. this runtime is written in a low-level language such as C, C++, Pascal or Rust, in order to achieve high-performance and efficiency. there is always a runtime, by definition.
the user doesn't interact nor alter the runtime directly. in order to actually develop a game, the user uses a scripting language such as Python or Lua, which is interpreted by the runtime when the game is being played.
usually, the user interacts with an editor to use a game engine. this editor can be created with any language that is suitable for creation of GUI software, and is separate from both the runtime and scripting, but interacts with both because the GUI is one bridge between the human and the machine.
examples.
Unity: runtime is in C and C++, scripting is in C#, its editor is made with C#
Godot: runtime is in C++, scripting is in GDscript
Flash: runtime is in C++, scripting is in ActionScript and its editor is made with ActionScript
LÖVE: runtime is in C++, scripting is in Lua, it has no editor
libGDX: runtime and scripting is in Java, it has no editor
Scratch: runtime is in JavaScript (formerly ActionScript, formerly Smalltalk), scripting is with its block coding, editor is in JavaScript
WolfRPG Editor: runtime is in C#, it has no scripting, so the game is entirely created through its editor by pressing buttons and editing textboxes
Unreal Engine: runtime is in C++, scripting is in C++, editor is in C++
three.js: runtime is in JavaScript, scripting is in JavaScript, it has no editor
as you can see, some editors leverage the runtime itself to create their GUI. some game engines implement their runtime with the scripting language itself. some game engines use for scripting the same language used for their runtime.
O prudente varão há de ser mudo,
Que é melhor neste mundo, mar de enganos,
Ser louco c’os demais, que só, sisudo
At 8/28/25 04:42 PM, detergent1 wrote:At 8/28/25 04:13 PM, JeanJuniorGames wrote:At 8/28/25 04:10 PM, detergent1 wrote:At 8/28/25 04:03 PM, JeanJuniorGames wrote:At 8/28/25 01:57 PM, detergent1 wrote:How Hard can it be?At 8/28/25 09:01 AM, JeanJuniorGames wrote:ok so i have a ton of questions that are stuck in my brain and i want them answered,
let's answer all of them
how does a game engine work,
game engines are one big software that solves several problems, covering the entire game development process from start to finish.
a game engine provides several things among:
all those features are tightly integrated with each other, so that they make sense together.
and how do you make them?,
please, don't make a game engine. not even for learning purposes. I think that creating a game engine is biggest pitfall in the world of programming. I will die on this hill and I'm ready to fight anyone who says otherwise.
going out on your own to make a game engine is impossible.
current game engines are severely flawed, while being the result of the joint effort of hundreds of professionals over several years with lots of cash to back their work.
notice that a game engine is not required to create a game.
I guess your right (another question: does it take a bunch of people to make a game engine?
this question cannot be answered specific to game engines. so it is more general.
a single person will have total control over the software idealization, but this person can become out of touch and their efforts is still of one lone human
a large group produces more, but has to be managed, and bad management is... bad
a growing group suffers with time spent training newcomers to work with the rest of the team
the book The Mythical Man-Month deals a little about this
, does it require pyhton?, can it be written in lua?)
a game engine has a runtime, which is the software that actually runs the game and is shipped with the game in every platform. this runtime is written in a low-level language such as C, C++, Pascal or Rust, in order to achieve high-performance and efficiency. there is always a runtime, by definition.
the user doesn't interact nor alter the runtime directly. in order to actually develop a game, the user uses a scripting language such as Python or Lua, which is interpreted by the runtime when the game is being played.
usually, the user interacts with an editor to use a game engine. this editor can be created with any language that is suitable for creation of GUI software, and is separate from both the runtime and scripting, but interacts with both because the GUI is one bridge between the human and the machine.
examples.
Unity: runtime is in C and C++, scripting is in C#, its editor is made with C#
Godot: runtime is in C++, scripting is in GDscript
Flash: runtime is in C++, scripting is in ActionScript and its editor is made with ActionScript
LÖVE: runtime is in C++, scripting is in Lua, it has no editor
libGDX: runtime and scripting is in Java, it has no editor
Scratch: runtime is in JavaScript (formerly ActionScript, formerly Smalltalk), scripting is with its block coding, editor is in JavaScript
WolfRPG Editor: runtime is in C#, it has no scripting, so the game is entirely created through its editor by pressing buttons and editing textboxes
Unreal Engine: runtime is in C++, scripting is in C++, editor is in C++
three.js: runtime is in JavaScript, scripting is in JavaScript, it has no editor
as you can see, some editors leverage the runtime itself to create their GUI. some game engines implement their runtime with the scripting language itself. some game engines use for scripting the same language used for their runtime.
i think now i know everything about game engines (thanks to you), thanks for answering
pineapple pizza aint that bad ngl
Tom Fulp wrote a new engine to make games for PC and consoles, and his family made games like Hominid and Castle Crashers. I really want to write one like that too, but it should be an incredibly legendary, amazing engine. But I don't think I have the patience for it.
At 1/1/26 04:08 PM, punkman53 wrote:Tom Fulp wrote a new engine to make games for PC and consoles, and his family made games like Hominid and Castle Crashers. I really want to write one like that too, but it should be an incredibly legendary, amazing engine. But I don't think I have the patience for it.
wait i ddint know that thats really cool
pineapple pizza aint that bad ngl
