hello friends! new(ish)!
Game programming: Difference between revisions
>Britfag m (→C#) |
>Eldy No edit summary |
||
| Line 1: | Line 1: | ||
Game programming is complicated. It can also be a great way to practice your language. Before you even think about any serious game/multimedia programming, you should know the language that you're going to use to a decent extent. | Game programming is complicated. It can also be a great way to practice your language. Before you even think about any serious game/multimedia programming, you should know the language that you're going to use to a decent extent. | ||
Aside from the programming itself, a good game needs decent graphics, sound/music, and story. Just having "ideas" for your game isn't good enough, but can be a good start. | Aside from the programming itself, a good game needs decent graphics, sound/music, and story. Just having "ideas" for your game isn't good enough, but can be a good start. | ||
Another important point: Making your own "engine". Don't. Or at least, don't in the way that you think you're going to: Don't try to visualize the perfect game and then make an engine around it. An engine, especially for someone that programs unprofessionally, is something that is built on, and added to. The features of an engine should be able to apply to many different aspects - they should be reusable. | Another important point: Making your own "engine". Don't. Or at least, don't in the way that you think you're going to: Don't try to visualize the perfect game and then make an engine around it. An engine, especially for someone that programs unprofessionally, is something that is built on, and added to. The features of an engine should be able to apply to many different aspects - they should be reusable. | ||
== Engines == | == Engines == | ||
Revision as of 12:17, 6 June 2018
Game programming is complicated. It can also be a great way to practice your language. Before you even think about any serious game/multimedia programming, you should know the language that you're going to use to a decent extent.
Aside from the programming itself, a good game needs decent graphics, sound/music, and story. Just having "ideas" for your game isn't good enough, but can be a good start.
Another important point: Making your own "engine". Don't. Or at least, don't in the way that you think you're going to: Don't try to visualize the perfect game and then make an engine around it. An engine, especially for someone that programs unprofessionally, is something that is built on, and added to. The features of an engine should be able to apply to many different aspects - they should be reusable.
Engines
A game engine is a collection of framework and libraries that manage all the aspects of game development (physics, rendering, networking, etc.). They usually come with a scripting language to allow you to program the behavior of the different components, and some come with an editor that allow you to visualize these components in a graphical interface.
- Unity is one of the most popular game engines out there. It features an editor and uses C# as its main scripting language. It is also responsible for most of the trash and shovelware that was released on Steam since the dawn of Steam Greenlight, mainly because it is very easy to learn (the official website provides some decent tutorials). The basic license is free but requests that you use the default Unity splash screen.
- Unreal Engine was paid until May 2015, but, following the success of Unity, it picked the same business model (free with a few restrictions that should not bother hobbyists). Like Unity, it features a powerful editor. Unlike Unity, it uses C++ as its main scripting language. It also features visual graph-node scripting called Blueprints if you're a brainlet. Unreal Engine's source code is available to anyone with an Epic Games account.
- Godot is a FOSS game engine. Its features are comparable to Unity.
- LÖVE is an open source game engine geared toward 2D games development. It uses Lua as a scripting language and is simple to learn and use, making it well suited for beginners.
- Pygame is the same as above but with Python as a scripting language.
APIs/Libraries
/g/'s general recommendations:
Pleb Tier
"Game Engines" such as Unity/UDK/CryEngine. Seriously, don't use these. It is just a waste of your time when you could be learning programming and actual game development.
Java
Java is pajeet tier but usually fast enough for games. For Android don't work in Java; you'll want to use the native api (NDK).
C
- SDL
- Allegro - targets a very old version of OpenGL, useful for making games compatible with Windows 95 - XP.
C++
A list of open source C++ libraries
C++ graphics libraries:
Physics Engines:
OpenGL-based libraries are suggested as it has the capability of being multi-platform, unlike DirectX (ex: Direct3D).
C#
C++ is generally suggested over C#, but C# is by no means bad. Especially if you're a beginner, C# lets you not have to deal with as much memory management as C++, and C# has helpful frameworks available. Note that in managed code, garbage collection is your enemy. You'll have to take special care in writing performance critical code to limit GC allocations. C# is extremely useful for tools development (eg. level editors)
Note that many scripting languages can be used on top of the base engine, ex: AngelScript
All of the libraries listed above are licensed under free licenses.
Game Jams
A game jam is a challenge asking you to develop an entire video game in a very limited time spawn. They are a very good opportunity to hone your game programming skills, as well as to have fun.
- Ludum Dare is one, if not the most popular game jam, running since 2002 and occurring every 4 months. It lasts either 48 hours or 72 hours depending on if you are participating solo or as a team.