-
Notifications
You must be signed in to change notification settings - Fork 526
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
Blasphemous: Randomizer 2.0 #1883
Conversation
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 would look at at least changing some of the if-elif chains to dictionary lookups, other than that I'm happy with this. Didn't have have time to do any test gens
Oh, also, overall, I think the improvements you made to options are great. And in general, I could tell that you put a lot of thought into all of this :) Most of my complaints come from unwieldy if-elif chains and enourmous logical expressions in rules.py, everything else seems great |
I have no idea why The Messenger's |
I suspect one (or more) of the tests has a small % chance to fail. I pinged alwaysintreble on it so they can look. |
Well I updated my branch and it passed all the tests after that, so idk. It is strange that it only failed that one test though. |
Added another comment to one of the threads above, idk if you would notice that if it's marked as "resolved". I think it's valuable so I don't want it to go unnoticed :D |
I took your advice. It's definitely a lot nicer to look at now |
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.
In addition to the below, I saw you changed the relative imports to world.<...>
, I haven't tested the APWorld compatibility, but if you can confirm it works as an .apworld, can you also edit setup.py
to remove "Blasphemous" from non_apworlds
so it can output as an apworld during setup build?
Yeah it works as an APWorld, people have been playing it on their own already. And now that it doesn't use |
Overrides the option to check if it is set to random, and if it is then select a different valid location rather than raising an exception
Running into the following error on this PR (with
|
Whoops. Fixed it |
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.
Should be fine. Playthrough spoiler looks a bit ugly, but that should be resolved by #1925 (out of scope for this PR) and is very minor. Confirms works as an apworld on 3.11.
Co-authored-by: Fabian Dill <Berserker66@users.noreply.github.com>
Co-authored-by: Fabian Dill <Berserker66@users.noreply.github.com>
@BrandenEK and I have been working on getting the world for Blasphemous updated to work with Randomizer 2.0. Here is a full list of changes and new features:
expert_logic
option has been removed.difficulty
now affects both the number of upgrades required for boss fights, and whether or not the randomizer expects the player to know certain tricks/glitchesskip_long_quests
, which excludes the following locations, ensuring that they will not have important items: "Albero: Donate 50000 Tears", "Ossuary: 11th reward", "AtTotS: Miriam's gift", "TSC: Jocinero's final reward"Notably, we decided to cut Door Randomizer from AP for the time being. We agreed that it was more important to worry about it later and focus on getting the rest of the new features to work instead, so that people don't have to downgrade versions to play Multiworld anymore.