-
Notifications
You must be signed in to change notification settings - Fork 671
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
Terraria: Add crate logic #2841
Terraria: Add crate logic #2841
Conversation
Dict[str, int], | ||
] | ||
): | ||
def read_data() -> Tuple[ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this monster have to be built out of recursive tuples?
I'm scared
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh god I missed that now I’m shaking in my boots
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there's a reason for it. it accurately represents the data structure of the output data or something idk that's chatgpts word
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the outer tuple is fine, it gets split up on line 719, but yeah the rules type is messy. It's not relevant to this pr, though. It just got caught by my formatter. I'll move it to a class if I end up doing parser reworks
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes LGTM. Tested the grindy logic by looking at spoiler logs. Walked through the logic changes with a friend who knows the game better than myself; we concluded that they were correct.
What is this fixing or adding?
Terraria fishing crate logic. I originally excluded it because it could be grindy, but I've found that it doesn't affect accessibility anyway, except for the Head in the Clouds achievement, whose logic I've changed based on whether grindy achievements are enabled.
How was this tested?
I generated a world and made sure checks still work, and then I generated a lot of worlds and checked if their spoilers match what I expect