Beginning MonoGame

February 6, 2017 · 1 min read

I’ve had a few folks ask me for a good “Getting Started” tutorial for MonoGame over the last year and I’ve done a few talks on the subject, but hadn’t really had an opportunity to put anything together until now.

Instead of writing some massive thing that I never finish, I’m going to keep these posts relatively short, and focus on individual aspects of getting up and running with MonoGame, dissecting the starter project, and then move into cool things you can do.

As I create new pieces, I’ll update this post with links to them, and hopefully keep a running thread to tie them all together. Also, if I mention covering something later, I’ll try to add a bullet for it here so I remember to come back and add it.

Let’s see where it goes, and feel free to suggest stuff for me to cover as well.

**NEW VERSION ANNOUNCEMENT**

GETTING THE STUFF

MONOGAME BASICS

  • MonoGame project types explained.
  • What’s in the starting project?
  • The Game Loop
  • Getting a sprite onscreen
  • Putting text onscreen with spritefonts 
  • Listening for (and responding to) input
  • Moving your images around

ADVANCED TOPICS

  • More about the SpriteBatch
  • More about SpriteFonts
This article is part of the GWB Archives. Original Author: Chris G. Williams

New on Geeks with Blogs

  • We Won The One Award I Actually Care About

    Full Scale made the Inc. 5000 for the fifth year straight, the 12th listing across my three companies. Here is why the one award you cannot buy is worth stopping for.

  • Your Customers Build the Features Now

    I let a tool I liked sit dead for a year rather than build the features I wanted. An MCP server meant I never had to, and your customers can do the same to your product.

  • Get the Size of a Directory in Linux the Easy Way

    du -sh for the quick answer, ncdu for the cleanup, df for the disk itself: every command for checking directory size in Linux, plus why du and df never agree.

  • Vim Search and Replace: The Ultimate Guide

    One :%s command replaces every match in a file before a find dialog would even open. The Vim substitute patterns worth the muscle memory: flags, ranges, capture groups, and multi-file edits.