From 113259bc1546ec648b4d1780ec79e6c7b53f11f8 Mon Sep 17 00:00:00 2001 From: Exempt-Medic <60412657+Exempt-Medic@users.noreply.github.com> Date: Fri, 7 Mar 2025 20:17:45 -0500 Subject: [PATCH] Update links (#4690) * Update links * Update two more --- docs/tests.md | 4 ++-- docs/world api.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/tests.md b/docs/tests.md index c8655ccf..e7f40042 100644 --- a/docs/tests.md +++ b/docs/tests.md @@ -73,11 +73,11 @@ When tests are run, this class will create a multiworld with a single player hav generic tests, as well as the new custom test. Each test method definition will create its own separate solo multiworld that will be cleaned up after. If you don't want to run the generic tests on a base, `run_default_tests` can be overridden. For more information on what methods are available to your class, check the -[WorldTestBase definition](/test/bases.py#L104). +[WorldTestBase definition](/test/bases.py#L106). #### Alternatives to WorldTestBase -Unit tests can also be created using [TestBase](/test/bases.py#L14) or +Unit tests can also be created using [TestBase](/test/bases.py#L16) or [unittest.TestCase](https://docs.python.org/3/library/unittest.html#unittest.TestCase) depending on your use case. These may be useful for generating a multiworld under very specific constraints without using the generic world setup, or for testing portions of your code that can be tested without relying on a multiworld to be created first. diff --git a/docs/world api.md b/docs/world api.md index 6a45ccbf..9e3fe67b 100644 --- a/docs/world api.md +++ b/docs/world api.md @@ -291,7 +291,7 @@ like entrance randomization in logic. Regions have a list called `exits`, containing `Entrance` objects representing transitions to other regions. -There must be one special region (Called "Menu" by default, but configurable using [origin_region_name](https://github.com/ArchipelagoMW/Archipelago/blob/main/worlds/AutoWorld.py#L295-L296)), +There must be one special region (Called "Menu" by default, but configurable using [origin_region_name](https://github.com/ArchipelagoMW/Archipelago/blob/main/worlds/AutoWorld.py#L298-L299)), from which the logic unfolds. AP assumes that a player will always be able to return to this starting region by resetting the game ("Save and quit"). ### Entrances @@ -331,7 +331,7 @@ Even doing `state.can_reach_location` or `state.can_reach_entrance` is problemat You can use `multiworld.register_indirect_condition(region, entrance)` to explicitly tell the generator that, when a given region becomes accessible, it is necessary to re-check a specific entrance. You **must** use `multiworld.register_indirect_condition` if you perform this kind of `can_reach` from an entrance access rule, unless you have a **very** good technical understanding of the relevant code and can reason why it will never lead to problems in your case. -Alternatively, you can set [world.explicit_indirect_conditions = False](https://github.com/ArchipelagoMW/Archipelago/blob/main/worlds/AutoWorld.py#L298-L301), +Alternatively, you can set [world.explicit_indirect_conditions = False](https://github.com/ArchipelagoMW/Archipelago/blob/main/worlds/AutoWorld.py#L301-L304), avoiding the need for indirect conditions at the expense of performance. ### Item Rules