[Anprionsa]

Hi Lava,

I'm running into an installation failure with Athkatlan Grounds: The Ooze's Lounge v3.0 on EET (BG2:EE with Enhanced Edition Trilogy). The error occurs during component 0:

```
ERROR locating resource for 'COPY'
Resource [AR0400.wed] not found in KEY file:
      [./chitin.key]
ERROR: Failure("resource [AR0400.wed] not found for 'COPY'")
```

**Investigation results:**

After digging into this, I found that this is not an EET-specific issue — it would affect vanilla BG2:EE as well. The BG2:EE engine does not store area WED files as standalone indexed resources in chitin.key or BIF files.

Specifically:
- Vanilla BG2:EE's chitin.key contains **zero** AR-prefixed WED entries
- The AREA0400.bif file contains height maps, light maps, search maps, and ambient sounds — but no WED or ARE resources
- The ARE file (AR0400.ARE) references "AR0400" as its WED, but this WED resource simply doesn't exist as a BIF-indexed resource on the EE engine
- The 1,648 resources using the WED type code (0x3ee) in chitin.key are all spell effects, items, and other non-area resources — none are actual area layout files

The EE engine appears to handle area layout/rendering through a different mechanism than classic BG2, where WED files were stored in the BIF/KEY structure and accessible via COPY_EXISTING.

**Environment:**
- BG2:EE v2.6
- EET (Enhanced Edition Trilogy)
- WeiDU v25100
- Ooze's Lounge v3.0
- Windows 11 Pro

**Suggested fix:**
The COPY_EXISTING on AR0400.wed would need to be replaced with an alternative approach that doesn't rely on WED files being present as indexed resources. Other mods that modify area layouts on EE typically use ADD_AREA_TRIGGER, EXTEND_TOP/BOTTOM on area scripts, or patch the ARE file directly rather than copying the WED.

Happy to provide more details or test a fix if needed. Thanks for the great mods!

— Anprionsa

[Lava]

Erm, it does work normally, and I've just tested it. 

// Log of Currently Installed WeiDU Mods
// The top of the file is the 'oldest' mod
// ~TP2_File~ #language_number #component_number // [Subcomponent Name -> ] Component Name [ : Version]
~OOZE/OOZE.TP2~ #0 #0 // Athkatlan Grounds: The Ooze's Lounge - a new area under Athkatlan Slums: v3.0

This was coded that way from the very first version and the function works fine and people are also playing it on EET normally. 

The mod must include update of the .wed file, it's something entirely else than ADD_AREA_TRIGGER, EXTEND_TOP/BOTTOM, because the mod needs to adjust wall regions and the open/closed animations to that area. 

Sorry, but I don't think the error has anything to do with this mod; it's been there since 2018.

[Anprionsa]

You could very well be right, I can't quite nail it down yet, but Ooze has failed a few times in the last 50 or so times I've done an install test. 

I'm using mod_installer, so it's hard to say what the issue could be or if it's further up the chain.

[Lava]

I also checked if the new .wed is being added to override, and it is. Sadly, Gwendolyne, who helped with that part of the mod, has most likely retired; he hasn't been around for a very long time.

EDIT: my test was on EE. I no longer use oBG2.

[Anprionsa]

I'm going to modify mod installer to see if I can't find out what's causing the corruption. If it isn't Oozes, then something else is causing the issue. I'll report back.

[CamDawg]

The EE engine appears to handle area layout/rendering through a different mechanism than classic BG2, where WED files were stored in the BIF/KEY structure and accessible via COPY_EXISTING.

FWIW, EE Fixpack uses COPY_EXISTING on multiple WED files without issue.

[Lava]

I tried to install the mod again, it went fine. Then I removed the game, removed all files, installed the game again and then tried to install Ooze's Lounge again and it also went fine. I don't think the setup can be cleaner than that.

[Anprionsa]

The EE engine appears to handle area layout/rendering through a different mechanism than classic BG2, where WED files were stored in the BIF/KEY structure and accessible via COPY_EXISTING.

FWIW, EE Fixpack uses COPY_EXISTING on multiple WED files without issue.

Hmmm, must be something else I'm missing then.

---

Thanks for taking the time to test it clean, Lava. And CamDawg, good to know EE Fixpack uses COPY_EXISTING on WEDs without trouble — that narrows it down.

I'm fairly confident now it's on my end. I tracked down a file caching issue in the installer where copied files weren't being properly flushed to disk before WeiDU tried to read them. That would explain why the KEY file lookup fails intermittently — the data just wasn't fully there yet. I've patched the copy routine so it should be resolved on the next install run. I'll report back either way.

[Lava]

I hope you'll be able to make it all work fine for you

[Anprionsa]

You're the best Lava, been loving your stuff for years now.

[Lava]

Thank you!

[Anprionsa]

Just wanted to say that it was definitely an installer issue. I've got it all sorted now. It was indeed a false positive. No issues since.

[Lava]

Thanks for letting me know  Have a great day!