No problem. Seeing that your using console graphics, I'm assuming you are going to want to detect collisions on the character level. If that's the way you go, once you get things working to your liking you could make it speedy and less memory hungry by creating bitmasks of the sprites and judicious use of bitwise &, and bit shifts.
Let's say you limit sprites to 32 x 32 (pretty big for ascii characters),
You could make a bit mask for the characters with something like so... (untested)
Then by comparing the appropriate rows, collision checking can be done with a bitwise & (After you've shifted the mask appropriately )
my $transparent_color = ' ';
my $chardata = [
' |x x|',
' | |',
' = ',
];
my $map = make_collision_map($chardata);
# This gives you a map like so
#00000000000000000000000000110110
#00000000000000000000000000100010
#00000000000000000000000000001000
# Assuming the character animations is an array ref of one or more hor
+izontal lines
sub make_collision_map {
my $sprite = shift;
my @mask;
foreach my $row (@$sprite){
warn "Sprite length exceeds limit:[$row]" and return if length($
+row) > 32;
(my $bits = $row)=~s/[^$transparent_char]/1/g;
$bits=~s/$transparent_char/0/g;
push @mask, unpack("N", pack("B32", substr("0" x 32 . reverse (
+$bits), -32))) ;
}
return [@mask];
}
I don't have time to finish this right now, but hope it helps.
-Lee
"To be civilized is to deny one's nature." | [reply]
[d/l] |
Thanks, I may be adding character level collision detection, but initially it will just use bounding boxes. When/if I do, it will certainly be using the technique you describe.
| [reply] |