Skip to content

Conversation

@Pepe20129
Copy link
Contributor

@Pepe20129 Pepe20129 commented Dec 22, 2023

Copy link
Contributor

@leggettc18 leggettc18 left a comment

Choose a reason for hiding this comment

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

This is looking great, but I have one comment in the code and two things I'd like to see before this gets merged.

  1. I'd like to see if we can get these in as possible Ice Trap models. I forget exactly where right this minute, but I think it's in item_pool.cpp, there's a place where a vector gets filled with RGs, and I think if we add the Ocarina Button RGs in there it should just work.
  2. Even if it's just placeholder text, I'd like to see something in the item tracker. I won't require it for this to get merged because I'm not familiar enough with that code to know how easy it is to add these buttons to, but I would like for that to be looked into.

If we can get those addressed then I'll say LGTM!

@Pepe20129
Copy link
Contributor Author

I've made all the requested changes. The only thing that's left now is trick names.

Copy link
Contributor

@leggettc18 leggettc18 left a comment

Choose a reason for hiding this comment

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

Have you tested the ice trap models to make sure they actually render correctly? Adding them to the list should be all that's needed for that, just curious if that's actually been verified. If not I'll gen a few seeds and check. Assuming they render correctly, LGTM!

@leggettc18
Copy link
Contributor

leggettc18 commented Dec 26, 2023

I went ahead and tested it. Unfortunately the model rendered as the Stone of Agony rather than the Ocarina button. You can probably fix it by using the drawItemId from the GetItemEntry in DrawOcarinaButtons instead of getItemId. Otherwise that function is trying to draw RG_ICE_TRAP, and so ends up falling back to GID_STONE_OF_AGONY from the entries in item_list.cpp
You should be safe to not have to check for RG_ICE_TRAP first, since drawItemId will be the same as itemId (which for all the ocarina buttons is the same as getItemId).

EDIT: Just tried that, and unfortunately it did not work. Give me a moment.

Copy link
Contributor

@leggettc18 leggettc18 left a comment

Choose a reason for hiding this comment

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

Sorry for the review whiplash. Turns out the custom models as they are now as Ice Trap models won't work (at least during the GetItem Animation where link holds the item above his head), and fixing that is outside the scope of this PR. So just remove the added Ice Trap models for now, but do keep the trick names so that those will work when the ability to draw custom models as Ice Traps is fixed.

@Pepe20129
Copy link
Contributor Author

Removed the models.
This issue is probably also present in boss souls since they use a custom model and are added to the possible models for ice traps.

Copy link
Contributor

@leggettc18 leggettc18 left a comment

Choose a reason for hiding this comment

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

This one is my bad from when I attempted to resolve the merge conflict, I included what should be the needed fix for it.

…_death_mountain.cpp


Fix lost closing brackets from merge resolution.
@leggettc18 leggettc18 merged commit c860f7a into HarbourMasters:develop-rando Dec 28, 2023
@Pepe20129 Pepe20129 deleted the shuffle_ocarina_buttons_develop-rando branch December 28, 2023 20:05
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.

2 participants