> For the complete documentation index, see [llms.txt](https://resources.dscvit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://resources.dscvit.com/game-development.md).

# Game Development Resources

### Engines

* [Unity](https://unity.com/)
  * Great tooling for 2D, 3D development.
  * Good community and good first-party support.
  * Exports to pretty much any platform you can think of (including web)
  * C# scripting - easy if you are familiar with c-inspired languages (c, cpp, java...)
  * Most any modern indie and AAA titles are made with Unity.
  * Requirements vary, dedicated graphics card recommended, but will work on mid to upper lower tier machines if you are patient enough.
  * THE main engine for XR developement.
* [Godot](https://godotengine.org/)
  * great 2d tooling. 3d tooling is lacking compared to other mainstream engines but is being improved.
  * great community support.
  * Exports to most platforms (console support is a bit iffy)
  * officially supports GDScript (Python like) and c#. Third-Party support is available for a few other languages.
  * Open Source!
  * No jobs (yet)
  * very lightweight. needs a pc that can run atleast 5 chrome tabs (or a flagship smartphone).
  * has XR support
* [Unreal](https://www.unrealengine.com)
  * Arguably the best 3D developement pipeline in a mainstream engine. 2D support is meh.
  * Made by a game studio that uses their own engine, so battle-tested by default.
  * good community and first-party support
  * Scripting done visually (Blueprints) or through c++.
  * optimization will take concious effort.
  * if you see a modern indie game with mind-bogglingly realistic graphics, its a safe bet to assume it was made in C#.
  * has decent XR support
  * no web builds in later versions
  * Source Available, NOT Open Source.
* [Many Other Options](https://gameenginelist.com/)
* Or go engineless if you are comfortable with programming custom graphics, physics, audio, networking, input management, and UI Systems.

### Engine Specific Resources

* Unity
  * [Documentation](https://docs.unity.com/en-us)
  * [Your First Tutorial (GMTK - The Unity Tutorial For Complete Beginners)](https://www.youtube.com/watch?v=XtQMytORBmM)
  * [The Structured, Official Course](https://learn.unity.com/)
  * [Intermediate guided project (Code Monkey - Learn Unity Beginner/Intermediate 2025 (FREE COMPLETE Course - Unity Tutorial) )](https://www.youtube.com/watch?v=AmGSEH7QcDg)
  * [Forum](https://discussions.unity.com/)
* Godot
  * [Documentation](https://docs.godotengine.org/en/latest/)
  * [Tutorials](https://youtube.com/playlist?list=PLPV2KyIb3jR7ecat0FBEMv2EZgsDg6Wcv\&si=gEGtuG84HNcDNloz)

### Engine Agnostic Resources

* Audio:
  * [FreeSound](https://freesound.org/)
  * [Sound Generation](https://www.bfxr.net/)
* Multimedia:
  * [OpenGameArt](https://opengameart.org/)
  * [Itch.io](https://itch.io/)
* Game Design/Theory
  * [GDC](https://www.youtube.com/@Gdconf)
  * [Game Makers Toolkit](https://www.youtube.com/@GMTK)
* Publishing:
  * [Itch.io](https://itch.io/)
  * [Newgrounds](https://newgrounds.com/)
* Tutorials:
  * [SimonDev - What Kind of Math Should Game Developers Know?](https://www.youtube.com/watch?v=eRVRioN4GwA)
  * [Game Dev Beginner - How to write a Game Design Document](https://youtu.be/bro4rwYVo0I?si=nsoa7tab5PL214YL)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://resources.dscvit.com/game-development.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.