Arthmoor

Generally, no, it won't cause you any trouble. You do need to keep in mind though that finalizing a cell will propagate changes to the 4 cells in each direction from the one you're editing. North/South/East/West. You'll end up with a total of 5, and potentially a lot more. Best bet is once you're done doing that, load the mod into TES5Edit and clean it. It will remove any dirty edits that result from finalizing, and there's usually a LOT more than just the 5 cells.

Guess I'm a bit late in reporting this then :P +1 for being a fly on that wall. That would be epic.

Why would you want an old version though? A lot of fixes for Oblivion, FO3, and FNV have been done along the way too.

Or if you're one of the lucky few for whom it works (I'm not, sadly) you can tell Steam to switch to offline mode and then just never log it back on. Don't count on this actually helping though because Steam tends to force its way online again seemingly at random.

*pokes his nose in* So. There are really THAT MANY people who DON'T resent government intrusion into private life that this test calls me a talking head because I do? :blink: Ok then. I will consider myself proud not to be part of the "New American Center".

Also mine: http://skyrim.nexusmods.com/mods/16084

This bug was fixed in the Unofficial Skyrim Patch.

Hopefully they're listening then because 18-24 months is long enough for most people to shelve the game and move on to other things.

They're not lazy, just hamstrung by management's stupidity in not ditching their garbage engine sooner and going with something genuinely new instead of lying to us all and claiming they were. Frankly I think it's all going to change soon when Witcher 3 comes along and schools everyone in what a proper open world game looks like.

Can't be done. You need to start a new game. Removal of a mod with that many script intensive things going on is not possible. This isn't limited to just Warzones either. As a general rule, it's not safe for your save to remove ANY mod from the game aside from some very simplistic things that don't change much. Or mods that don't come with esm files, esp files, or scripts at all. SKSE cannot help you either. And especially stay away from any tool which claims it can clean your save. All those will do is further corrupt the game for you.

Then you aren't giving the place a fair shake. @OP: Check out the mods by ThirteenOranges. Most of it is really good.

That's because the fix you're talking about is still being trialed in the beta. It hasn't gone public yet.

Updated the OP for this as it was written before TES5Edit could do these. Yes, this is still necessary. It's not a bug that we need them. They're required for start-enabled quests to function properly in the same way facegen files have to be exported for NPCs to look right.

No, actually it DOES mean you either have the wrong load order, or the UDBP isn't activated even though NMM may have told you otherwise. It's notorious for not actually doing so. Barring that, you should make sure you DON'T have Data\Scripts\DragonActorScript.pex laying about in there. Installing loose scripts as stopgap fixes is generally a bad idea because they tend to get forgotten and when updates to them happen in the BSA files, you'll be scratching your head wondering why it's not working.

Just an FYI, but this will do nothing for these log spamming scripts. That setting ONLY applies to mods which have been removed from the game and left behind rogue RegisterForUpdate type events. Since you obviously can't remove Skyrim.esm from the game, any registrations it makes are entirely valid even if they're bugged to all hell. SKSE will NOT remove these. @Steve40: Some folks are asking for us to incorporate this into the USKP. Would you have any objection to us doing so? If not, can we have your permission to incorporate this once we've put it through some testing?

Are you sure all of the texture paths in the meshes are in the proper format? Like so: textures\somefolder\someotherfolder\somefile.dds Rather than: textures/somefolder/someotherfolder/somefile.dds If the slash marks are wrong, they won't display from inside of a BSA. PyFFI will correct this. You'll also need to be sure all of the textures have mipmaps, because the ones that don't also won't display. That's a bit harder to work out. Possibly DDSOpt will fix this, but I don't know as I've never used that.

In response to post #7520441. Looks like 960x175 for the background banner after cropping. Hotfile image is 928x270 after cropping.

One of those spinning Dwemer blade traps you find in the ruins appears to have gone insane. Try opening the console and typing this: player.moveto 00052458 Be ready to move away quickly as you'll probably land right on the thing. Stand a little bit away from it and let it finish doing whatever it's doing. Then leave, and hopefully the issue stops after that.

Your save has had both Dawnguard and Dragonborn active at some point. That's what all the Papyrus errors about missing files mean. You'll either need to reactivate the ESMs for the DLC files or start a new game. Your CTDs are being caused by data your game is looking for but can't find from the DLCs.

It's a recent issue, likely caused by one of Valve's unwelcome client updates. Bethesda knows about it and last they said they're investigating the issue.

Since there's no difference at all in the actual data files, it makes zero sense for PC not to have this already. The PC is the XBox's competent and capable older brother that can do anything it can do and then some. Performance issues would not be holding anything back. The 30 day Microsoft exclusivity is over and gone, so that's no longer flying as an excuse either. If anyone actually thinks they're holding back to fix bugs, they don't know this company well at all. History proves they don't fix DLC bugs. Not even when said DLC has a private beta going on. NOTHING the Xbox beta testers reported for Dawnguard was fixed for PC. So they all got to beta test for absolutely no reason whatsoever. Dawnguard is 6 months old and has never been patched, and history says it never will be. The PS3 situation sucks, but why enrage the PC fans over that? It makes no sense. Especially since instead of telling us what's going on they're spending their time fawning over fan art and tablet support for Dishonored and trumpeting Elder Scrolls Online.

Yep, Skyrim went belly up too. Or maybe that's just where all the other folks on the affected box are shifting their attentions to. It's lagging BAD, but still functioning.

The SEQ file has to go into your BSA file. Your BSA file then uploads to the workshop with your ESP. All nice and neat like.

If I decide to go on hiatus, it's still my mod. If I decide to never update it again, it's still my mod. That I personally decide to relinquish my rights in the event that I go AWOL, doesn't mean any mod automatically becomes community property, and people like you make me rethink my community-friendly stance. Pretty much all of this. Including that last part. All of this is the sort of poison that will eventually cripple a healthy community. I've been there, done that, and don't care to repeat it. It results in chronic stagnation at best, and will outright kill a community at worst.

That's probably it then, another one just dribbled out for me from February. Not a huge deal, just slightly confusing when Thunderbird says I have a new one and it's at the top of the list :P