11-26-2008, 02:35 AM
Hello, respected sprite rippers! I have a question regarding your policy toward assembling sprite tiles.
I'm an intermediate user of Game Maker, and in this program, you are able to define the 'collision detection' zone that a whole sprite has. In other words, you can determine the exact size of its hitbox. For example:
![[Image: shanoaexamplefo3.gif]](/image.php?src=http%3A%2F%2Fimg224.imageshack.us%2Fimg224%2F6514%2Fshanoaexamplefo3.gif&hash=678d3302d5b729548a43272df1813388)
You can decide whether the collison zone is composed of the entire sprite, just the opaque pixels, or just a small region.
In my experience with Game Maker, it is much better to work with whole sprites than to spawn fragments at the right times. Sure - it does come in handy for a few rare occasions, but it's a hassle for common simple things like simple animations.
A lot of the sprite sheets I'm seeing here aren't very useful for actual game implementation because the standard method among amateur game designers is to use whole sprites; using fragments and tiles is exceedingly difficult and impractical, except in rare cases, such as enemy limbs that rotate.
But all of that aside, I have a question to ask.
Who here would be willing to convert the Shanoa sprite sheet to an assembled sprite sheet? How much time and labor would it take? I imagine it would be meticulous - but it would be very useful for anyone planning on making practical use of Shanoa's sprites (myself included). If there is anyone here up to the task, I would appreciate it immensely.
(10-22-2008, 04:05 PM)SmithyGCN Wrote: The tiles can be left as is found in the data files. There's no need to assemble unless for an example. This is because this is mainly for those who would make fan games. If we left the sprites whole, then it'd put a strain on their programming system to incorporate complex collision detection parameters.
If anyone DOES want to assemble any tiles previously ripped, feel free to, but only if the tiles sheet is up as well.
I'm an intermediate user of Game Maker, and in this program, you are able to define the 'collision detection' zone that a whole sprite has. In other words, you can determine the exact size of its hitbox. For example:
You can decide whether the collison zone is composed of the entire sprite, just the opaque pixels, or just a small region.
In my experience with Game Maker, it is much better to work with whole sprites than to spawn fragments at the right times. Sure - it does come in handy for a few rare occasions, but it's a hassle for common simple things like simple animations.
A lot of the sprite sheets I'm seeing here aren't very useful for actual game implementation because the standard method among amateur game designers is to use whole sprites; using fragments and tiles is exceedingly difficult and impractical, except in rare cases, such as enemy limbs that rotate.
But all of that aside, I have a question to ask.
Who here would be willing to convert the Shanoa sprite sheet to an assembled sprite sheet? How much time and labor would it take? I imagine it would be meticulous - but it would be very useful for anyone planning on making practical use of Shanoa's sprites (myself included). If there is anyone here up to the task, I would appreciate it immensely.