Additional Unit Cursors

[Nighthawk]

Basically, this would be another improvement on the new mouse cursors logic, allowing modders to specify custom move, deploy and attack-move cursors (the latter may not be as necessary), as well as the weapon cursors.
Example tags would be:
[UNIT]
CursorMove=
CursorNoMove=
CursorAttackMove=
CursorNoAttackMove=
CursorDeploy=
CursorNoDeploy=
Update:
Also, something I forgot to add to the request, Enter cursors:
CursorEnter=
CursorNoEnter=
For something like capturing a building or vehicle, or entering a civilian structure or a transport vehicle.

 would be an entry in the [MouseCursors] section (if you're sticking with such a system). This would allow for use of the old Chrono Move cursors in the mouse.sha file.

Also, on the weapon cursors, would it be possible to have the cursor read for the Secondary weapon as well? Currently only the Primary is read, the Secondary is ignored, and the Primary cursor is displayed instead.

[Renegade (renegade)]

All illiterate here.

Fixed Severity. (And Reproducibility if necessary.)

[Nighthawk (nighthawk)]

Thanks.
Also, something I forgot to add to the request, Enter cursors:
CursorEnter=
CursorNoEnter=
For something like capturing a building or vehicle, or entering a civilian structure or a transport vehicle.

[Black Temple Gaurdian (black-temple-gaurdian)]

Deploy cursors aswell?

[Bug Importer (bug-importer)]

AttackMove / NoAttackMove - are these overrides to the weapon-specific ones, or do the weapon-specific ones override these?

/NCoder

[MRMIdAS (mrmidas)]

strong support for this, custom cursors are a worthy addition.

[Nighthawk (nighthawk)]

Hmm, my requested implementation was suggested back when I thought Ares would go with a similar system to what the RockPatch used for cursors ([MousePointers] section with defined cursors in there). But Ares now uses a different system for its super weapon cursors, which I'm guessing would be applied here if this were implemented.

For a start, instead of simply one tag for each cursor like in the original implementation, it would have a tag for each variable like the current super weapon cursor logic, e.g.
[BLAH]
CursorMove.Frame=
CursorMove.Count=
CursorMove.Interval=
... etc.

@NCoder - you're confusing AttackMove with weapon cursors. AttackMove is where you can order a unit to move to a destination but stop to attack targets on the way. It's accessible through a keyboard command in YR, and uses a different cursor to both the Move and Attack ones. Weapon cursors is a different request entirely.

Edit: Though I notice I mentioned something to do with weapon cursors, so I can see where you're getting mixed up. That was related to a bug in the old RockPatch system of weapon cursors where only the Primary weapon's cursor would be used. Again, I was being presumptive and assumed Ares would re-use the old [MousePointers] system. Ignore that last bit.

[DCoder DCoder (dcoder1337)]

To be fair, MousePointers are more compact than multiple flags to describe one cursor and we might look into a less verbose notation.

[Renegade (renegade)]

I'm setting this to invalid as I've converted it into a blueprint, which is the proper procedure for feature requests now. The blueprint is linked in the sidebar.

[mevitar (mevitar)]

17.139.1131, Cursor.Move=, Cursor.NoMove=, Cursor.Deploy=, Cursor.NoDeploy=, Cursor.Enter=, Cursor.NoEnter=, and also Cursor.Spy=, work properly for all appropriate types. No issues noticed with the defaults.

[AlexB (alexander-b)]

Thanks! Also confirmed https://ppmforums.com/viewtopic.php?p=556823 and onwards.