Document Actor "Fidget Tables"

[Feacur]

rename func_80034F54 -> MM's naming UpdateLimbOverrides, because:

• 0x814 and 0x940 constants
• *_OverrideLimbDraw functions association
• respectively Actor_UpdateFidgetTables and .fidgetTable
• introduce constants for "fidgeting" formulas (no variation throughout OoT and MM)

consequent changes:

• move the constants into z64animation.h
• use these constant for existing formulas
• properly name corresponding actors' fields
• add occasional explicit limbs limit constants
• fix z_en_go.h fields naming (was as for skeletal animation)

P.S., as a side note: `*_OverrideLimbDraw` and `*_PostLimbDraw` functions look more like `*_PreProcessLimb` and `*_PostProcessLimb` to me so, is there a strong or any reason why they should be named as they are now?

my question comes from the following observations:

• these functions does not draw anything
• the latter can update colliders as a "post processing" step
• synchronize transforms or other parameters
• generally do anything for game logic

obviously, the change by itself would be meaningless, leave alone huge. it's just curiosity

[fig02]

You should check out the Actor_UpdateFidgetTables documentation in Majoras Mask. Instead of a generic "update overrides", its a very specific type of override. It manually rotates certain bones in an actors model to give it an idle animation, where it looks like they are breathing or otherwise idling.

I dont personally agree with the naming direction MM went by calling it "fidgeting", and is why I personally have not ported these docs over to OoT. But do not think we should go in the direction of calling it generic "overrides" either.

[fig02]

Regarding override limb draw: It has its name because of the return value. It gives you the ability to override the display list for a given limb if the return value is true. But yes it is true that it runs before a given limb is drawn.

[fig02]

In addition to the discord conversation about using MM's names, here are some other things