My brain makes things explode.
Archive for April, 2010
Nuzlocke Challenge
Apr 25th
Starting out with the Nuzelock Challenge in Fire Red
So, I’ve started reading a friend’s blog recently (http://www.walnut100.com </shamelessplug>), and he’s started playing through a hacked version of Pokemon Emerald doing something called a “Nuzlocke Challenge.” I’m guessing that the name originates from the user who first came up with the challenge (or something), but here’s the basic rundown:
You play through a Pokemon game, but you add some personal, arbitrary rules to make it more challenging:
1) If your pokemon faints, it is “dead” and must be released. If all of your pokemon die, the game is over.
2) You can catch only the first pokemon you encounter in each new area.
3) No healing items may be used outside of battle.
4) You must use the SET battle mode, meaning you can not change your pokemon while opponent is switching (when you knock their pokemon out)
He’s added the following house rule, which I think I’ll play around with, as well:
-) If you white out at any point in the game, it’s game over
Since I’m already pretty far along in Soul Silver on my DS, I decided I’ll run it through Pokemon Fire Red, and I’ll be publishing my progress here. This is going to be a pain in the ass. >.>
C++/D3D Pong Tutorial 04: Adding Keyboard Input
Apr 25th
Tutorial Description
In the last tutorial, we established a rendering engine and got scene objects working, with basic physics. In this tutorial, we are going to implement the initial Input manager, which will be focusing on the keyboard. I was planning to include mouse input, but it turns out that DirectInput only handles the mouse in relative positioning – which is perfect for three-dimensional first-person shooter games that need to track the movement of the mouse – but it’s poor for two-dimensional casual games. For those of you that do wish to use mouse input, I will be covering it a later tutorial – the methods of getting absolute positioning will require a bit of modification to our engine.
Downloads
Please note that I’ve switched to using 7-zip in place of WinRAR for compression
Binary Only (20.4KB)
Full VS2010 Project Dir (26.8KB)
SVN Repository
As of this tutorial, I have created and added a Subversion repository on Assembla to store the code for the tutorial series. I will continue to upload the source for each tutorial – the SVN will merely contain the code as I write it, so you can feel free to play around with the code that I’m working on before I release a tutorial. Mostly, this is to help people play around with things if there’s a point where I’m slow to create the tutorial following the code (as was the case with this tutorial).
SVN URL: http://svn2.assembla.com/svn/d3dpong
Starting Words
Notice: This tutorial continues from where “C++/D3D Pong Tutorial 03” article left off. Please read it if you have not already.
Another update.
Apr 21st
Well, this has been a busier week than I’d thought. I’ve been more exhausted from the rifle range than I’d anticipated, and while I’ve gotten the code pulled back up and compiled on my reinstall of Windows, I haven’t gotten around to actually writing the tutorial. I have gotten a little work done on it, but not much. And this weekend, I’m probably going to be making another trip to Phoenix, and you can’t count on me to get any work done on my tutorials when I’m spending time with Erin – no offense, but she’s much better company. ;)
Anybody who’s been to my blog more than one time will probably notice that I’ve changed the theme. I’m just playing around with some different themes and such, and I’ve been in a very Apple mood recently, so I decided to pop that up. Other than the time I’ve been able to spend with Erin, nothing’s really changed about my life, that’s worth mentioning, so I guess that about wraps things up here.
Sorry for those who are still waiting on the next tutorial! I’ve got a project that popped up that I’m playing around with as far as Torque goes, but I’m still planning on working through writing up the next tutorial. I’ll probably create a Google Code project for the tutorial series, so that people can get the most up-to-date code from a Subversion repository and play with things themselves, but I haven’t really gotten around to doing anything at all recently. >.>
Some Changes
Apr 7th
For those of you watching my Direct3D tutorial series, I apologize for the continued delay of the Keyboard Input tutorial. I’ve been having some life issues coming up recently, and have been putting in ridiculously late hours at work, all of which take priority. I also got Red Steel 2 and Final Fantasy XIII (and a DSi XL), so my time’s been stolen. Decided it was time for a fresh start on my computer (I do that every now and then), and I was too lazy to download the copy of Windows 7 Ultimate that I had pre-ordered while I was in Afghanistan, so I installed Xubuntu for a while (I feel dirty. I really don’t like Ubuntu. It takes away the only reason anybody should ever want Linux in the first place.) Don’t worry, because I backed up the project files, and I’m going to be reinstalling Windows 7 tonight – assuming I get off work at a reasonable time – and will be able to continue the D3D Pong series.
Which brings me around to my next point. Unlike what I had planned, I am probably not going to be continuing this engine after the Pong clone is complete. I just don’t seem to have the time anymore, and I feel that my time is better spent with Erin and working on other life issues than releasing these tutorials. In short, I don’t feel that I could release the series in a timely manner. Don’t get me wrong, I’m still going to be programming, and I will still be developing tutorials – even a couple series tutorials. I’m just not going to be worrying about releasing the tutorials on any sort of deadline, and most of them will be one-shot tutorials (kind of like my XBOX 360 Controller Input tutorial at CodeProject).
Sorry if this is bad news for anybody, but you gotta do what you gotta do. I’ll still be available for help, if you want it. Best place to hit me up is #snoopy at Keyboard-Failure.
