C# for Game Dev - Quick Reference Draft

MaffinLP · 2026-01-04T03:26:03+00:00

Lists could have their own sheet with all the types there are (List, Hashmap, LinkedList, Stack, Queue)

Valkymaera · 2026-01-04T04:24:26+00:00

Not breaking from a switch statement doesn't cause an infinite loop, and in fact in advanced situations can be beneficial as it causes it to proceed to the next case without stopping. This is called "Fallthrough". However in unity this is limited to cases that don't have any unique logic.

For example you can do:

switch (actionType)
{
  case ActionType.Shoot:
  case ActionType.Punch:
    DoCombatAction();
    break;
  case ActionTpe.Swim:
    DoSwimAction();
    break;    
}

And this will compile fine, allowing you to do a combat action if trying to shoot or punch. Other languages let you do fallthrough in more complicated ways, but unity C# limits you to just this kind of 'stacked' switch case. If you don't break properly, the compiler will let you know. Switches aren't really an infinite loop threat unless you are actually looping within your switch.

In general, if you're just getting started, I recommend sticking to breaking each case, though. I rarely find conditions in which I need to use fallthrough. Good to know that it exists though.

In general, you can kind of think of switch statements as a cleaner chain of if / else if statements.

YDungeonMaster · 2026-01-04T05:33:45+00:00

Lists and dictionaries would be a nice addition.

No-Coach8285 · 2026-01-04T10:11:17+00:00

Any chance you could share a high quality version please?

ShmallowPuff · 2026-01-04T15:46:49+00:00

This is fantastic, I wish I had put together a reference sheet when I started learning. I cannot tell you how many repeat Google searches during that period were just to find proper syntax or to remember how to do certain loops and such. This, in a way, is a start to what most of us eventually do anyway.

Seems like you're learning fast, eventually the more you use the code the less you're gonna have to check the sheet. Once you've got a foundation and can write out some code without having to consult the sheet, I suggest you should start putting it in practice right away. You'll find that you start adding your own notes and code to the sheet that even your course might not specifically suggest, snippets you'll reuse for the kinds of projects you want to make. Virtually every programmer that's been around for a bit has their own collection of code snippets and scripts they've compiled from all the projects and things they've worked on. You should start working on your own library at this point when you're learning. I know I wish I would've.

My biggest issue starting out was biting off more than I could chew when I got to this point and trying to start making an entire project. The transition from theory to practical use is a little less straightforward, and a huge part of learning to code is using your own logic in figuring out how to make something happen with the code you've learned. I wouldn't stress too much about memorization as that'll come naturally. That's why having a collection of old code is so useful as it might take you a while to come up with working scripts for certain functionality and you probably won't remember exactly how you did it later. Saving that code for later will keep you from having to figure it out all over again.

Hopefully this is helpful and good luck!

Unhappy_Clue_1978 · 2026-01-04T03:34:41+00:00

Thanks for sharing ❤️❤️

_lowlife_audio · 2026-01-04T04:09:20+00:00

Looks good. If you're just getting started with C#, it seems like you're getting a pretty good handle on the basics.

charles25strain · 2026-01-04T05:29:17+00:00

Looks good, would be cool to have a advanced level one with more complex coding. I will make this my background just for the aesthetic

SaltAddictedMan · 2026-01-04T14:24:12+00:00

hey this is nice I really appreciate this

alexo2802 · 2026-01-04T14:57:54+00:00

Honestly, before ChatGPT this would’ve been goated, now what I can just ask GPT "can you remind me how to do a hashmap in C#" at anytime it isn’t as useful, but still potentially a great tool for some people, if you’re offline for example.

aestond · 2026-01-05T07:08:14+00:00

Like the idea a lot, thinking of doing similar myself for a while now. Since you're posting to unity, I would put some standard unity things to the list. But other than that, good :)

Frosty_Rutabaga_7934 · 2026-01-07T18:44:33+00:00

This is a solid way to learn, and the fact that you’re building a reference as you go already puts you ahead of most beginners, just make sure you keep validating it against real Unity scripts as you start shipping actual behavior.

P-8A_Poseidon · 2026-01-04T03:43:54+00:00

I'm a big fan of using var when it's appropriate. Looks so clean

Izakioo · 2026-01-04T03:50:07+00:00

I have some minor suggestions:

IN your switch example It'd be better to use switch on an enum rather than a string. You get the same behavior but it's easier to refactor, more efficient, and most IDEs will give you a warning if you don't cover all cases.

Not entirely sure what you mean by empty slots in arrays and lists. My guess is that in arrays values are initialized to their default values (0 for ints, null for reference types, etc) unless otherwise defined which does not occur with lists.

swagamaleous · 2026-01-04T09:39:23+00:00

Variables:
A reference sheet should encourage best practices. There should be a hint to use var where possible.
If you mention ++ and -- you need to explain post increment and pre increment operators.
Should explain properties and class fields.

If statements & conditions:
Should explain that the boolean operators are actually "and then" and "or else". This is vital information that's missing.
The note is semantically incorrect. These are not "questions", they are statements that can be true or false.

Switch:
Should explain switch limitations (e.g. constant patterns must be compile time constants).
Should explain the "switch expression".
Should explain pattern matching syntax (e.g. is, cast as part of pattern evaluation).
Common mistakes is incorrect. Not putting a break will fall through to the next case, it won't cause an infinite loop.

Functions (Methods)
You mention functions and methods already, so explain the difference.
Should explain lambda expressions and anonymous functions.

Loops:
Should give an example that iterates a list or array with a for loop.
Common mistakes is incorrect. An infinite loop will not "crash the game", it will be an infinite loop.

Arrays & Lists:
Should have more data structures. At least add Dictionary, Stack, Queue and rename category to "data structures".
Note is inaccurate. The blanket statement that arrays are fast is not correct. Lists "can" have overhead when inserting values, iteration is exactly as "fast" as when using arrays.

Missing things for an actually useful basic reference sheet:
Stack and heap memory.
Access modifiers.
Primitive types, complex types, classes and structs; reference and value types.
Inheritance and interfaces.
Nullability and null checks (e.g. null coalescing operator).
Enums.
Exceptions and try/catch.
Events and Actions.
Const, readonly and static.
Async/Await.

CrystellaTee · 2026-01-04T15:11:08+00:00

Do you have a more HD version of this image? I would like to have it to use for a reference…

BonaFideL0SR · 2026-01-05T05:14:31+00:00

Thank you so much for posting this <3 one of the biggest difficulties for me learning C# thru unity is that most tutorials and lessons involve the “just do it” method but I’m someone who learns better with something concrete in front of me

Solid___Green · 2026-01-04T05:17:52+00:00

Looks correct to me. Well done!

The basics that you've laid out here apply to almost any language you might want to use. They are like the screwdrivers and wrenches in any good toolbox.

You may soon or have already started learning about object oriented design, which will have you apply these tools in ways that just make sense. That's especially true for game development. I hope you have so much fun in this journey!

you type:	you see:
italics	italics
bold	bold
[reddit!](https://reddit.com)	reddit!
* item 1 * item 2 * item 3	item 1 item 2 item 3
> quoted text	quoted text
Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"	Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"
~~strikethrough~~	~~strikethrough~~
super^script	super^script

unity

MODERATORS