@Ned: I'm not exactly looking for a better way of doing the hit-test, I think I have it down but it would be great to see someone else say so.
_root.range_list is an array of objects to hit test.
_root.monster_list is second array of objects to hit test.
The hit test itself is very easy, the object is a circle so I test if the "diameter" of the object to be hit tested is smaller then the diameter of the circle being hit tested. If it's smaller then it's within the circle, if it's bigger it's not.
in a nutshell -
if(it's able to hit test)
{ while(do hit test)
{
if(hit test)
{
if(ready to shoot)
{ - shoot - }
- end hit test -
}
}}
_root.range_list[x].onEnterFrame = function() {
if (!_root.tower_list[this.tower].placing) {
monster_counter = 0;
this.shoot_counter++;
while (monster_counter < _root.monster_list.length) {
hitDif_x = this._x - _root.monster_list[monster_counter]._x;
hitDif_y = this._y - _root.monster_list[monster_counter]._y;
if ((hitDif_x * hitDif_x) + (hitDif_y * hitDif_y) < (this._width + 15) * (this._width + 15) / 4) {
if (this.shoot_counter > 10) {
_root.placeBullet(monster_counter,this);
this.shoot_counter = 0;
}
monster_counter = _root.monster_list.length;
}
monster_counter++;
}
}
-----------------------------------------------
@Rothhrock: I was thinking of doing something like that, the quadtree, but wasn't coming up with anything that would be less work then just doing the hit test on everything. Breaking the larger sections down...that could work.
(added)
Rothhrock, how would a quadtree work? I am thinking having multiple monster arrays, moving the monsters between the arrays as it moves between game sections and then testing the arrays those objects are in, but I'm not sure if the management would be any less work.
