I appear to have been updated. A quick five-minute walk around Whiterun and just outside seems to show nothing there is broken for me, either. Only Wrye Bash is unhappy about Update.esm as far as I can tell ...

...and SKSE, of course.

It would be if I hadn't updated that to the latest SKSE beta.

Forgot about the beta!

Here's to hoping the CK update isn't far behind.

so arthmoor USKP beta is out now ??

So we can't just go ahead and update our mods with just the skyrim.esm right?

If you're already using Update.esm you don't want to go ripping that out because you'll just wind up wiping out official fixes down the road. Give it a couple of days or so. CK updates don't tend to take them long to get out after the betas end.

v1.8 hasn't hit me yet, nice still have a CK to play with.;p

I'm a little confused. What's the danger of updating right now from the perspective of the mod user?

That official changes will invalidate mods and therefore break mods.

The worst being crashing.

[edit] oh and possibly tools and utilities don't work 100%,

FYI SVN version of Wrye Bash doesn't freak out about the new Update.esm, so just some patience on the next release (or use the bleeding edge version).

Im waiting till skse updates then i update skyrim

Grab the beta SKSE on the first page of their thread if you don't want to wait.

The more mods you have and the more tools you use the longer you have to wait. That has been the cycle.

Nope. Patch 1.8 doesn't break much. Old mods will continue to work, but they CANNOT be updated right now until the CK update comes along, hopefully in the next few days.

TES5Edit is already compatible with the new info found in 1.8 so that's safe to keep using.

Since Wrye Bash is slightly upset with the new Update.esm, I guess we'll be cutting an official 301 for that later today.

SKSE updated last week when beta 1.8.151 came out. Use that, it will become the live version without you needing to do anything.

^^ with this game I'm not so trusting.

Sounds good on paper though.

Yeay. Finally.

Thanks everyone

Well then trust someone who knows, yes? I've been on the beta for 2 weeks and had zero problems with mods that weren't already a result of obsolete files from before Patch 1.6.

So I cannot use the CK if Steam updates me to 1.8?

I ask because I have a mod to upload to Steam, but will not go 'online' and upload, if this means that Steam updating to 1.8 results in me not being able to use the CK.

You may use Skyrim.esm to mod with using 1.8 with impunity; the issue arises if you want to use Update.esm or anything requiring it (like Dawnguard.esm).

HearthFires.esm actually doesn't require Update.esm, but we don't have the source scripts so you're limited to world building there.

The CK does not stop working because of the 1.8 game update. However, the current CK 1.6.89 does not understand the updated new Update.esm. Therefore, you can't edit any mod that has Update.esm as a master and would require the CK to open it.

You can still use the CK with mods that do not have Update.esm as a master. However, creating such mods is not good practice, because that may cause the mod to overwrite official fixes included in Update.esm.

The latest SVN version still says the most recent revision is 2693, which doesn't like Update.esm. I'm looking at http://oblivionworks.svn.sourceforge.net/viewvc/oblivionworks/Programs/Wrye%20Bash/ Is this the correct location?

There's more to it than just a version number on Update.esm that the CK doesn't understand. The racial body part data was changed to a new subrecord. Any data relying on this will be broken and uneditable. Which usually means anything under the Armor heading - armors, clothing, etc. A wide range of things will not be possible to touch without the CK update.

Now, if you're one of those people who got hold of CK 1.6.91 and put it aside for whatever reason, that MIGHT work because it was using those new subrecords. I can't vouch for that though since I reverted to 1.6.89 when 1.6.91 was backed out.

I've given up on warning people about ignoring such things, so I won't waste any more keystrokes on saying it after this point, but just don't force the issue. Wait on the CK update.

The SVN version of Bash won't complain about Update.esm. It's been in use now for a little under 2 weeks, and hasn't complained once since the version number support was added.

Yes, that's the correct location. Wrye Bash shouldn't complain at all about Update.esm (the problem with the non-SVN is it doesn't like "1.70" as the version field in the header). Double check: in Bash what does your Update.esm say under the Version field.