817197c14d
The static class with the "disable forced good item" field is gone. Now, certain tests that want to check for specific access progression can run a method that removes the forced good item and adds it back to the pool. Tests that don't care about this will collect the forced good item like normal. This should prevent the intermittent fill failures on complex doors unit tests, since the forced good item should provide enough locations to fill in.
18 lines
512 B
Python
18 lines
512 B
Python
from typing import ClassVar
|
|
|
|
from test.bases import WorldTestBase
|
|
|
|
|
|
class LingoTestBase(WorldTestBase):
|
|
game = "Lingo"
|
|
player: ClassVar[int] = 1
|
|
|
|
def world_setup(self, *args, **kwargs):
|
|
super().world_setup(*args, **kwargs)
|
|
|
|
def remove_forced_good_item(self):
|
|
location = self.multiworld.get_location("Second Room - Good Luck", self.player)
|
|
self.remove(location.item)
|
|
self.multiworld.itempool.append(location.item)
|
|
self.multiworld.state.events.add(location)
|