From 08ea3fe22539f44933088a4c0e57c579e1ea3089 Mon Sep 17 00:00:00 2001 From: Mysteryem Date: Sat, 29 Nov 2025 18:09:30 +0000 Subject: [PATCH] ALTTP: Fix setting `Beat Agahnim 1` event twice (#5617) alttp was setting the `Beat Agahnim 1` event onto the `Agahnim 1` location twice. I was debugging a multiworld generation issue with various custom worlds, where, for debugging purposes, I changed `multiworld.push_item` to make it crash like `location.place_locked_item` when the location was already filled, which also identified this minor issue in alttp. --- worlds/alttp/ItemPool.py | 1 - 1 file changed, 1 deletion(-) diff --git a/worlds/alttp/ItemPool.py b/worlds/alttp/ItemPool.py index 7b64e6e5d3..6b0968f6e5 100644 --- a/worlds/alttp/ItemPool.py +++ b/worlds/alttp/ItemPool.py @@ -263,7 +263,6 @@ def generate_itempool(world): ('Frog', 'Get Frog'), ('Missing Smith', 'Return Smith'), ('Floodgate', 'Open Floodgate'), - ('Agahnim 1', 'Beat Agahnim 1'), ('Flute Activation Spot', 'Activated Flute'), ('Capacity Upgrade Shop', 'Capacity Upgrade Shop') ]