<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Raelifin.com &#187; game</title>
	<atom:link href="http://raelifin.com/tag/game/feed/" rel="self" type="application/rss+xml" />
	<link>http://raelifin.com</link>
	<description>Deus ex Machina</description>
	<lastBuildDate>Sun, 04 Jul 2010 01:45:59 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>Learning Python</title>
		<link>http://raelifin.com/code/learning-python/</link>
		<comments>http://raelifin.com/code/learning-python/#comments</comments>
		<pubDate>Wed, 26 May 2010 18:10:36 +0000</pubDate>
		<dc:creator>Raelifin</dc:creator>
				<category><![CDATA[Code]]></category>
		<category><![CDATA[game]]></category>
		<category><![CDATA[python]]></category>
		<category><![CDATA[text-based]]></category>

		<guid isPermaLink="false">http://raelifin.com/?p=375</guid>
		<description><![CDATA[It&#8217;s not that interesting, but I made a little one-player text-based RPG in python (3.1.2) this morning/last night. I&#8217;m happy with it, just because it&#8217;s the largest thing I&#8217;ve ever done in python. The whole thing is based off of this blog post. You can get the source code here: http://raelifin.com/files/code/rcrpg.py It&#8217;s all public domain, [...]]]></description>
			<content:encoded><![CDATA[<p>It&#8217;s not that interesting, but I made a little one-player text-based RPG in python (3.1.2) this morning/last night. I&#8217;m happy with it, just because it&#8217;s the largest thing I&#8217;ve ever done in python. The whole thing is <a href="http://web.archive.org/web/20080212201605/http://shortcircuit.us/muddy-kinda-like-a-mud-but-single-player/">based off of this blog post</a>. You can get the source code here: <a href="http://raelifin.com/files/code/rcrpg.py">http://raelifin.com/files/code/rcrpg.py</a><br />
It&#8217;s all public domain, but I like credit (yada, yada).</p>
]]></content:encoded>
			<wfw:commentRss>http://raelifin.com/code/learning-python/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Mastery</title>
		<link>http://raelifin.com/meatspace-games/mastery/</link>
		<comments>http://raelifin.com/meatspace-games/mastery/#comments</comments>
		<pubDate>Thu, 25 Mar 2010 22:14:23 +0000</pubDate>
		<dc:creator>Raelifin</dc:creator>
				<category><![CDATA[Meatspace Games]]></category>
		<category><![CDATA[game]]></category>
		<category><![CDATA[Mastery]]></category>
		<category><![CDATA[minimalist design]]></category>
		<category><![CDATA[PnP RPG]]></category>
		<category><![CDATA[roleplaying]]></category>

		<guid isPermaLink="false">http://raelifin.com/?p=244</guid>
		<description><![CDATA[A friend of mine wanted me to post this minimalist RPG system I wrote back in 2007. So, here it is. I suggest using it as a starting point in making something that works best for your group. Yes, this is the entire rulebook. The GM is always right. Characters Each character has a number [...]]]></description>
			<content:encoded><![CDATA[<p><img style="float: right; margin-left: 5px;" src="http://farm4.static.flickr.com/3144/3093982684_79d7b3ea6a_m.jpg" alt="[Photo of Dice]" />A friend of mine wanted me to post this minimalist RPG system I wrote back in 2007. So, here it is. I suggest using it as a starting point in making something that works best for your group. Yes, this is the entire rulebook.</p>
<p><span id="more-244"></span></p>
<div style="border: 1px solid; padding: 5px; clear: right;">
<p><strong>The GM is always right.</strong></p>
<h2 style="text-align: center;">Characters</h2>
<p>Each character has a number of traits, abilities, and skills.</p>
<p>Traits represent the raw talent or power your character possesses in a field.<br />
Example traits might include cunning, intelligence, fortitude, or agility.<br />
Normally, traits can be -2 through +4.</p>
<p>Abilities represent general skill-sets which the character has learned.<br />
Example abilities might include martial arts, stealth, acrobatics, or magical lore.<br />
Normally, abilities can be +1 through +4.</p>
<p>Skills are more specific than abilities, and represent specific prowesses.<br />
Example skills might include tracking, lock-picking, feinting, or swimming.<br />
Normally, skills can be +1 through +5.</p>
<h2 style="text-align: center;">Challenges</h2>
<p>Before playing, pick a kind of dice to use (I prefer d6) and stick with that for the rest of the game.</p>
<p>All challenges are made by rolling dice and counting the number of results that equal or exceed a Target Number.<br />
Target Numbers are based on the inherent difficulty of an action. Jumping across a small gap would be easy, while jumping across a large gap would be hard. Don&#8217;t even bother rolling trivial challenges.</p>
<table>
<caption>Target Numbers:</caption>
<tr>
<th>Difficulty</th>
<th>d6</th>
<th>d10</th>
<th>d20</th>
</tr>
<tr>
<td>Easy</td>
<td>3</td>
<td>4</td>
<td>7</td>
</tr>
<tr>
<td>Normal</td>
<td>4</td>
<td>6</td>
<td>11</td>
</tr>
<tr>
<td>Difficult</td>
<td>5</td>
<td>8</td>
<td>15</td>
</tr>
<tr>
<td>Extreme</td>
<td>6</td>
<td>10</td>
<td>19</td>
</tr>
</table>
<p>For any solo challenge, the GM will require a certain number of successes for the character to succeed in their action. In many instances (such as music or athletics), more successes indicate a more impressive performance.</p>
<p>When characters oppose one another, treat it as though both characters were performing solo challenges where the victor is the one with the most successes. In this circumstance, the degree of success is equal to the difference, rather than the absolute number of successes.</p>
<p style="text-align: center;">* * *</p>
<p>A player rolls a number of dice for a challenge depending on their character&#8217;s attributes and the circumstances of the challenge.</p>
<p>Each challenge uses a trait, chosen by the GM. The player then chooses one ability and one skill. If the GM decides that either are unfit for the test at hand, the player cannot use them (and may not change their choice). The player then rolls a number of dice equal to:</p>
<p><strong>1 + trait + ability</strong> (if any) <strong>+ skill</strong> (if any) <strong>+ circumstance</strong> modifiers (if any)</p>
<p>Unless a challenge is impossible, all characters get one base die, which cannot be removed due to modifiers.</p>
<p>Circumstantial modifiers can include assistance from others, low visibility, weariness, wounds, magic, distraction, etc.</p>
<h2 style="text-align: center;">Character Creation and Advancement</h2>
<p>Before the game can begin, the GM must provide a list of traits. These traits should optimally cover all character archetypes that players want to use.</p>
<p>All traits start out at +0. Each player has two points which can be spent increase a trait (+0 -> +1 or +1 -> +2). Traits may be reduced to -1 to gain an additional point. Normally, a trait cannot be increased above +2 or reduced below a -1.<br />
If a player wants to play a specialist, however, they may opt to reduce a +0 to a -2 in order to increase a +2 trait to a +3. This specialization may only be done once.</p>
<p>Starting characters then gain 20 &#8220;triumphs&#8221; which they can use to buy up skills and abilities, described below. 20 triumphs is intended to represent a starting hero, and the GM is encouraged to allot more for creating &#8220;experienced&#8221; heroes.</p>
<p>&#8220;Triumphs&#8221; are the units used to keep track of character advancement. Whenever a player does something difficult and important, the GM is suggested to give them a triumph. When a character is in a situation where they have the opportunity to increase a trait, ability or skill, (such as when creating a character) they may burn triumphs to do so. The number of triumphs it takes to move from one number to another depends on what is being increased.</p>
<table style="font-family: monospace;">
<caption>Cost of increasing traits:</caption>
<tr>
<td>-2 -> -1 = 1</td>
</tr>
<tr>
<td>-1 -> +0 = 2</td>
</tr>
<tr>
<td>+0 -> +1 = 3</td>
</tr>
<tr>
<td>+1 -> +2 = 4</td>
</tr>
<tr>
<td>+2 -> +3 = 5</td>
</tr>
<tr>
<td>+3 -> +4 = 7</td>
</tr>
</table>
<table style="font-family: monospace;">
<caption>Cost of increasing abilities:</caption>
<tr>
<td>+0 -> +1 = 2 (Gaining a new ability)</td>
</tr>
<tr>
<td>+1 -> +2 = 3</td>
</tr>
<tr>
<td>+2 -> +3 = 4</td>
</tr>
<tr>
<td>+3 -> +4 = 6</td>
</tr>
</table>
<table style="font-family: monospace;">
<caption>Cost of increasing skills:</caption>
<tr>
<td>+0 -> +1 = 1 (Gaining a new skill)</td>
</tr>
<tr>
<td>+1 -> +2 = 2</td>
</tr>
<tr>
<td>+2 -> +3 = 2</td>
</tr>
<tr>
<td>+3 -> +4 = 4</td>
</tr>
<tr>
<td>+4 -> +5 = 6</td>
</tr>
</table>
<p>If the task of learning is difficult (such as without a teacher) the GM may require a challenge to improve.</p>
<p>Characters start with whatever items or equipment are considered appropriate for the setting and the character. If in doubt, ask the GM.</p>
<h2 style="text-align: center;">Combat</h2>
<p>In addition to traits, abilities, skills and gear, characters have a number of health boxes which are an abstract representation of their physical condition. The number of health boxes a character has will depend on the style of game that the GM is running and the physical toughness of the character. GMs are encouraged to tie a trait, like &#8220;Health&#8221; or &#8220;Fortitude&#8221; to the number of Health Boxes a character receives (minimum 1). I suggest using a base of 10 boxes. Gritty games may go for 5 or even 3. When a character takes damage, mark off a number of health boxes. When the last one is marked, the character typically goes into a coma or dies, depending on the circumstances. A character&#8217;s health should always be taken into account when determining the &#8220;circumstances&#8221; of a challenge.</p>
<p>Combat can also vary, depending on GM. Presented below are three ways that I suggest handling combat.</p>
<h3>Fearsome Challenges</h3>
<p>Perhaps the simplest way to deal with combat is simply to make it a series of deadly challenges.</p>
<p>Imagine a group of explorers venturing through a forgotten tomb. They come upon a spike-laden pit trap. Jumping across the pit might take two successes against a difficult target number, with failure dealing 4 health boxes of damage, and the extra problem of getting out. Now imagine the explorers come across an ancient tomb guardian. The guardian is slow, and all the players can take actions before the guardian acts. When it does, it swings it&#8217;s hammer at a single character, forcing a challenge to either block or move with failure meaning the victim takes 4 health boxes of damage. Under this system of combat, there is no difference between an environmental hazard and an intelligent opponent, except that opponents are generally deadlier and more adaptable.</p>
<p>This system allows the GM to avoid rolling dice, which lets them stay focused on the group. To determine the number of successes to dodge the attack of a humanoid opponent, just assume that they roll all average. That is, if they are looking for a &#8220;normal&#8221; target number, just make their degree of success = half their dice pool.</p>
<p>Using this system, determine if enemies act first, then take turns where the whole party acts in whatever order they want (though only within reason).</p>
<h3>Single-Action Roundtable</h3>
<p>Good for dueling, this system breaks combat down into a number of rounds, where each player takes a single action.</p>
<p>Each character, at the beginning of combat, performs a challenge to act first, comparing degrees of success. In the case of a tie, the character with the highest &#8220;agility&#8221; trait (or equivalent) acts first, or the GM simply decides. Each character then acts in turn, taking a single action. Typical actions involve directly attacking the opponent, or modifying circumstances to get more dice on a future attack.</p>
<p>Attacks are handled as contested challenges with the defender. Stunned or surprised characters cannot defend. If the attacker wins, he or she deals damage equal to their degree of success (plus any modifier from weapon or armor). If the defender wins, they gain a counter-attack advantage on their next turn of a single die.</p>
<h3>Bloodbath</h3>
<p>This system is good for games that favor violent, or unpredictable combat. In Bloodbath, all characters decide on their actions in secret and act simultaneously. The results of a round of combat depend on the nature of the actions involved.</p>
<p><strong>Independent Non-Challenge:</strong> An example of this is two characters that run away from each other. No rolls are made, and both characters successfully withdraw.</p>
<p><strong>Independent Challenge:</strong> An example of this is two characters that attack each other. Each character rolls a solo challenge to hit and deals their raw successes as damage to their opponent (plus any modifier from weapon or armor). This can mean that both characters kill each other, if they roll high enough.</p>
<p><strong>Conflicting Challenge:</strong> An example of this is a character that attacks a defending or fleeing character. The action is made as an opposed challenge, where the victor is the only one to have their action take effect, and their degree of success is the difference between the rolls.</p>
<p><strong>Asynchronous:</strong> An example of this is a character that attacks a character trying to focus on something. In instances where one action (like attacking) is unaffected by another action (like focusing), but not vice-versa, the action that is not effected works and the other is disrupted.</p>
<p>Bloodbath can become unwieldy in non-one-on-one situations, and favors power in numbers.</p></div>
</div>
<p><br/></p>
<p><em>Thanks to gcardinal for <a href="http://www.flickr.com/photos/30883129@N08/3093982684">the photo</a>.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://raelifin.com/meatspace-games/mastery/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Steven the Blind Millipede</title>
		<link>http://raelifin.com/meatspace-games/steven/</link>
		<comments>http://raelifin.com/meatspace-games/steven/#comments</comments>
		<pubDate>Wed, 01 Jul 2009 17:44:50 +0000</pubDate>
		<dc:creator>Raelifin</dc:creator>
				<category><![CDATA[Meatspace Games]]></category>
		<category><![CDATA[boardgame]]></category>
		<category><![CDATA[game]]></category>
		<category><![CDATA[game design]]></category>
		<category><![CDATA[Game Design Concepts]]></category>
		<category><![CDATA[GDCU]]></category>
		<category><![CDATA[prisoner's dilemma]]></category>

		<guid isPermaLink="false">http://raelifin.com/?p=74</guid>
		<description><![CDATA[So a while back I saw that Ian Schreiber was offering to teach a game design class to the general public over the internet. &#8220;Sounds great! I&#8217;m in.&#8221; Well, it started on Monday. Pretty cool, so far, given that there are over a thousand students and it&#8217;s completely impersonal. The first &#8220;class&#8221; was more of [...]]]></description>
			<content:encoded><![CDATA[<p>So a while back I saw that <a href="http://teachingdesign.blogspot.com/">Ian Schreiber</a> was offering to teach a <a href="http://gamedesignconcepts.wordpress.com/">game design class</a> to the general public over the internet. &#8220;Sounds great! I&#8217;m in.&#8221;</p>
<p>Well, it started on Monday. Pretty cool, so far, given that there are over a thousand students and it&#8217;s completely impersonal. The first &#8220;class&#8221; was more of a <a href="http://gamedesignconcepts.wordpress.com/2009/06/29/level-1-overview-what-is-a-game/">blog talking about game design terminology</a>. The &#8220;in-class&#8221; assignment was to make a race-to-the-finish type game. I have a lot of experience coming up with stuff like this, so it was pretty easy. I ended up making Candy Land + <a href="http://en.wikipedia.org/wiki/Prisoner%27s_dilemma">The Prisoner&#8217;s Dilemma</a>, and I haven&#8217;t played it, so I&#8217;m not sure if I overlooked anything. I did add one kinda-innovative element to it though, which is the ability to trick your opponent into sabotaging their own progress. Let me know if you play it!</p>
<p><span id="more-74"></span></p>
<blockquote><h3>Game Basics</h3>
<p>Everyone assumes &#8220;Faerie Land&#8221; is a garden. Why? I don&#8217;t know. It&#8217;s not like they&#8217;ve ever been there.</p>
<p>Fae actually live on a giant millipede named Steven. A <strong>blind</strong> millipede named Steven.</p>
<p>You&#8217;re a couple of pixies (of course). And if there&#8217;s one thing pixies are good at, it&#8217;s not getting things done.<br />
Unfortunately, the great Fae Ball is tonight, and all the other faeries are busy working. Too bad Steve is headed toward a cliff.<br />
Nobody listens to either of you&#8230; you&#8217;re only pixies, after all. I guess it&#8217;s up to you two to tell Mr. &#8220;I have no eyes&#8221; that he&#8217;s about to send the whole world into the abyss.</p>
<p>Steve is soooo long, though, and you only have <strong>six</strong> turns to get from the royal palace (on his butt) to his ears&#8230; or whatever millipedes have.</p>
<p>Oh, and did you ever wonder why pixies are so bad at getting things done? It&#8217;s because they can only do things by getting permission from non-pixies. That, and all pixies fight constantly, and pull pranks to make each other fail.</p>
<p>You&#8217;ll each have five cards from the deck. Each card represents someone you can get help from.</p>
<p>During a turn, you each put a card down on the table, making sure it&#8217;s covered by your hand. When you both have cards down, remove your hands to reveal them.</p>
<p>If your card is face-up, you&#8217;re asking for permission, but if it&#8217;s face-down then you&#8217;ve decided to prank the other player.<br />
If both of you are asking, you both do what is on your respective cards.<br />
If both of you prank each other, nothing gets done (&#8230;typical).<br />
If only one of you asks for permission, while the other one pranks. The prankster steals the other pixie&#8217;s card and does what&#8217;s on it.</p>
<p>After each turn, you both draw another card, and put the cards played this turn in a discard pile.</p>
<p>Now remember, it doesn&#8217;t really matter that Steven stops before he gets to the cliff&#8230; it matters <strong>who</strong> tells him! That pixie will probably be the star of the Royal Ball while the other one gets to take coats&#8230; or something.<br />
If seven turns go by, and you two haven&#8217;t still managed to do such a simple task, the whole world ends, but the one who is furthest from the head has the best chance to jump off (after all, it&#8217;s not about <strong>if</strong> you die&#8230; it&#8217;s who dies <strong>first</strong>).</p>
<h4>Fine print</h4>
<p><small>If a card would make you go past Steve&#8217;s head, that&#8217;s the same as landing on his head. (If a card would make you go past the palace, that&#8217;s the same as landing on the palace.)</p>
<p>Cards placed face-down are revealed before going into the discard.</p>
<p>If player one lands on Steve&#8217;s head, but then switches places with player two, player two wins.</small></p>
<p>**************<br />
<h3>Game Pieces</h3>
<p> Board depicting a giant millipede with no eyes, ten segments and a palace on the segment furthest from the head. It should be clear that the palace is the start, the head is the end, and that each segment is a space. Optional chasm in front of Steve. Optional characters (see cards) on Steve&#8217;s back.</p>
<p>Two pixie figurines that can both easily fit on a single segment. </p>
<p> A twenty-card deck of custom cards. Cards need to be small enough to be covered easily by a child&#8217;s hand, and similar enough on both sides to reduce the chance of revealing your move accidentally.<br />
 Each card has a simple drawing of a magical character and instructions. Bellow is a list of all instructions, and the number of copies of this instruction in the deck:<br />
  * Move forward four segments. (1)<br />
  * Move forward three segments. (5)<br />
  * Move forward two segments. (4)<br />
  * Move forward one segment. (3)<br />
  * Move backward one segment. (2)<br />
  * Move backward two segments. (2)<br />
  * Move backward three segments. (1)<br />
  * Switch places with your opponent after everyone moves. (2)</p></blockquote>
<p><strong>EDIT</strong>: After light playtesting, I&#8217;ve found that the &#8220;move backward&#8221; cards turn out to be more fun if they read as &#8220;the opponent moves forward.&#8221; This makes winning the game <em>much</em> easier, and makes it a bit more tense/interesting.</p>
]]></content:encoded>
			<wfw:commentRss>http://raelifin.com/meatspace-games/steven/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Zombie Corp.</title>
		<link>http://raelifin.com/code/zombie-corp/</link>
		<comments>http://raelifin.com/code/zombie-corp/#comments</comments>
		<pubDate>Fri, 20 Mar 2009 15:51:18 +0000</pubDate>
		<dc:creator>Raelifin</dc:creator>
				<category><![CDATA[Code]]></category>
		<category><![CDATA[game]]></category>
		<category><![CDATA[java]]></category>
		<category><![CDATA[programming]]></category>
		<category><![CDATA[rapid-prototype]]></category>

		<guid isPermaLink="false">http://raelifin.com/?p=8</guid>
		<description><![CDATA[During my first year of college I showed up one Friday for my C++ class only to find that it was canceled. Not wanting to simply go home quite yet, I talked one of the other teachers into letting me sit in and participate in one of the upper level game-development classes. We were broken [...]]]></description>
			<content:encoded><![CDATA[<p>During my first year of college I showed up one Friday for my C++ class only to find that it was canceled. Not wanting to simply go home quite yet, I talked one of the other teachers into letting me sit in and participate in one of the upper level game-development classes. We were broken into teams and instructed to design a game to work on for the rest of the quarter. I, of course, didn&#8217;t have to code anything, being in the class just for that day, but I jumped in anyway.</p>
<p>Most of the class was thinking of making an obscenely huge strategy game akin to Risk meets Monopoly, which just so happens to be the sort of design which I despise. Having spent many long years learning the hard way to design as small as possible, I helped my team brainstorm a small, grid-based, strategy game based on resource management and simple unit-movement. My hope was that the project would be basic enough that it could be running with an initial rule-set within the week and that the remainder of the term could be devoted to polishing the interface/graphics and working on the rules. (I was only vaguely aware of it at the time, but this sort of thinking would expand into rapid-prototyping, playtest-heavy, and iterative design philosophies in my own work.)</p>
<p><span id="more-8"></span></p>
<p>We decided on a zombie theme, with the twist that the zombies were actually corporate pawns, and the necromancers were CEOs. It&#8217;s kinda vanilla, but it was a 1-hour design within a group of relative strangers. We presented our designs for the class and they decided to work on Risk-Monopoly. That weekend, in about 8 hours*, I built a working alpha for the game:</p>
<p>EDIT: If the images aren&#8217;t working, you may need to <a href="http://raelifin.com/code/zombie-corp/">view this post by itself</a>.<br />
<applet code="master.CoreApplet.class" archive="http://raelifin.com/files/corperateZombies.jar" width="575" height="575"></applet><br />
<blockquote><strong>Rules:</strong><br />
The player on the left (pink/green) goes first. And then blue player takes a turn, and so on.<br />
To move an army, drag them to an adjacent square. (They move like kings in chess.)<br />
Armies are composed of undead: zombies, lawyers, or both.</p>
<p>Each space is commercial, residential or corporate (Starbucks, house or building). At the beginning of each turn, you get cash to buy lawyers with and new interns to turn into zombies. The goal of the game it to capture your opponent&#8217;s skyscraper. The income is as follows:<br />
Corporate Space: +$5,000 &#038; +5 interns / turn<br />
Commercial Space +$2,000 / turn<br />
Residential Space +2 interns / turn</p>
<p>Each turn you get one action (upper-right), in addition to moving each unit. Select a board space then chose:<br />
PROMOTE: Turn all interns into zombies at the selected space.<br />
HIRE: Hire lawyers for $5,000 each at the selected space.<br />
DEVELOP: Selected commercial or residential space now produces 2N+2, where N = current production. (Units are single interns or thousands of dollars.) Each space can only be developed twice.</p>
<p>If you move into a space that has an enemy army, you deal damage to them, killing a number of units. If you defeat all units in a space, you capture it. An army with both lawyers and zombies loses its zombies first. Lawyers deal roughly 5x<br />
more damage to zombies (I forget the actual multiplier).</p></blockquote>
<p>It&#8217;s really a very boring game, but the idea is that it&#8217;s playable and (mostly) bug free. Additional rules and features can easily be added onto the skeleton in an attempt to make it more engaging. At the end of the week you&#8217;ll have a game, though, and you&#8217;ll have a good impression of roughly how fun it is. This last part is vital, I think, to good game design.<br />
<strong>Rapid-prototyping lets me play a game with very little time investment. This lets me determine whether it is worth making.</strong></p>
<p><small>* This amount of time is actually quite excessive for such a simple game. At the time I wasn&#8217;t using <a href="http://slick.cokeandcode.com/">Slick</a>, and I didn&#8217;t have much experience with applets.</p>
<p>Disclaimer: I do not own any of the graphics used in the game, but I feel that they are <a href="http://en.wikipedia.org/wiki/Fair_use">used fairly</a>. Unlike most of my work, this game is not open source, and I ask that you do not redistribute it without permission. Its sole intent is to showcase what I did one weekend, and maybe talk a little about game-programming. <img src='http://raelifin.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </small></p>
]]></content:encoded>
			<wfw:commentRss>http://raelifin.com/code/zombie-corp/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
