-
Notifications
You must be signed in to change notification settings - Fork 238
Boss room shuffle #1468
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
Boss room shuffle #1468
Changes from all commits
0dfdfbb
5662a8d
c693ef6
4c5ba07
8ea2879
d4087ff
63c7e87
0f28c6f
72e8998
e1dbf6e
67e76a7
8e4f1e5
6f03c34
1f5cee5
ce2b15e
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -109,6 +109,15 @@ def get_scene(self): | |
return None | ||
|
||
|
||
def change_dungeon(self, new_dungeon): | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is there a reason for boss rooms to be tagged with a dungeon at all? I think it could be more straightforward to not consider boss rooms as part of any dungeon's hint area, and instead relying on finding the dungeon as the nearest hint area in the same way that interiors do. This would also make hints behave well in mixed pools boss shuffle if that ever becomes a thing. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes, Updating change_dungeon to accept |
||
# Change the dungeon of this region, removing it from the old dungeon list and adding it to the new one. | ||
if new_dungeon == self.dungeon: | ||
return | ||
self.dungeon.regions.remove(self) | ||
self.dungeon = new_dungeon | ||
new_dungeon.regions.append(self) | ||
|
||
|
||
def __str__(self): | ||
return str(self.__unicode__()) | ||
|
||
|
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.
This seems to be redundant with the code added above. Why is a change needed here anyway, besides inserting the
boss_map
indirection?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.
This is a backport from Roman's fork. Boss Shuffle began there and I ported it to Dev branch since I felt it more likely to be accepted here and then merged into Roman's that way. I think I didn't realize that Dev didn't have it this way when rebasing.
Here is the original source: https://github.com/Roman971/OoT-Randomizer/blob/Dev-R/Patches.py#L1863..L1880
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.
The code added above was a leftover on my branch (I'm guessing due to some merge conflict), and I just removed it from Dev-R. I think you should be able to just adjust the existing code to use
boss_map
and omit the rest.Here is the commit where I removed it for reference: Roman971@ba15f86