Team work flow for GECK modders

Post » Wed Jul 21, 2010 10:07 pm

Knowing is half the battle against the "Children". If a REF has an editor ID, it seems more likely to be orphaned after copying over. If any given REF or INFO has ended up orphaned in an FO3Edit session, one has to delete it/them and reload the program, then try again as that particular record will invariably end up orphaned if re-copied in the same session. To save time, if copying into an ESM with a large ONAM list, untick the ESM flag of the recipient file so you don't have to wait for it to build the ONAM list every session until all records are copied and fostered as they should be, then re-tick the ESM flag when done. If ever you encounter an INFO that just won't copy, you can manually add an empty info to the recipient's target topic and assign it the errant INFO's Form ID when doing so, allowing you to then drag/drop the subrecord data and all should work out.


Wow - more for the notes!

In reality, I think it should have been your knowledge behind the Fo3Edit guide with my documentation/diagramming capability - it would have been way more accurate and useful!

Noting all this down as well. When I finish the FWE work and start the updates to the Fo3Edit guide, would you be willing to proof it (or parts of it?)?

Cheers!

Miax
User avatar
Lauren Denman
 
Posts: 3382
Joined: Fri Jun 16, 2006 10:29 am

Post » Wed Jul 21, 2010 7:52 pm

I'd be down to contribute to the manual anything work-arounds I've learned and/or proofread the parts I'm familiar with. :) FOOK's next iteration is really close to ready, so I'll have time for other stuff soon peovided nobody's PC kerplodes over loading the plugins or anything.
User avatar
Tracey Duncan
 
Posts: 3299
Joined: Wed Apr 18, 2007 9:32 am

Previous

Return to Fallout 3