Download it here.

Goals are pretty much repeating what I said last time:

• Keep the same art style as last time.  I sketched things out on paper and scanned them in so I could colorize.  Keeping with bold colors and gradients is probably what I’ll do.
• KISS – Keep It Simple, Stupid!  Making something too complex is just a recipe for a headache at 1pm on Sunday afternoon.
• Make useful additions to the basecode that can be used in later competitions.  The screenshot stuff is an example of something I did previously that helps out a lot.
• Finish most of the work by Saturday night so I can spend Sunday polishing.
• Don’t run into dumb problems that eat up eight hours.

Tools in use:

• Java 6 SDK (though last time I included a version for JDK 5)
• Eclipse IDE
• Photoshop, maybe some Illustrator
• DrPetter’s sfxr for sound effects
• Audition, if I can get it to play well with my sound card
• HP OfficeJet 6450 All-In-One for scanning doodles
• No Fear Energy Drink Sugar Free (Hopefully Boris Said and Carter Racing will run some Sprint Cup this year)
• Everlasting Gobstoppers
• mIRC for chattery
• Killer Game Programming in Java and the base code I mentioned above.

Can’t wait to see what the theme is.  Hope it’s a fun one!

This was probably the best Ludum Dare weekend I’ve had.  My game was more than just a tech demo or an ‘unfinished’ idea.  Of course, they never are truly complete after 48 hours time; there is always something else that can be tweaked or added.  When all was said and done, however, my entry was a playable game.

Background

The theme was not one that I had put much thought into before it was announced so I really had zero ideas at Go time.  One thing that kept popping into my head was the Kroz series of games by Apogee software back in the late 80’s/early 90’s.  They’re all pretty much the same engine with a new collection of levels, but one was called Caverns of Kroz.  The object of the game is to take your hero through twenty or thirty levels to find or capture some relic.  Along the way you had to run, whip or out-maneuver swarms of monsters and solve puzzles.  I had always thought those games were neat, and it would be interesting to try and ‘recreate’ some of that nostaliga.  Caverns of Kroz didn’t have anything special that made it more caverny than the rest in the series, but I thought I could do better with actual graphics instead of ASCII art.

Kingdom of Kroz

LoneStranger's Caverns

Graphics

One of the first things I do in a LD is grab a piece of printer paper and start sketching some objects.  More is better, even if I think I may not use them.  For LSC, I sketched a few doodles and scanned them in.  The designs were done in homage of the original ASCII characters and colors.  For example, my monsters look remiscent of the Ä, Ö and Ω characters.  The first problem I had to resolve was how big to make the map.  Kroz uses something like 60×24, but I don’t really like how smushed that is.  I wanted a square ratio on an 800×600 pixel window.  This led me to pick 16×16 as the tile size, which seemed small to me.   For the first couple tiles, the floor and the walls, I used 16×16 image to create them.  That went OK.  Next I took a look at my scans to turn them into tiles.  I did an overhead view of the player, basically just a head and shoulders.  I created the tile originally as a full 120×120 image with margins.  I colored him yellow and red like the Kroz hero.  I copied the merged image and pasted it into a new document that I then resized to 32×32.  Inside the drawing routines I have it again resized on the fly as 16×16.  The reason for this was that I may want to add a ‘zoom’ feature to the game in the future and it would be great if the images didn’t get pixelated.  I followed the same procedure for all the rest of the tiles.

The style of the art is not much different than the other LD entries I’ve done.  I don’t try to draw the straightest or the best.  I just draw to my ability.  Those are then scanned in and then modified in Photoshop.  Since I shrunk these down, you don’t see the imperfections as much, and maybe that’s better?  I don’t think some people ‘get’ that the imperfect art is part of my style and I think I get marked down for it sometimes.

Coding

This is the fourth time I’m using the same general base code for my LD entry.  I think it shows because I have a hang of it’s abilities and limitations and I can get what I need to get done faster and more efficiently.  Also, each LD I add more basic functionality to it so I don’t have to reinvent the wheel each time, as they say.  Additions this time are an unfinished menu system and a tile/map data structure.

Most everything that I coded worked fairly soon thereafter, even the changes that take 30 minutes in between builds.  I think I had only two major problems: monsters moving over walls and monsters not dying when they move onto the player.  The first problem was because I couldn’t figure out why my collision detection logic was failing for monsters.  And it wasn’t.  I had an errant semicolon tagging along the end of an if statement.  My logic was fine and the if was completing an empty statement.  Then the next line moved the monster anyway.  The second problem was weird in that the monsters would sometimes die when they moved into the player, but not always.  A majority of that problem was due to how I keep track of the monsters.  I have two references for them.  One is in a two dimentional array similar to the tile map.  Either the cell has a link to a monster, or it’s null.  The second reference is in a linked list.  The grid is used for monster-monster collision detection since I only have to check the cell next to the monster for another monster.   The linked list is used when I have to traverse each monster object and is faster than checking every cell in the grid.  It’s actually a great idea but I was trying to solve the monster-player collision problem without actually having a fully implemented monster-monster collision.  It turned out that the monsters were moving into the same spot and the second monster was overwriting the first monster’s entry in the grid.  It was weird but once I finished implementing that code the rest fell into place.

These two problems cost me about eight hours split over Saturday night and Sunday morning.  If I didn’t have those problems, then my game would have been that much more complete.

I didn’t try to do anything too fancy in my code.  I could have spent more time doing things in a more efficient way for the future, but instead I hardcoded some functions just to get it done.  For example, I have eight different functions for the different directions in many parts of the code.  Those could probably be pared down to one in each situation if I passed some variables in.  I’d also like to combine the collision detection and movement between the player and the monsters.  Maybe base them from the same Mobile class or something.

What I did Wrong

Other than those two issues that I mentioned above, there wasn’t a whole lot that I did wrong while coding.  I did have a few too many distractions over the weekend.  My folks came over on Saturday to swim (which is great because it was triple-digit weather) and have dinner so I lost a few hours there.  That by itself wasn’t a problem but when I was actually coding I had the TV on which split my attention.

I also forgot to tie the score in with anything being done by the player.  Not a big deal, since score isn’t really much in the game yet, but it should have added some points for killing monsters and grabbing gems and whips.

Apparently my sounds were a bit harsh.  I used DrPetter’s sfxr to create them, but I must have used some weird settings because they sound fine through my 5.1 speakers, but they are harsh through headphones.  I guess I’ll have to do sound through headphones next time and hope that translates through the speakers.

What I did Right

I think I was helped by trying to emulate the Kroz series of games and it wasn’t because I had a model to ‘copy’ from.  I think the key was that the limits on what I was setting out to accomplish were already fairly firm.  I didn’t have to try to build in some weird functionality for the future, since I already knew where I was ending up.  The other LD weekends started with an idea that was to be flushed out later.  The only problem is that later usually doesn’t come and I am stuck with an incomplete game or a complete ‘thing’ that isn’t fun.

What I Wanted to Do After Last Compo

I wanted to work on my basecode after LD48 #14, and I did that.  I also wanted to scale down my goals, and I think I was able to manage my goals this time around by not setting them too high.  I think it’s a win.

What’s Next?

I’d like to continue with this project and there are a few obvious things I can do.

• Make the code more efficient and easier to read
• Profiling execution.  I haven’t tested lots of monsters or animated tiles yet, but it will probably suffer from performance issues.
• Level editor
• More objects and tiles
• Better level file format
• Continue adding basic functions to the basecode

So Mortem?  This thing’s just getting started!

The level’s goal is pretty straight forward.  Capture the airport, ferry a trooper over to an island and capture the city, all in 40 turns.  It’s not that easy though, as the enemy uses snipers and stealth tanks to stop you.  Whenever I would get close, they would nail me from a distance.  I could never get that airport and when I did, I would run out of time before I could get a unit over to the island.  After the first five or six failures, I started trying different strategies until I came across one that worked.

The default division is the Swarming Wasps.  At first they don’t seem like the best pick for the map.  They are cheap to build, but can’t use terrain very well and capture slowly.  They will be the key to victory,  however.  The enemy is the Black Bears and they have no real strengths or weaknesses.

To beat this level there are three things you have to do:

• Counter their snipers and stealth tanks with your own snipers and regular tanks
• Stop their reinforcements
• Use your division’s special abilities

At the start of the level, move your units up the two roads; one on the west of your main base and one on the east.  On the west road, capture the building.  On the right road, don’t bother with the building; your units will just get killed trying to capture it. The forest is helpful here, because it mostly keeps the enemy blocked from coming directly down to your base and it gives your units a place to hide. As soon as you can, make two snipers and send then up into this forest and into stealth mode.  Use your scouts to get them up there faster.  A truck would help you ferry guys faster as well, so build one in the next turn or so.  Don’t go rushing into the area north of the forest.  You’ll just get cooked.  Use your snipers to pick off their units as they get close and un-stealthed.  After the city along the west road is captured, send your trooper west to the factory and capture that for an easier time inserting units into the battle.  If possible, capture the other building as well.

This map gives you the ability to call in an Air Strike.  Don’t waste it on single units unless you are poorly matched up in an inevitable face-off.  If I didn’t see at least two enemy units in a line within five squares, I waited a turn or two to use it.  Don’t forget it exists, and use it to soften up units before making your attacks. Once you use it, you’ll have to wait for it to build up again.

Just as you get a special unit to Air Strike, the enemy has a special EMP-like attack that will cause the target and nearby units to not be able to move for the next turn.  They tend to use it well enough to slow you down right before you are about to make a move.

While you’re capturing on the left side and snipering in the center of the map, you’ll want to help yourself out by slowing the enemy reinforcements.  I’ve had success moving either a tank or an anti-aircraft gun up the east road to their factory and just camping out there.  If you wait until your trooper is capturing the factory in the west, you may be able to avoid trouble as they move units west to counter. They will occasionally try to destroy the unit on the factory, but if you keep the number of their units low, the AI will prefer to reinforce the battle rather than free their factory.

Scouts are helpful in revealing stealthed enemy units so that your snipers and tanks can attack.  Stealth units are not as effective when they aren’t stealthed, so you can take advantage of that.  On the flip side, your own stealthed units can help stall the enemy, as they will stop moving and end that unit’s turn when they come across one of your snipers waiting in hiding.  When they stop moving, it usually means they have missed a chance to attack so you should strike first with a tank or other sniper.  Afterward, move your unit away and back into stealth mode.

So far, I haven’t mentioned anything about capturing the airport.  That’s because you don’t need to.  Yes, I know that is what the mission briefing tells you to do, and I’m sure it’s possible, but that’s not the only option.

Your division has two abilities that you can take advantage of.  Double Shot creates two stealth fighters at half strength near your base.  As soon as this ability is available, use it.  Then send those two up the left side of the map.  Park them over a captured city to recharge them if you want, but it’s not totally necessary.  I’ve had to use them in combat a few times to protect the capturing trooper, but that’s not their main goal.  When you get a chance, send them up to the island in the northwest corner that doesn’t have the city on it.

The second ability of the Swarming Wasps is Eject.  This destroys one of your fighters, but does 100% damage to that square and 75% to adjacent squares.  It also dumps a half-health grunt on the ground.  It can only be used next to or on an enemy unit.

Well, what do you know?  After awhile, the enemy decides to reinforce the target island with an anti-aircraft gun.  You might think that is bad, but in actuality, you need it there.  Since the Eject ability requires an enemy to be nearby, you’ve just been handed victory.  Take one of your fighters and end it’s turn over the anti-aircraft gun.  Do the moves for the rest of your units.   If you aren’t in the middle of combat, send your units up between the water and the enemy’s second factory, and be sure to sit someone on the actual factory to stop the enemy from building anything.  Go back to the fighter and select Eject.  It should blow up the anti-aircraft gun and leave you with that damaged grunt.  Take the unit and begin capturing the city.

You aren’t home free yet.  Once you start the capture, the enemy will bring in yet more reinforcements from off the map.  An anti-aircraft gun and a rocket launcher.  The units you moved near the water should be able to overrun these two before they can do any damage.  Keep capturing the city, destroying any other enemy units you find, and prepare your victory speech.

I hope that this guide can help at least one person get unstuck on this level.  This is one of my favorite PSP games and an extremely well-done representative of the genre.  If this solution helped you, please comment and let me know!  If you need more assistance, well, I can try that too.

• Classes are now organized into the package net.lonestranger.common, game and network.
• Network isn’t really too useful yet.  The only class that exists in it is called Report.  It’s job is to take a string of data and send it via POST to a website, where it can be digested as fit.  For example, sending scores back to a central repository.
• You can take jpg screenshots by hitting F10.  They are named based on the current date/time and dumped into the working directory. 

Here is the link to download it.

I didn’t really list my goals in my declararion post a few days ago, so I’ll do it now.

• Keep the same art style as last time.  I sketched things out on paper and scanned them in so I could colorize.  Keeping with bold colors and gradients is probably what I’ll do.
• KISS – Keep It Simple, Stupid!  Making something too complex is just a recipe for a headache at 1pm on Sunday afternoon.
• Make useful additions to the basecode that can be used in later competitions.  The screenshot stuff is an example of something I did previously that helps out a lot.
• Finish most of the work by Saturday night so I can spend Sunday polishing.

Ok, time to finish work and then I’m off to Thanksgiving, The Sequel, but I’ll check in after 8pm Pacific tonight to see the theme I need to start thinking about.  I expect everyone to be in FULL CODE MODE when I get back. 

So let’s take a look at what I’ll be using…

The two additions are the USB devices.  I actually used the mic last compo to make the sounds for the monster, arrows and stair-stepping in my tower game.  I will have to go stock up on Gobstoppers and No Fear Energy Drink.

I’ve just fired up Eclipse to create my workspace for this Friday.  It helps to have a clean app that opens up a window so I can get down to business once the theme is announced.  I wanted to add some functionality to the base code to make things easier.  For compo 12, I added the screen shot button so that I could easily take snaps of my progress.  This time, I want to integrate a simple logging class to make debugging easier.  If I get it done in time, I’ll link to a new base code zip file later in the week. 

Anyway, I’m looking forward to completing a decent entry.  One of my personal goals is to crack the top five in any of the game categories.  It was nice last time to get in the top five for Food, but it would be even better for a game category.

See you then!

It’s a concept that I had been toying with this past week, jotting down some ideas and refining it along the way.  Quite simply, it’e the game Breakout, only with a twist.  In regular Breakout, you move the paddle back and forth on the bottom to keep the ball from falling off the screen.  At the same time, you are trying to use the ball to destroy all the bricks on the screen.  In my game the computer plays the part of the paddle and you instead try to defend a goal at the top of the screen by placing bricks. 

It’s a neat idea, but I by no means was able to implement all my ideas.  The number one thing that was lacking is multiple types of bricks.  This version only has two: normal and 2X Hit.  As you can probably guess, normal takes one hit to be destroyed and 2X Hit takes two.  I wanted to add more bricks that did weird and interesting things when the ball hit it, like explode or eat it. 

You build your wall of bricks by buying them from money you’ve earned while playing.  So far, the only two ways you can earn money is to play, where you get one credit every so many seconds, or when the computer misses the ball with the paddle and it goes off the bottom of the screen.  Eventually you’ll be able to get money by doing other things.

One thing that doesn’t seem to work very well is the collision.  The ball seems to react well when it hits the top or the bottom of the bricks, but if it hits the side of two bricks, it can sometimes bounce in a way that causes it to go ‘inside’ the wall.  I have a few ideas on fixing that but I didn’t have enough time to implement them.

The AI could be improved, letting it think ahead instead of having it just react to the current position of the ball.  If I project the location it will be at when it gets to the bottom, I could have the paddle waiting for it.

There are no skill levels implemented.  Smarter AI, less money and multiple bouncing balls would make it more challenging and could be set to differing degrees.

I also didn’t do any sounds for it, as the compo requires that all resources be generated within the 48 hours and my recording soundcard is not quite working.  I will create some for the post-compo version of the game.  Same for music.

I tested it on the Sun JVM 1.6.0, though it should work on on JVM 1.5.0.  It will not work on the JVM 1.4.2, as it requires System.nanoTime() that was introduced in JVM 1.5.0.

I programmed it in Eclipse 3.3.2, and used Photoshop for the graphics.

You can download the game here or the source code here.

[update: changed the above link to the .zip file.  The jar just wasn't handling some class-pathing stuff well and I don't have time to troubleshoot it right now.]

When all is said and done, and I’ve completed a game, I’ll post it here.  If for any reason I don’t get it done… well, I’ll still post something.

So if you have a (mostly) free weekend and you want to try your hand at designing and coding a game in 48 hours, come by the compo. Even if you don’t have the time, come by and check out the reports and progress of those who are.  You can also check my personal coding blog at LD.

In this first jam, they created a game called Gravediggers.  The post includes a video with five people playing through a round.  The graphics themselves remind me a little of the original Joust game, with the brown floating platforms and blockish characters.   The players are represented by small rectangular blocks, and the playing field offers a lot of space to run around and shoot.  The object is to kill the rampant zombies with a gun and collect the heads to return them to the crypt for points.  Heads of the other players can be returned for extra points.  The side-view perspective shows generated terrain and two crypts randomly around the field.  The players hop from platform to platform, and over little hills.  They can also shoot through the terrain if they can’t get around it to score those zombie heads.

This reminds me of Ludum Dare’s 48 Hour Game Programming Competition held twice a year (voting starts for the LD11 theme April 11th).  There are a lot of neat little games that come out this competition, many of them that look as good or better than the NES games we used to spend hours playing as kids.  They’re just as fun too.  Entrants are allowed to use a wide range of development tools and can create on any platform they wish.  The only caution is that if other people can’t play your game, they can’t vote on it, so most entries are done on Windows.  If you are an amateur game programmer, give the LD11 a shot.  If I can get a decent desk for my computer by April 11th, I may try to enter.  Trying to type with the keyboard on an endtable is not fun.  I submitted a sad entry for LD2, many years ago.  Sad enough that I won’t bother to show you.

Shake these two things together in a glass, add a little lemon–here’s my third topic.

Sony hasn’t moved forward with any kind of amateur software development kit for creating PS3 games.  Sure, it is possible to create games for the PS3 running on Linux, however, there is no formal tool package to make the process easier.  Requiring an install of linux in order to play these also doesn’t do anything good for widespread distribution to the community. 

I don’t have a 360, so I haven’t tinkered with their system but based on what I have read, Microsoft seems to be doing a good job with their XNA community development project.  Everything from providing the tools, developing on a PC, MSDN reference, and the end-user distribution is fairly well thought out.  Of course, Microsoft has been giving out development tools for years now, whereas Sony has only been distributing professional tools directly to the game developers.  They have been touting how much easier the Playstation EDGE dev kit is for developers so perhaps a stripped down version of it would be the answer for the amateur side.  

These little amateur games fill a niche in the games industry but they haven’t really penetrated console systems.  How many hours are spent each day playing silly little Flash-based games.  It doesn’t take a three year cycle to create an interesting game people will spend hours playing.  All you need is a simple concept implemented in a way that is fun.  Bejeweled and Tower Defense are good examples.  PixelJunk even took the Tower Defense idea and twisted it enough in an attempt to get Japanese players to like it.

While we’re at it, I think I’ll mention that Microsoft is expanding their XNA in version 3.0 to allow development on their portable Zune system.  I don’t know about the technicalites of the PSP hardware and how software is run on it compared to the PS3, but I think that Sony should not forget the PSP when working on their dev kit.

There are more high-profile things that people might like Sony to work on, including Home and better in-game communication with our friends.  I agree, these things are important.  In fact, Home has arcade machines in some of the spaces, and I think that is an opportunity for people to create mini-games.

There are many aspiring game developers who could use this kit as a valuable experience for a future job.  There are also people who don’t want to submit themselves to the grind that is the professional development cycle and they can use it as a way to express themselves in a less-demanding manner.  There is no reason why Sony shouldn’t spend the resources to get a dev program going.  It really is the ultimate in user-generated content.
 

Giant Bomb.  Yea, That’s it.

Even with his termination from a large gaming website last November, it seemed pretty obvious that Jeff wasn’t done with the gaming industry.  He started a personal blog to post a few game reviews, talk about Tiger Gatorade, let us know when he’d be doing a tv, podcast or webshow, and of course, keep us primed for the announcement.  Giant Bomb is a new gaming website where people can go to get their dose of gaming related information.  This first stage of Giant Bomb is merely lighting the fuse to a greater grand opening explosion later on this summer.  As of now, it’s in a blog-style format while they finish designing and implementing the full site. 

There is another man behind the bombness, fellow former-large-gaming-websiter, Ryan Davis.  He’s been keeping his own personal blog, including a fairly-weekly podcast featuring Jeff and Alex Navarro.  The podcast will morph itself into a round ball with gunpowder inside sometime soon, featuring the same wacky conversation about games, drinks, movies and whatever else happens to be brought up.  They probably already have a title in mind, but here’s my recommendation: The Bombcast.  I don’t know if it’s in public-domain or not, but they need to secure that famous sample of some guy in a deep voice saying “The Bomb” over some of RyDeezy’s synthesized beats.

It looks like they’ll be using a new rating system for games, and I am sure it isn’t totally finalized.  The reviews of Burnout Paradise and Poker Smash have a five-star system to keep it simple.  There are a lot of different dimensions to score a game on, however an overall rating pounds and pummels all that down into a one dimensional meterstick.  You can never know what part of it either bumped the score or dragged it down, so there isn’t much of a point in using a stick with infinite tickmarks.  That only invites people to nit-pick over a scoring detail (8.8, anyone?).  A five-star system can help you decide which games were properly executed at a glance (or should be executed) and then the review will tell you why.  Depending on your own likes and dislikes, you can make your own decision.  The review is, afterall, just an opinion, and everyone puts different values on each of those different gaming dimensions. 

As Jeff said in his announcement, they’ve been listening to the feedback from their site visitors and podcast listeners and have been using that to help form the ideals of the final site.  It sounds really interesting and I can’t wait to see what they are going to do with the site to help video game players make their purchasing decisions while at the same time showing us an entertaining product.  So add it to your RSS list!

SimYard has an interesting twist to it.  Your team is made up of semi-pro players who you find while interacting with the fans around The Park.  You pick a field at the park and wait for someone to accept your challenge, or you find a field with another team waiting and accept theirs.  There is no set game schedule or requirement to play specific teams.  It’s more like pick-up baseball. 

Currently, your team has a roster limit of 40 players comprised of the usual positions.  Each player has a set of internal stats that make up what kind of player they are, ranging from 1 to 20 (I assume it’s 20.  The highest I’ve seen is a value of 17 on one of my pitchers).  The stats fall into one of three disiplines: batting, pitching and fielding/baserunning.  Batting, for instance, is made up of the Hit, Bat Speed and Power stats.   They go up against pitchers who use the Finesse, Pitch Speed and Endurance stats. 

Each individual matchup in the game is determined by the server using these stats, pitch by pitch.  You can see the current number of balls and strikes on the status display and the results of the matchup show up on a representation of the field.  You have as much control over the batter or pitcher as a real manager does in the dugout.  Sure, you can call substitutions, but like in the real game, you don’t have time to think it over too much before play continues on.  Each pitch takes about one second, and a full game can be completed in anywhere from 15 to 20 minutes.  The automatic manager does a pretty decent job replacing pitchers when they get tired and ineffective batters in the later innings, so don’t feel overwhelmed with figuring out who to pull and when.  The pitcher’s endurance stat determines how long they can go in the game and how much rest time they need in between starts.  Typically, it’s anywhere from 10 to 20 hours, which would equate to about four to six days in real life.   

The games go much like any game you watch on TV.  You root for your players like you would your favorite team, yelling at the screen when hitters can’t seem to do more than create a breeze and your pitchers appear to be throwing underhanded.  Of course, you do the same when your four-slot knocks a grand slam or your pitcher goes a complete game.

The baseball season is 24 days long, plus two days of spring training at the start of the month and two days of a post-season tournament at the end of the month.  Even though there are no official leagues in The Park, standings and stats are kept.  A simple games behind calculation determines where your team is in relation to the others.  Since everyone plays a different number of games in the schedule-less format, you can play half as many games as one team and still be next to them in the standings.  The date of the seasons is set in the late 1890’s, which some consider the beginning of modern baseball.  Everything from then to now is a blank slate… ready for you to make history.  Each new month bring a new season, new standings and new opportunity.

The top teams will play in the post-season, however not much about that has been revealed to the public yet.  I do know that you’ll set your starting rotation and closers to pair up against your opponents, and the computer will schedule the tournament with as many as 64 teams. 

All of that is free.  Starting next month, there will be a way to take your team to the next level, by purchasing a stadium license and joining a league with it’s own schedule, standings and playoffs.  Not only will you be playing against better teams, you’ll also have to keep the fanbase you built at The Park happy with good seats, concessions and souveniers.  They’ll show their happiness by attending games and spending money at the park so you can turn around and offer your players contracts and keep them on your team.   

The game is currently in beta, so you may notice some changes as the month goes on, as SimYard developer Erick Robertson tweaks things and adds features.  Erick sure did his homework when he came up with the engine behind the whole thing, so be sure to let him know you enjoy the game if you see him in the game’s chat or forums.  

So come on out and check out SimYard.  Anyone who is interested in baseball, especially those who take part in fantasy baseball should find enjoyment in taking a team of players and trying to beat the pants off of everyone at The Park.  You can find me in there as, who else? LoneStranger.