Opened 14 years ago

Closed 14 years ago

#209 closed bug (fixed)

Missile range targetting problems

Reported by: tehtmi Owned by: tehtmi
Priority: minor Milestone: 0.9.9.4
Component: engine Version: 0.9.9.3
Keywords: Cc:
Blocked By: Blocking:

Description

There are two issues with the missile "range" property.

Currently, this property is only used by rocketjump (and possibly by modders). It was previously used (in beta) by the combat knife altfire.

1) Targeting is restricted to a radius of range - 1 even though the missile is allowed to travel range away. This makes it hard/impossible to target some cells within the range.

2) Using 'f'ire with such a missile can auto-target enemies that are outside the range. If this happens, the targeting cursor cannot be moved at all (if the enemy is far enough out of range).

CForum:4350

Change History (3)

comment:1 Changed 14 years ago by tehtmi

Currently, range actually seems to be square based. I think it should be radius based instead. Also, perhaps missiles should also be limited by range instead of just targeting?

comment:2 Changed 14 years ago by tehtmi

  • Owner changed from epyon to tehtmi
  • Status changed from new to assigned

I'm going to leave it square-based for now since that would affect all missiles.

comment:3 Changed 14 years ago by tehtmi

  • Resolution set to fixed
  • Status changed from assigned to closed

(In [1569]) * Missiles' internal ranges now match observed targeting ranges.

  • Weapons can no longer autotarget enemies that are out of range. (Fixes #209)
  • Combat knife altfire now uses restricted targeting.
  • Rocketjump range reduced to one to more closely match the old behavior.
Note: See TracTickets for help on using tickets.