They call it "Legacy Targeting" but it doesn't seem to be the case. There are currently 2 targeting systems in 2D, of which I and many others use the "Legacy-Legacy" one. Not the TargetNext, TargetPrevious, and whatever. The true original system doesn't appear to exist at the moment.
I just want to clarify: Our intent is to emulate the "Legacy-Legacy" one with the Legacy Targeting option.
"Legacy-New" seems unnecessary to implement because the non-Legacy Targeting option in the enhanced client covers much of that ground already and adding in a third targeting system is overkill.
What we imported into Legacy Targeting are (text in parenthesis as macros in the Classic client):
- Cursor Target Last (LastTarget)
- Cursor Target Self (TargetSelf)
- Cycle Last Cursor Target (TargetNext)
- Attack Last Cursor Target (AttackLast)
What I consider grounds already covered for "Legacy-New" in the non-Legacy Targeting option of the enhanced client (text in parenthesis as macros in the Classic client):
- Target Next (SelectNext)
- Target Previous (SelectPrevious)
- Target Nearest (SelectNearest)
- Attack Current Target (AttackSelectedTarget)
- Use Targeted Object (UseSelectedTarget)
- Current Target (CursorTargetCurrent)
Our goal is to get Legacy Targeting in the enhanced client as close as possible to "Legacy-Legacy". If there are quirks that you are noticing, post as much detail as possible about it such as how it works in the classic client and what you end up seeing in the enhanced client.
There are already a few things on our list to fix. The TargetLast/TargetSelf issue mentioned in the beginning of this thread. The delays in a macro between activation of a spell/item and cursor targeting.
