Simple Question

[Riven1978]

Ok the story is i am merging a few mods in order to make room for more hehe, and as i am going through the Mod and doing a bit of clean up through the use of the GECK, FOMM's Plug-in Editor, FO3EDIT for use of changing the duplicating ID's and such. Well the Problem i have is when i get the error "File 'merge01.esp' contains a form with a master file ID but no match in the master file: (00F12345)" (this is only one of the few that i do get. I am checking the original mod for this item to see if it might have happened when i merged it, but no the original file has it as well. The item works Perfect in the original (as best as i can tell) So why does the error pop up (errors are not always things that are wrong per se, just things they want to call attention too). I did read somewhere at one time or another, about it being because of a forced FormID Change through FOMM or FO3edit (not sure if it is true or not), but my attempts to find where i read it hoping that i might be able to finish where that story line went to ; I didn't heed any note to it because it wasn't a problem i was having so i skipped that comment. My question now stands to either those who may have answered the question somewhere else or to some one new who might just happen by this Post.... Why do i get an error about something in a MOD (see error above) When there is nothing seemingly wrong with the item in question? Also. How would one go about "fixing" said error?

 

 

Riven1978

[TGBlank]

The error you're getting is that comes from a combination of this:

 

- "item" is not a "new" item, but an override of one from one of the master files of the plugin.

 

- "item" cannot be found on the masterfile.

 

It may be that the "item" was removed in a later version of the master file, and the item of the mod in question you're merging does not actually work. Or that you did a sloppy merging there. If you did edited the item's base-id manually, the later is likely to be the case.

[Riven1978]

It may be that the "item" was removed in a later version of the master file, and the item of the mod in question you're merging does not actually work. Or that you did a sloppy merging there. If you did edited the item's base-id manually, the later is likely to be the case.

 

Well i already discovered that it wasn't sloppy merging on my part, since the original file (reinstalled it to make sure) is doing it on the exact same items. My question was why would the original modder done to cause the error in the first place. I want to know in order to make sure i don't do something to mimic the effect. and also how i might go about fixing the one i already have to not cause the error anymore. I am sorry if the questions sounded too vague or misleading.

[Phoynix]

Its a phantom error, the cause for it is hex editing new idents rather before geck was out, that isnt to say the error isnt real too, but its more then likely false.

 

My mod has this problem.

Basicly I copied a master file ident, changed its ident, but its still taged somewhere in the hex as a masterfile file, so its automaticly made a dependent.. but when its checked there is no master in the master file to match it.. so geck will give an error, despite this it works perfect in game and doesnt override anything.

 

To fix it would mean making new textures/item idents from scratch, thats about 15mins work so why bother, I actually saw something about a program that can remove the error but I was in a hurry at the time and been unable to find it since. I was of the view why bother wasting 15 mins to recreate the file, but if its screwing up merging I guess I need too as I made my mod as a resource for other modders to use.

 

Its not my blastermod is it, that would be ironic.

[Riven1978]

Its a phantom error, the cause for it is hex editing new idents rather before geck was out, that isnt to say the error isnt real too, but its more then likely false.

 

My mod has this problem.

Basicly I copied a master file ident, changed its ident, but its still taged somewhere in the hex as a masterfile file, so its automaticly made a dependent.. but when its checked there is no master in the master file to match it.. so geck will give an error, despite this it works perfect in game and doesnt override anything.

 

To fix it would mean making new textures/item idents from scratch, thats about 15mins work so why bother, I actually saw something about a program that can remove the error but I was in a hurry at the time and been unable to find it since. I was of the view why bother wasting 15 mins to recreate the file, but if its screwing up merging I guess I need too as I made my mod as a resource for other modders to use.

 

Its not my blastermod is it, that would be ironic.

 

 

Ah I see so this was a problem for back before the geck was out.... hehe would it be better on my merge mod if i just inputted it manually from the beginning then to actually merge it, the problem would go away then right?

[Riven1978]

Its a phantom error, the cause for it is hex editing new idents rather before geck was out, that isnt to say the error isnt real too, but its more then likely false.

 

My mod has this problem.

Basicly I copied a master file ident, changed its ident, but its still taged somewhere in the hex as a masterfile file, so its automaticly made a dependent.. but when its checked there is no master in the master file to match it.. so geck will give an error, despite this it works perfect in game and doesnt override anything.

 

To fix it would mean making new textures/item idents from scratch, thats about 15mins work so why bother, I actually saw something about a program that can remove the error but I was in a hurry at the time and been unable to find it since. I was of the view why bother wasting 15 mins to recreate the file, but if its screwing up merging I guess I need too as I made my mod as a resource for other modders to use.

 

Its not my blastermod is it, that would be ironic.

 

 

Ah I see so this was a problem for back before the geck was out.... hehe would it be better on my merge mod if i just inputted it manually from the beginning then to actually merge it, the problem would go away then right?

 

 

 

Edit finally found an Obscure refence after more digging which says it can be safely ignored hehe :whew:

 

[

QUOTE (Arthmoor @ Mar 20 2009, 09:25 AM) *

That particular error appears to be carrying over from oblivion.esm. I don't know for sure if the 31 flag is bogus or if it's just a flag Elminster hasn't figured out. I'd recommend leaving it be as it could be one of those instances where "fixing" it actually makes things worse.

 

There is no way in TESCS to set or reset this specific flag in any way. As such the meaning of the flag is unknown, probably it's being totally ignored by the game engine (but I can't say for sure). The "Check for Errors" function lists everything that it find which doesn't exactly match the record definition.

 

This particular error can safely be ignored.

Actually was kind of hard for me to find it seeing as how i have never really played nor modded Oblivion >.< so now here it is for Fallout 3 if anyone else has the burning itch. Still would like a way to fix it without totally re inputting the info in if anyone knows of the program "Phoynix" is talking about. It just annoys me to have to click those little boxes every time i want into my new merge mod :P