here is the gif of the death sequence.
i'll have to make this into a png tomorrow.
~Scott
Thursday, May 21, 2009
Tuesday, May 19, 2009
Thursday, May 14, 2009
1, 8 and 16 Bit Era Layout's
these are the mock ups of whats been done by the art team.
the rest of the 16 bit level will be made asap and uploaded.
the actual monster and bit layout will be indicated on the collision maps that are given to the programmers.
~Scott
(1-Bit)
(8-bit)
(16-bit)
the rest of the 16 bit level will be made asap and uploaded.
the actual monster and bit layout will be indicated on the collision maps that are given to the programmers.
~Scott
(1-Bit)
(8-bit)
(16-bit)
Wednesday, April 15, 2009
Map Builder v2
Fixed the scale vertically. Scott, with the backgrounds that we currently have there's very little detail down around the bottom, so we should probably try to change that so that the screen isn't just filled with a solid color and there's something interesting there to look that.
I'm going to start creating tiles for 1 bit and 8 bit that are 64x64 pixels and act as tileable landscape. I know you've got some big ground tiles but I'm not sure they'll work, I'm thinking we'll have to go with a repeating tile that can be used for all major landscape. I'd suggest sticking to one 64x64px tile throughout all of the 16 Bit phase and then use a 32x32px tile to make bridges and platforms.
So basically you need one 64x64px "landscape" tile, and one 32x32px "platform" tile (no end caps, unfortunately - I'm thinking of time consumption and how long it's going to take the programmers to lay all this out inside of Python, even with our help).
EDIT: Thinking more about this and the tile engine that we have in place, I am not sure that the 32x32px tiles will work. It might be safer to make a second set of 64x64px tiles to act as platform tiles.
Reinventing Yourself
Funny that you did that little poster, Scott. I've been working on something myself... dramatically different though.
The writing under the silhouettes of the sprites is Latin because I was suggesting evolution, hence the "Charles Darwin" signature in the corner. The Latin simply translates to "Bit Square", "Bit Knight" and "Bit Fat Man".
I'm still laughing at my own joke.
The writing under the silhouettes of the sprites is Latin because I was suggesting evolution, hence the "Charles Darwin" signature in the corner. The Latin simply translates to "Bit Square", "Bit Knight" and "Bit Fat Man".
I'm still laughing at my own joke.
Monday, April 13, 2009
Friday, April 10, 2009
Map Builder
I posted measurements as to the sort of space we'll need for gameplay, and have been working on sizing down the scale so that we can accurately create maps for the Programmers to use and implement into the game engine. I've finally got it together now.
This is only an example image, the full-quality PNG is here.
Now mind you, even if the speed does change in our final build, this should be much more than enough for the levels to work functionally. Given the speeds I recorded, every two lines should be one level of the game. The way I'm expecting it should work is simply loading in new textures every 100 seconds over the map, so there's no major issues with us building out every level of the game altogether rather than separating the levels into specifically 1 bit, 8 bit and 16 bit maps.
What I'd like to do is assign specific roles later on to do two lines of this document each, to get split up and swapped around in the end document so a fair bit of ideas are separated and it doesn't work out to be "this level was made entirely by so-and-so", so there's no major distinctive differences in each part. We can work that out once we get back to class, but for now, feel free to play around with it and save anything you do so that we can possibly use it later.
The little blue box in the top left was just to see how much exactly will be on screen when the game first starts, but it's incorrect. The actual height of the screen vertically would only be 7 of the 64x64 blocks. I got my math wrong (most likely because it's 2AM, heh). This means that the vies will never "ascend" despite my intention in making the map, I can edit it at a latter date as it was my intention, rather, to have the map be twice the height vertically of the actual screen resolution. You can play around with that yourselves if you're so inclined, I'll try to get an appended map up in the coming days.
This is only an example image, the full-quality PNG is here.
Now mind you, even if the speed does change in our final build, this should be much more than enough for the levels to work functionally. Given the speeds I recorded, every two lines should be one level of the game. The way I'm expecting it should work is simply loading in new textures every 100 seconds over the map, so there's no major issues with us building out every level of the game altogether rather than separating the levels into specifically 1 bit, 8 bit and 16 bit maps.
What I'd like to do is assign specific roles later on to do two lines of this document each, to get split up and swapped around in the end document so a fair bit of ideas are separated and it doesn't work out to be "this level was made entirely by so-and-so", so there's no major distinctive differences in each part. We can work that out once we get back to class, but for now, feel free to play around with it and save anything you do so that we can possibly use it later.
The little blue box in the top left was just to see how much exactly will be on screen when the game first starts, but it's incorrect. The actual height of the screen vertically would only be 7 of the 64x64 blocks. I got my math wrong (most likely because it's 2AM, heh). This means that the vies will never "ascend" despite my intention in making the map, I can edit it at a latter date as it was my intention, rather, to have the map be twice the height vertically of the actual screen resolution. You can play around with that yourselves if you're so inclined, I'll try to get an appended map up in the coming days.
Subscribe to:
Posts (Atom)