Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EnHy + objects docs #1499

Open
wants to merge 21 commits into
base: main
Choose a base branch
from
Open

EnHy + objects docs #1499

wants to merge 21 commits into from

Conversation

hensldm
Copy link
Contributor

@hensldm hensldm commented Feb 18, 2023

Documents EnHy as well as the different objects surrounding it (except os_anime which is large and tbh I didn't feel like documenting all the animtions). Regarding the objects I decided to go with the naming style gHylian + attributes, where attributes describe the npc (old/young, man/woman, details describing their head, etc.) . Any suggestions are welcome of course.

Comment on lines 77 to 78
/* 0x021C */ s16 fidgetTableY[16]; // bodyWiggleY ?
/* 0x023C */ s16 fidgetTableZ[16]; // bodyWiggleZ ?
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Im not 100% sure about calling this a "fidget table" in general. I am aware that mm just recently moved to this terminology, but I wasnt around at the time to take part in the conversation.

Guess its ok for now, but will prob want to discuss it on a broader scale at some point in the future.
Can prob remove the the comments on them too

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm always down to discuss names, so if we do have other suggestions please just let me know. Removed the comments at least.

Comment on lines 1441 to 1443
// ENHY_TYPE_DOG_LADY
// ENHY_TYPE_WOMAN_3
case ENHY_TYPE_MAN_1_BEARD:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are some of these types commented in the switch? If their case isn't here, then the code below wouldn't run?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah the code doesn't run for those cases. The comments were just there from the original decomp I think. I should probably just remove them.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I put those comments in, to highlight which types are not there (they are placed in the enum's order)
but yeah feel free to remove 🤷

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see, could always put the comments in the default case?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure why not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants