dAb

Members
  • Content count

    39
  • Joined

  • Last visited

1 Follower

About dAb

  • Rank
    Hearthfriend
  • Birthday 04/08/74

Profile Information

  • Gender
    Male
  • Location
    Italy

Recent Profile Visitors

426 profile views
  1. dab, where u at

  2. Uh. I'm half through now but I'll certainly put your method to good use if needed again. Ty.
  3. Heh. Figured as much. Expecially the 'manually' part
  4. So, I have ESP A and ESP B. I need to mirror into ESP A a lot of records of ESP B, for the most part it's new perks, meaning that they are brand new records which do not exist in the game ESMs. So, I'll just have to copy them as new records. Problem is, they are either linked to each other through CK conditions or linked to vanilla perks through the "next perk" function. How do I go about properly importing everything without destroying ESP A in the process?
  5. It's back. Apparently enough complaints in the RELz thread persuaded moderators to put it back on.
  6. Don't flatter yourself, I arrived here first. [ciao ]
  7. How do you push SEQ files to XB1 using the CK?
  8. You might want to add a big red statement to Nexus as well, as I've seen a lot of people cleaning files already.
  9. One question which isn't answered here is.. how are we supposed to port a mod that requires USLEEP as a master? Will the switch masters xEdit script work?
  10. A-well-a everybody's heard about the bird
  11. Wow, lol. Things like that could make me bald.
  12. Oh my, it does what? Now I can see where all MO-related problems come from. So if I'm understanding this right it actually allows packaged assets to be loaded in a different load order than the ESPs?
  13. The way I do it, it's to make a new mod folder inside the Bash Installers folder and drop the very first file in there. Then I "install" the mod in WB so that it becomes green, as in properly synchronized with the Data folder contents. When more files I work with in the Data folder/subfolders are added and I'm done working with them, I copy them to the mod folder and do a refresh, if anything is dirty WB will warn you. Everything you'll need to gather up for packing will be into the mod folder, so that you can safely ignore what's scattered inside Data, and even uninstall and reinstall at will the mod you're working on, nothing will be lost. Perhaps there's even a more elegant way to do the above and I can't see it, but I got used to it and I've never made mistakes once.
  14. Oh, that clears that up. Perhaps things like these are reasons why MO users stay clear from Bash, even me being a long time user have not fully understood how it works and what I know about it I tend to forget it pretty fast