"Cannot target this" function for Custom Cursors

[Bug Importer]

If you include a Custom Cursor function, could you include a way of defining which frame to use in case the current action is not valid for the object targeted? For example, if I have a mind control weapon with the brain from mouse.shp as cursor, I want it to show the "crossed brain" from mouse.shp when targeting ImmuneToPsionics=yes

[Bug Importer (bug-importer)]

Great idea

~ZeroMD

[Bug Importer (bug-importer)]

Millennium says:
There are a LOT of unused cursors in mouse.shp / mouse.sha (for example, a "RadDeploy" cursor and a move cursor for Teleportation). Wouldn't it be useful to have "MoveCursor=" and "DeployCursor=" as statements on units, so we could put these unused frames to use?

[Darkstorm (bynnar-starblade)]

I MoveCursor and DeployCursor would be useful, but I suggest something more like:

[ARANDOMUNIT]
TheNormalsettings=yes

;Cursor Settings
MoveCursor=
NotMoveCursor=
AttackCursor=
NotAttackCursor=
DeployCursor=
NotDeployCursor=
GuardCursor=
NotGuardCursor=

I'm not sure if there is a regular "unable to guard" cursor so that one is questionable but the others make sense.

[Professor_Tesla (professor-tesla)]

In my opinion, AttackCursor= should be defined per weapon, not per unit. The reason is that a unit could have a normal weapon for its Primary=, and a "special" weapon for its secondary, and it would be silly to have a "special" cursor for both. Also, it might be better if the "Not" cursor was defined for each cursor. The code could then be trimmed down to:

[UNIT]
Primary=Fudge
MoveCursor=ChronoCursor
DeployCursor=CustomDeployCursor
GuardCursor=CustomGuardCursor

[Fudge]
Cursor=CustomAttackCursor

[Renegade (renegade)]

Is this on our pseudo-mental "list of stuff to do"?
If so, somebody set this to "invalid" and update the blueprint.
If not, somebody set this to "won't fix" and the blueprint to "obsolete".

(Alternatively, the original requester can, of course, proactively start whipping the blueprint into shape.)