FNVEdit bug when using "Copy as Override" on a Base Effect associated to a script

[GoogleCodeExporter]

What steps will reproduce the problem?
1. With FNVEdit loads the FalloutNV.ESM file
2. Go to the "Base Effect" section
3. Select a base effect with an associated script (for example, 
NightstalkerPoisonEffect "Nightstalker Poison" [MGEF:00147D26])
4. Right-click and try to "Copy as Override" into another file
5. When FNVEdit asks the user if FalloutNV.esm should be added to the masters 
list of the other file, select "Yes"

What is the expected output?

FNVEdit should properly copy as override both the associated script and the 
base effect into the second file

What do you see instead?

FNVEdit doesn't copy the associated script. The Base Effect is then associated 
a null reference (NULL - Null Reference [00000000]).

What version of the product are you using? On what operating system?

The problem is old, I remember it started at least in the early months of 
FNVEdit

Please provide any additional information below.

See supplied ESP

Original issue reported on code.google.com by danielhmpdx16@gmail.com on 5 Oct 2012 at 1:51

Attachments:

• [FNV - Base Effect Associated Script Bug.esp](https://storage.googleapis.com/google-code-attachments/skyrim-plugin-decoding-project/issue-60/comment-0/FNV - Base Effect Associated Script Bug.esp)

[GoogleCodeExporter]

Original comment by danielhmpdx16@gmail.com on 5 Oct 2012 at 2:07

[GoogleCodeExporter]

Original comment by zila...@gmail.com on 13 Oct 2012 at 6:01

• Changed state: Evaluating

[GoogleCodeExporter]

I looked at that issue and the problem is that "Associated" value is a union 
that depends on a field "Archtype" that comes after it, so looks like when 
copying union decider for a new record can't find the correct deciding value 
because that value doesn't exist yet.
However almost the same code I wrote for Skyrim works there, need more time to 
investigate :)

Original comment by zila...@gmail.com on 5 Nov 2012 at 9:33

• Changed state: Accepted

[GoogleCodeExporter]

The exact issue is that wbMGEFArchtypeAfterSet forces "Assoc. Item" to zero on 
any Archtype change, and archtype is assigned AFTER "Assoc. Item".
I will try to use a wbMGEFFAssocItemAfterSet to force the proper archtype when 
assigning "Assoc. Item".

Original comment by HuguesLe...@gmail.com on 2 Jan 2013 at 12:07

[GoogleCodeExporter]

This should be solved by r1070.

Original comment by HuguesLe...@gmail.com on 2 Jan 2013 at 2:13

[GoogleCodeExporter]

Did MGEF version of TES5, should be up soon.

Original comment by HuguesLe...@gmail.com on 2 Jan 2013 at 8:51

[GoogleCodeExporter]

Original comment by HuguesLe...@gmail.com on 14 Jan 2013 at 12:24

• Changed state: Started

[GoogleCodeExporter]

fixed in 3.0.28

Original comment by HuguesLe...@gmail.com on 9 Feb 2013 at 6:52

• Changed state: Fixed