luksamuk

Yeah, so let's start a new blog.

It's kinda hard to start because I think I have nothing to talk about, but I just happened to find one thing.
I'm currently working with a friend of mine on an indie project called Prepare: Uranus (you may soon see it on Desura). Also, the simplies part of it will be divulged opensource; I'm making videos to teach people deal with MonoDevelop.

So I realized I had to follow a trail of important arguments, or else I'd just end up teaching randomly.
That's when I chose to teach some more advanced techniques, such as Screen Managing system and etc.

Why? Because tutorials sometimes lack optimization - and that's pretty much the case for another project I'm yet going to reveal, from which Prepare: Uranus uses its input and screen management engine. In some part of it, I just ended myself asking "how the hell am I supposed to unload the content I'm not using anymore?"
The answer, as always, came on StackOverflow: "Make a new ContentManager." Instantiating it for every screen TOTALLY wasn't hard.
But it asks for a ServiceProvider when it is instantiated. So I was like "what the heck", until I googled a bit more and found the solution.

Back to my previous point, in this series of tutorials I will touch some important parts regarding bugs and other things that may be found on the road of game development with XNA/MonoGame, thus basic input system for platforming games (including non-X360 controllers, which was a PAIN to figure out how to make them work) and basic (but yet complete) screen management.

The current videos (today I'll make the third) are on my Youtube Channel, and are dubbed Portuguese-Brazil.