It's a bit too early for screenshots. Still making engine. Need to make state machine (already did collision detection) and sprite animation routines, but that after sleep. Then I will test engine with some dummy graphics, after that... Mario Ripping Time!
//edit: Of course I'll post source code along with game - keep in mind tho that since it is my "training project" in Allegro.pas, probably most of it unless not written by myself, is The Daily WTF material.
Last edited by Darkhog; 29-05-2013 at 01:21 AM.
Great! Another Allegro.pas project. I'm sooooooo happy!
No signature provided yet.
Update: Currently figuring out world generator. I don't know how to make blocks appear on ground and not get buried (think way grass in Terraria is outside, but never inside of dirt). It is important, because I want to add some spikes here and there and those won't look good in mid-air or inside of ground.
Next on: State machine.
//edit: Also it is amazing, how much randomly plotted circles can do to generate cool cave.
Last edited by Darkhog; 29-05-2013 at 12:04 PM.
Project update: Started to move world generator stuff into it's own class and unit. I think I'll leave state machine for end.
Next on: Figuring out how to make collision with map (probably I'll use my custom TSprite class for that).
I've figured out way to make sprite collisions. As I suspected, I'll use my TSprite class for that. Will need two sprites per chunk (one for blocks that just stop player and one for blocks that hurts him, like spikes) plus array of sprites for shootable blocks (will need to check for collision between bullet and any of those so I can remove them).
I've almost finished world generator. After I'll finish it completely I'll get to tileset stuff (such as rendering chunks to sprite objects and getting tile with specific ID from tileset).
Why needing two sprites per chunk. Wouldn't it be better to just include additional information to a single sprite which would tell you what type it is.Originally Posted by Darkhog
At some point your would probably decide to include some AI controlled units. So would you use even more spites to determine their behaviro?
I belive it would be better to just derive the base sprite clss and add aditional information to it like is pasable, can be destroyed, its health, how much damage does it do. Combination of theese can be for instance even used for defining wall which would deal damage to the player oif it bumps into (spiked walls).
Problem is that when checking for collision with one sprite (it's pixel-perfect by the way) I can't tell if part of sprite player is colliding with is spike or harmless object, hence two sprites per chunk - one for harmful things and other for harmless. Supposedly I could do like you are saying, but I'm too much of a n00b yet and I'm basically learning Allegro with this project so...
Also you are talking to guy who barely made world generation and pixel-perfect collision and only because I was given perlin noise unit and was able to (barely) translate pixel-perfect collision code for original Allegro (in C).
Posting Permissions
Reply With Quote
Bookmarks