Yet another Group Project:Best Titanium Forge Game

[Gan]

Hah, that is pretty simple. I kind of like that story line. Though whatever we do, we have to think what tiles we will use and how we will obtain them. I believe Silver made water for swashbuckler the group project. His tiles look really good.


-Gandolf

[Silverwind]

Swashbuckler? I think we were just gonna use the plain blue tiles from QoM. I think those old tiles are crap compared to my new ones without the boundary box, but you're welcome to use whatever you can find of my old tile sets. I'd send you a complete up to date sprite sheet myself only... You know... They were all destroyed in The Great Hard Drive Fire of A Few Months Back.

Man I'd love to be game designing again...

[WarHampster]

Hah, that is pretty simple. I kind of like that story line. Though whatever we do, we have to think what tiles we will use and how we will obtain them.

All the game's assets (including tiles) should be made by us... it will make the finished product much more impressive.

[Xiphos]

I can make tiles!

[Gan]

You can see here how much of an artist I am:

So, which storyline idea shall we agree on?


-Gandolf

[WarHampster]

Lets use mine... it will require less assets and make things easier.

[Gan]

Sounds good to me, what does everyone else think?


-Gandolf

[Xiphos]

yeah sure!

[WarHampster]

Ok, I'll start work on the following:

Player sprites and animations for the main world

First person sprites (I'm thinking that I'll just make a first-person view of a hand, then we can make different magic blasts coming out of it)

A generic ninja

[Gan]

Ah sounds good to me. I'm hoping to have sprite collision code finished by today. Here's what I have so far: http://screencast.com/t/GyTOBJ6Hlx1


-Gandolf

[WarHampster]

Doesn't making a sprite's collision sensitive area a shape other than a square cause lag?

[Gan]

Yes if you plan on doing the pixel perfect method.
Pixel Perfect = Identifying each pixel and seeing if it collides with a pixel from another object. Extremely slow but very precise.
Square Collision = If two squares around sprites crash, it collides. Very fast, not precise. Circles and other more then 4 sided polygons are in trouble. Especially convex sprites.

So, I don't like either of them because I either have a slow game or a cruddy precision game. I decided to mix both methods. Now I have a slow and cruddy precision game. (Kidding)
Actually I have created the Polygon Perfect collision detection system. You create the polygon in the sprite editor and when in game it uses the Square Collision method. If two squares collide, it takes it a step further and looks to see if both polygons are intersecting.
With this method the game stays as smooth and fast as the Square Collision system but keeps as precise as the Pixel Perfect system.

Win-Win. Except if you have two sprites that are constantly colliding and can't stop colliding. That's when the CPU starts getting used up.


-Gandolf

[Gan]

Finished sprite collision, and I gotta say... It's looking pretty good:
http://screencast.com/t/2K5FIw02


-Gandolf

[WarHampster]

This is already dead.

NOT MY FAULT.

[Telstar5]

This is already dead.