Our game is gonna be, like, so cool!

HIDE THE MONEY Y'ALL, THERE'S POOR PEOPLE AROUND

2005-05-02T21:33:00.000-04:00

Our presentation today went rather well! We hope that everyone who saw it now understands our intentions behind creating Mastrix, as well just how leet we are.

Level design is also going along smoothly; we planned out 16 missions, and we have finished 12. We should be in pretty good shape for the showcase.

FYI

2005-04-28T22:02:00.000-04:00

The reason why powerups can float around in Mastrix is because it's another galaxy. That just makes sense.

making it happen

2005-04-21T18:09:00.000-04:00

Our game is getting loaded. We've got turrets, bosses, multi-screen levels, mouselook, weapons, etc. etc. etc. etc.

We are completely on track with our milestone doc.

spring is here...

2005-04-10T15:33:00.000-04:00

Updates to the Mastrix website... it looks quite different, and I'm finally happy with it. The format and style is more appealing to the eye and the media page has nice, attractive thumbnails.

We had our alpha presentation on monday, and the website finally has screenshots from the alpha version. Basically, our AI works, our physics is nice and we have a complete single player level written entirely in the scripting language of Mastrix (meaning we can make lots and lots of single player levels with the level editor, which if we didn't have, would be next to impossible). We have a great title screen plus working radar. So charging ahead towards our beta release, we are focusing on having a variety of weapons and more levels, as well as a more structured multiplayer mode.

keeping you updated

2005-03-31T01:34:00.000-05:00

trusted news from a trusted source.

- our website has had some updates, if you haven't seen, it's version, like, 0.5 now.
http://mastrix.jimrandomh.org

- our performance issues have been fixed, for now at least

- we are focusing on getting good art and designing fun levels with various kinds of enemies other than just fighters. we might need to outsource art, who knows? we are relying on GPL for some things as of now.

- making enemies fly around the screen is still an issue, but we'll have it down soon.

another presentation is coming up... april 8. it's.... so..... exciting!

back from Spring Break

2005-03-28T13:47:00.000-05:00

Ok, so we are back from Spring Break and hard at work on our game. Our priorities now are:

- Performance, so the game is actually playable even with 8 or more people at a time.
- Single player levels that are fun and original.
- Good sound effects.
- AI that doesn't kill itself.

The website didn't get any work last week but the only thing really missing is the instruction manual, which shouldn't take long at all.

Codemonkey session, March 13

2005-03-13T17:23:00.000-05:00

On our way to our second prototype... we've gotten a lot done.

- We have our website! Here's the link: Mastrix!

- Our game has lots of updates. We have a scoreboard, names for players, and messages that say who killed who. Our networking has gotten more reliable and now we have level editing (for the single player mode).

- We finished the functional specifications document. A link should be up on the website by now.

- Our first song is complete. Expect an album deal soon.

Update

2005-03-12T00:36:00.000-05:00

Making some preparations for the second prototype.

There's been some hee-haw and whining about how we don't have a designer diary or whatever, so I guess I'll mention some design decisions now.

-On a somewhat technical note, I think I'm going to modify the bot obstacle avoidance algorithm *again*. Potential functions are too rigid, and explicitly doing vector calculations and trig is tricky, given our fancy physics system. I'm thinking of using dual ray tracing along the nearest obstacle to find a clear path, and just set a temporary goal to a position along that path.

-Mastrix's gameplay is really starting to take shape. We implemented mouse control, a faster turning speed, and strafing. This allows for a much faster paced gameplay, and it in fact feels like you're playing a first-person shooter like Quake, except in a 2D space shooter environment.
This is exactly what we are trying to achieve - a simple, fast-paced action game that is competitive and addictive.

-Networking code is functional. You can start a listen server and others can connect to your computer. Oh golly gee!

-We have a message text area for chatting (not yet implemented) and notifications.

-Just for the record, Jim's not the only one in our group who favors porting the game code from GameX to SDL. The biggest reason I can think of right now is for performance; we use lots of nice looking particle effects for explosions and engine thrusting to make up for a lack of a dedicated artist, and GameX's point drawing function is unsuitable for this. (It draws points as quads!) Hopefully I will get around to porting the code soon, but first I should probably finish up the bot AI.

-A scoreboard would be nice.

-Oh and we're probably going to migrate this blog somewhere.

-Yi

//And here's a copy of my bot AI design log/whatever
AI Overview
---------

Idea: Bot AI will be based on a FSM.

Reason: Potential functions are not too flexible, and they don't allow for
deterministic behavior modification. The FSM itself is nothing more than an
enumeration of some constants; we'd end up building an AI just the same without
it, but the enumerations make bookkeeping easier.

Execution
---------

-Since this is a FSM, let's enumerate some states:
enum ai_state
{
state_roaming,
state_chasing,
state_evading,
state_defending //protect a position, stay within a certain radius of it
}

-Aside from giving each bot a state that describes its current behavior, we
should also assign each bot some attribute values to describe its inclined
behavior.

float aggressiveness;
float defensiveness;
int skill;
float hitpoints; //we probably have something like this already

-Associated with these attributes could be another enumeration of bot roles.

enum ai_role
{
role_chaser,
role_interceptor, //tries to intercept you along your trajectory
role_defender
}

-The overall AI algorithm! Each bot will have an ai_role, and will have
different corresponding behavior patterns.

*For chasers:

1) Spawn
2) Look for a target;
if you can't find one, roam, repeat (2)
if you found one, chase it
3) While chasing:
if target is no good, (dead, waaay too far away) goto (2)
elif target is alive, turn towards it and shoot
elif target is alive but too strong, run away!

*Ok now for some pseudocode...

Add a bot, set initial state to roaming

timepass() //loop
{
if state_roaming
{
FindBestTarget()
if still no target,
roam()
else
set state_chasing
}
if state_chasing
{
if (target no good)
set state_roaming
elif (target alive and not too strong)
chase(target)
else //too strong
set state_evading
}
if state_evading
{
if (target, who is actually chasing the bot now, died or is too far)
set state_roaming
if (target is weaker than the bot now)
set state_chasing
}
}

*Now we have to consider how the bot will avoid obstacles. From what I've
tried, potential functions are too strict, and explicitly doing vector math
and trig to figure out which way to turn is quite hard considering our physics
system.

On a side note, a mistake I think I was making with the algorithm was that I
did not modify the bot's roam goal. I would iterate through the obstacles and
tell it to turn left or right, but that's just an instant command; it does not
affect the bot's overall intention, which should be to go to a place that is
not blocked by an obstacle!

So, I think we should try use dual ray tracing to figure out a clear path.
If the bot thinks that it is on a collision course with an obstacle, it will
create two rays starting at the vector representing the collision course, and
span away from it by a certain amount. This gets repeated until the bot finds
a clear path. If he can't find a clear path, then I suppose he can just go in
some random direction. (Although this should not happen.)

A ray represents a "clear path" if the length along it up to the bot's
visbility is unobstructed. Perhaps we can simplify this if we figure out which
obstacle is the closest to the bot, or test a few places along the ray.

By now we should have a clear path. We then pick a position along the length
of the ray; that length should be inversely proportional to the distance
between the bot and the obstacle. Therefore, if the bot is very close to a
planet, it will trace rays until it finds a suitable path. Since it is very
close, it should probably strive to go farther away. If it chooses to stop
close to the planet, then it's vulnerable to gravity.

If the bot is barely touching the planet, then his rays will have to trace out
to 90 degrees in both directions. (To its left and right, assuming that it's
facing the center of the planet.) Since it is so close, it will want to move
far along one of those two rays.

Codemonkey session, March 6

2005-03-06T17:02:00.000-05:00

Fixed the edge handling, it behaves pretty well now. Working on the chat box, particle effects, AI, networking, so on and so forth. Latest milestone doc:

Milestone 1 Due: March 2 - Completed

Playable multiplayer in split-screen
Camera control
Scrolling star field
Send commands from server
Handle collisions and take damage
Sound effects
Complete scripting system

Milestone 2 Due: March 16

Level editing mode
Single player objectives and level sequence
Computer controlled AI opponents
Networked multiplayer
Background music
Functional specifications document

Milestone 3 Due: April 6

Various unique weapons
Human ships and weapon designs
Alien ships and weapon designs
Good performance for CSUG Lab
Graphical effects
Ship explosions - Completed
Radar
Title screen
Website

Milestone 4 Due: April 20

Ship and weapon selection
Challenging, unique levels
Multiplayer game modes and levels
Gravity - Completed
Complete soundtrack
Game Script

Milestone 5 Due: May 4

Balanced
Debugged

Codemonkey session, March 4

2005-03-04T18:06:00.000-05:00

The first prototype presentation took place today. It went extremely well. We presented a playable demo with multiplayer on the same computer. We've got graphics, sound, and interactivity... who needs expensive games with us on the job?

Codemonkey session... lots of new changes... the health bar is now a health circle that turns from green to red (very cool). We have great particle effects... ships blow up and debris flies EVERYWHERE!

We decided to make the center of an entity at the true center, rather than at the top left. So the center of your ship really is the center, so then it's really easy to place a ship on the screen depending on the center of the ship. It's a small detail that makes a big difference.

Codemonkey session, February 20

2005-02-20T23:18:00.000-05:00

Another codemonkey session in the CSUG lab. We've encountered some problems with our game running very slow. Aside from the fact that the CSUG computers run like frozen molasses, we are still trying to pinpoint the problem. It may have to do with drawing too many objects on screen at once... this is definitely not good.

We've made progress here and there with edge handling, console commands, and camera following, but we definitely have to deal with the speed of the game before we can make any big steps.

Concept Doc Draft 2

2005-02-16T12:14:00.000-05:00

Now with more excitement...

MASTRIX
Concept Document

Premise: Bringing momentum to new worlds.

Genre: Space Shooter

Audience

Anyone who can learn the mechanics of Mastrix would enjoy it. The plot may be too mature for young children, but the game is simple enough for anyone. The single player mode will provide enough challenge for skilled players without being impossible. The multiplayer mode will be easy to learn and well balanced for players of all skill levels.

Story

After Space Ship One claimed the Ansari X-Prize, private corporations quickly claimed the realm of space travel. There were huge profits to be made in space mining, and with the formation of the Universal Trade Organization (UTO), companies pooled their efforts and reached farther into space than we had ever imagined.

This would have been a golden age of scientific exploration, but as the UTO expanded, the entire world faced a new problem. Material greed brough about fatal consequences. The world's supply of oil was gone. No one even saw it coming. Other resources were also dangerously low. People everywhere were frantic. Huge gas guzzling SUVs, now useless, filled the streets all over the world, as their owners abandoned them and pondered their new lifestyles. "Should I walk to the grocery store? Do I really need groceries? Maybe I'll take the bus. Wait a second, THE BUS USES GAS! AAAAH!" Pandemonium followed. The UTO convened immediately to address this dire emergency.

Many ideas were proposed to solve the Earth's problem. Radical ideas like alternative energy sources and synthetic fuels were rejected outright. The world needed a practical solution, not fantasy. The world needed genius, and that came from the head of the UTO Defense Force, a division of the UTO dedicated to protecting the interests of the UTO in space. The plan was simple; the UTO would supply the Earth's massive demand for resources bye exploiting the abundant Mastrix solar system. If anyone got in the way, the solution was obvious. Destroy them.

All the UTO needed was an ace pilot crazy enough to answer the call. That's where you come in. The danger, the distance, or the ethics, you might have considered. If you didn't have bills to pay. Bottom line is, the UTO is paying you enough for this job to put you in permanent retirement. If you survive. Mastrix awaits.

Core Gameplay

Physics
The player's ship can turn with constant speed, and accelerate forwards or backwards, as in Asteroids, Spacewar and derivatives thereof. Some locations will have gravity which pulls the player's ship (possibly into a crash). For advanced players, in multiplayer and on later levels, other ship physics are possible, such as movement with rotational inertia.

Objectives
In single player mode, the player will be given a number of objectives in an open area, and the level will end when they are all complete. The main focus, however, is the many destructible enemy ships in the way. Objectives include destroying targets, planting your flag on planets, and stealing valuable objects.
In multiplayer, there will be different modes, the most basic being the traditional deathmatch: kill every other player, repeatedly. This could be done either with traditional weapons, or in a special mode where players push asteroids into their opponents (as in Half-Life 2's gravity gun). Capture the flag would also be available, and other modes are possible if time permits.

Interesting and Unique Game Elements

Single player mode will focus on fetch and destroy strategy while avoiding obstacles and dealing with various elements in space.
Obstacles could be planets with their own gravitational field or black holes that must be avoided at all costs.
Levels will require strategy as well as quick reflexes to complete.
The player can choose from various ships with unique capabilities.
Multiplayer offers unique competition modes unusual to space shooters: death match and capture the flag.

So far...

2005-02-15T00:34:00.000-05:00

Concept Doc

Premise:

Mastrix is a game that will be fast, fun, and full of variety.

Audience:

Anyone who can learn the mechanics of Mastrix would enjoy it. The plot may be too mature for young children, but the game is simple enough for anyone. The single player mode will provide enough challenge for skilled players without being impossible. The multiplayer mode will be easy to learn and well balanced for players of all skill levels.

Genre:

This game fits the space shooter genre.

Story:

After Space Ship One claimed the Ansari X-Prize, private corporations quickly claimed the realm of space travel. There were huge profits to be made in space mining, and with the formation of the Universal Trade Organization (UTO), companies pooled their efforts and reached farther into space than we had ever imagined.

This would have been a golden age in scientific exploration, but as the UTO expanded, the entire world faced a new problem. Material greed brough about fatal consequences. The world's supply of oil was gone. No one even saw it coming. Other resources were also dangerously low. People everywhere were frantic. Huge gas guzzling SUV's, now useless, filled the streets all over the world, as their owners abandoned them and pondered their new lifestyles. "Should I walk to the grocery store? Do I really need groceries? Maybe I'll take the bus. Wait a second, THE BUS USES GAS! AAAAH!" Pandemonium followed. The UTO convened immediately to address this dire emergency.

Many ideas were proposed to solve the Earth's problem. Radical ideas like alternative energy sources and synthetic fuels were rejected outright. The world needed a practical solution, not fantasy. The world needed genius, and that came from the head of the UTO Defense Force, a division of the UTO dedicated to protecting the interests of the UTO in space. The plan was simple; the UTO would supply the Earth's massive demand for resources bye exploiting the abundant Mastrix solar system. If anyone got in the way, the solution was obvious. Destroy them.

All the UTO needed was an ace pilot crazy enough to answer the call. That's where you come in. The danger, the distance, or the ethics, you might have considered. If you didn't have bills to pay. Bottom line is, the UTO is paying you enough for this job to put you in permanent retirement. If you survive. Mastrix awaits.

Core Gameplay:

The goals of the single player mode are to destroy the opposition and collect resources for Earth. Gameplay is managed with the keyboard. Players can maneuver their ship and fire weapons. They can pick up powerups that give them various weapon options. In multiplayer there will be various modes. Death match will require players to destroy each other as much as possible. One variation will involve weapons from the game while the other will require the players to use repulsors to push debris into their enemies. The player with the most points is the winner. Capture the Flag will divide the players into two camps. The players must steal the opponent's flag from the opposite camp and return it to their own camp. Each time they do this they will receive a point. The team with the most points is the winner.

Interesting and Unique Game Elements:

Single player mode will focus on fetch and destroy strategy while avoiding obstacles and dealing with various elements in space.
Obstacles could be planets with their own gravitational field or black holes that must be avoided at all costs.
Levels will require strategy as well as quick reflexes to complete.
The player can choose from various ships with unique capabilities.
Multiplayer offers unique competition modes unusual to space shooters: death match and capture the flag.

Group Charter

2005-02-14T18:50:00.000-05:00

Group Name: The group formerly known as group G

Mastrix is a space shooter with asteroids style controls. The single player mode requires the player to collect materials necessary for the Earth's survival while destroying anything that gets in the way. The player can collect various power ups while using different ships with unique abilities. The multiplayer mode gives people the chance to compete against each other in death match and capture the flag. The main aim of our game is to be fast, simple, and extremely fun to play.

Group Leader: name withheld for internet safety – Programmer

Group Members:

name withheld for internet safety – Programmer

name withheld for internet safety – Programmer, Writer

name withheld for internet safety – Programmer, Musician

name withheld for internet safety – Programmer

After our first weekend...

2005-02-13T23:10:00.000-05:00

We've got tons of code done so far. To give you a qualitative description, we have a fully functional player ship that flies around. It rebounds at the edges of the screen. We have randomly generated stars in the background, shots that fire right out of the ship, and a really cool console that allows us to debug the program.

We've had two monkey coding sessions this weekend where we have coded like codemonkeys. Our current base of operations is the CSUG Lab in Upson. All our work is done using Visual Studio .NET and we use CVS to manage our collaborative work.

All the game companies should be worried. Our game is gonna be, like, so cool!

Update

2005-02-11T18:45:00.000-05:00

Set up keyboard event queuing.

Console is functional with a few basic commands. (addent, quit, etc.)

Client can load and draw images.

We're syndicated!

2005-02-10T00:01:00.000-05:00

I finally set this up. Now we can keep our "game diary."

Come to think of it, I don't like diaries. This is our game JOURNAL.