I am a Computer Science graduate from the University of Washington turned indie developer. My goal is to create a Module built adventure game piece by piece and document the process with the hopes to help someone in the future. I have been part of several game projects including Defense of Allende (Android), Ghostlight Manor (Steam), and GoArmy Edge Football (Android/IOS)
Here we go!

Subscribe to this blog

Follow by Email

Search This Blog

Posts

Following the previous post (here) The AstarPathfinding package is now wrapped up.I added the following features:

1) Get shortest path with Gameobjects2) Get shortest path with AstarNodes3) Return null if end point is unreachable4) AstarPathfinding is now static5) Added summaries to the methods for ease of use6) removed char[,] references.

1) Get shortest path with GameobjectsThe tiles on the game all have a component "AstarTileNode" and have the following members:

A* Pathfinding is kinda an essential to the gaming world, it lets you player move around, it helps AI both in NPC and Enemies, it can help validate paths, mazes, and dungeons, etc. so naturally Pathfinding is something that I had to implement.

Years ago in college I developed the algorithm for A* Pathfinding, however it was more of an theoretical exercise than a piece of code I could use, so with the help of YouTube.com and my old notes I put this together!

The code is simple, give the object a 2D char array, the start location, and the end location and it will spit you out a node with a recursive parent to take you to the end location.

Limitations:
Maps only work with (0,ymax) as the top left corner and (xmax,0) as the bottom right corner
ArgumentOutOfRangeException if the end point is unreachable
These limitations will be solved in the next iteration of the A* Pathfinding post

Way-points have always seemed to be an important part of gaming; traversing a unit through a path, patrolling an area, etc. Project and Source downloads are at the bottom of the post.

I started this post with what I thought was a well rounded and defined goal. As I moved forward with the code I thought "Hey, it would be cool to do this and add that". after going around and tripling my scope I decided to pair the features down to the basics: Moving to Random way-points and Traversing a way-point list in order. All other code was shelved for a part 2 and 3 (Reversing Direction, Shortest Paths)

I set forth with the idea to have unique customization events happen to each individual object traversing and with that in mind each unit contains the follow options:

I am a Computer Science graduate from the University of Washington turned indie developer. My goal is to create a Module built adventure game piece by piece and document the process with the hopes to help someone in the future. I have been part of several game projects including Defense of Allenda, Ghostlight Manor, and GoArmy Edge Football

Here we go!

Thank you for checking out my page, I intend to post every 1-2 weeks on a new part of my adventure game.

For now, here is a sneak peak at my first Adventure Game post (Waypoints)