Sigh .... Another Forced Update .... Bethesda embarrassing itself yet again

[Deleted119721User]

In Steam under the Properties tab for Skyrim Special Edition there is "Allow Updates" field that is greyed out, Bethesda has 100% control of this field so Updating SSE is nothing to do with Steam. I fully understand why they would grey out his field SOMETIMES, but not all the time and not when SKSE64 will be broken until that and all the dependent mods get updated.

 

Many people use SKSE64 and I have has no issues with it ..... but updates break SKSE.

 

Bethesda could allow us to "Not Allow Updates" during the times when updates will break peoples ability to play. Then when SKSE64 and all the depend mods get updated then they can Force Updates again with the "Allow Updates" greyed out. This isn't rocket science .... it is simple courtesy....

 

and no it doesn't matter that SKS64 is still in alpha ..... everybody knows it works and works well.....

 

Thanks to the Nexus I managed to avoid the update this time ......

 

 

In case Todd or whoever is unable to log into their laptops and enable the "Allow disabling of Updates" flag fro SSE I wrote some Pseudo code for Beth

 

Properties n = int ;number of days to allow update disabling

Properties SafeUpdate int ;SKSE64 conditional

 

On Update Notification PASS from SSE QA Deptarment

external email: Send update warning email to Skyrim SSE Nexus and Bethnet

Set allowDisableUpdate to 1 for n days

Begin deployment

On Update Begin

If File scan SKSE64

Set SafeUpdate to disabled for n days

else

Initialize and Update

endif

end

end

[Arthmoor]

That's a Steam client issue, not something Bethesda controls. All Bethesda does is push files to update on Steam and the client does the rest. Besides, that option was never disabled - it queued up and waited for me just like it's supposed to.

[Virde]

Many users are using a Beta version of SKSE64 against the advisement of the SKSE development team knowing full well that updates have always broken SKSE (Even in Oldrim and Fallout) since SKSE checks versions numbers.

 

The only one to blame here is the user for not taking the needed steps to prevent errors that they knew were going to come eventually.

[Deleted119721User]

 

 

 

 

 

 

 

In Steam under the Properties tab for Skyrim Special Edition there is "Allow Updates" field that is greyed out, Bethesda has 100% control of this field so Updating SSE is nothing to do with Steam. I fully understand why they would grey out his field SOMETIMES, but not all the time and not when SKSE64 will be broken until that and all the dependent mods get updated.

 

Many people use SKSE64 and I have has no issues with it ..... but updates break SKSE.

 

Bethesda could allow us to "Not Allow Updates" during the times when updates will break peoples ability to play. Then when SKSE64 and all the depend mods get updated then they can Force Updates again with the "Allow Updates" greyed out. This isn't rocket science .... it is simple courtesy....

 

and no it doesn't matter that SKS64 is still in alpha ..... everybody knows it works and works well.....

 

Thanks to the Nexus I managed to avoid the update this time ......

 

 

In case Todd or whoever is unable to log into their laptops and enable the "Allow disabling of Updates" flag fro SSE I wrote some Pseudo code for Beth

 

Properties n = int ;number of days to allow update disabling

Properties SafeUpdate int ;SKSE64 conditional

 

On Update Notification PASS from SSE QA Deptarment

external email: Send update warning email to Skyrim SSE Nexus and Bethnet

Set allowDisableUpdate to 1 for n days

Begin deployment

On Update Begin

If File scan SKSE64

Set SafeUpdate to disabled for n days

else

Initialize and Update

endif

end

end

Hi A .... The option to block updates is greyed out on my install of SSE..... If Beth doesn't control this option setting does that make them look more or less competent ....?

 

Well .... mod authors are being very quick in supporting v39 but Just Knock hasn't been updated yet so my load would be inoperable if I didn't play in Off-line mode.....

 

Why would I even want to update .... Finally after 2 years SSE runs properly ..... Who knows what this update may break ..... Beth and mod devs would have to come up with something compelling before I would voluntarily update ...... Modders fixed the wolf howl ages ago .....

 

To the guy that says SKSE64 breaks your game .... Not in my experience .... My install hasn't even burped ... For the first time since Oldrim came out I play without even thinking of ctds ....

[Arthmoor]

This update doesn't break anything. Breakages happen when modders ignore updates and don't update their mods. Those are the people you should be blaming when things go south on you.

 

So by your logic Bethesda should never update the game just because the unofficial patch exists? That's a rather narrowminded and selfish view of things.

[TheWilloughbian]

Considering the purpose of the latest patch, it's more of a nuisance than anything. Then again, after the first time an auto update messed up my game, I made damn sure that the game can't update unless I say so.

 

However, I also know to keep backups of the Skyrim EXEs, like all SKSE64 users should do.

[Deleted119721User]

One of last of the SKSE dependent mods ("Simply Knock") which many people use got updated to 2.07 today. Actually that was quick considering.

 

There is still question regarding SkyUI and 2.07 ,,,,but the consensus is that it is broken after update SKSE64. Still a no go then ....

 

Why would update my perfectly working 2.06 install for almost no benefit .......?

 

Beth shouldn't even bother with these updates until there is some compelling content to download.

 

An example of compelling content would be Beth COMPLETELY gutting out the poorly thought out, quarter done civil war where the player is forced to kill their brothers for puppet masters AND replacing it with a large scale conflict with the Thalmor.......Don't say it couldn't be done .... its only a question of will and economics ....... which will prevail as usual.

 

Examples of uncompelling content: mods which attempt to do something modders have already done better, weapon packs and pseudozombie hordes.

 

Don't say it couldn't be done .... its only a question of will and economics .......

[Deleted119721User]

 

In Steam under the Properties tab for Skyrim Special Edition there is "Allow Updates" field that is greyed out, Bethesda has 100% control of this field so Updating SSE is nothing to do with Steam. I fully understand why they would grey out his field SOMETIMES, but not all the time and not when SKSE64 will be broken until that and all the dependent mods get updated.

 

Many people use SKSE64 and I have has no issues with it ..... but updates break SKSE.

 

Bethesda could allow us to "Not Allow Updates" during the times when updates will break peoples ability to play. Then when SKSE64 and all the depend mods get updated then they can Force Updates again with the "Allow Updates" greyed out. This isn't rocket science .... it is simple courtesy....

 

and no it doesn't matter that SKS64 is still in alpha ..... everybody knows it works and works well.....

 

Thanks to the Nexus I managed to avoid the update this time ......

 

 

In case Todd or whoever is unable to log into their laptops and enable the "Allow disabling of Updates" flag fro SSE I wrote some Pseudo code for Beth

 

Properties n = int ;number of days to allow update disabling

Properties SafeUpdate int ;SKSE64 conditional

 

On Update Notification PASS from SSE QA Deptarment

external email: Send update warning email to Skyrim SSE Nexus and Bethnet

Set allowDisableUpdate to 1 for n days

Begin deployment

On Update Begin

If File scan SKSE64

Set SafeUpdate to disabled for n days

else

Initialize and Update

endif

end

end

Hi A .... The option to block updates is greyed out on my install of SSE..... If Beth doesn't control this option setting does that make them look more or less competent ....?

 

Well .... mod authors are being very quick in supporting v39 but Just Knock hasn't been updated yet so my load would be inoperable if I didn't play in Off-line mode.....

 

Why would I even want to update .... Finally after 2 years SSE runs properly ..... Who knows what this update may break ..... Beth and mod devs would have to come up with something compelling before I would voluntarily update ...... Modders fixed the wolf howl ages ago .....

 

To the guy that says SKSE64 breaks your game .... Not in my experience .... My install hasn't even burped ... For the first time since Oldrim came out I play without even thinking of ctds ....

 

 

In Steam under the Properties tab for Skyrim Special Edition there is "Allow Updates" field that is greyed out, Bethesda has 100% control of this field so Updating SSE is nothing to do with Steam. I fully understand why they would grey out his field SOMETIMES, but not all the time and not when SKSE64 will be broken until that and all the dependent mods get updated.

 

Many people use SKSE64 and I have has no issues with it ..... but updates break SKSE.

 

Bethesda could allow us to "Not Allow Updates" during the times when updates will break peoples ability to play. Then when SKSE64 and all the depend mods get updated then they can Force Updates again with the "Allow Updates" greyed out. This isn't rocket science .... it is simple courtesy....

 

and no it doesn't matter that SKS64 is still in alpha ..... everybody knows it works and works well.....

 

Thanks to the Nexus I managed to avoid the update this time ......

 

 

In case Todd or whoever is unable to log into their laptops and enable the "Allow disabling of Updates" flag fro SSE I wrote some Pseudo code for Beth

 

Properties n = int ;number of days to allow update disabling

Properties SafeUpdate int ;SKSE64 conditional

 

On Update Notification PASS from SSE QA Deptarment

external email: Send update warning email to Skyrim SSE Nexus and Bethnet

Set allowDisableUpdate to 1 for n days

Begin deployment

On Update Begin

If File scan SKSE64

Set SafeUpdate to disabled for n days

else

Initialize and Update

endif

end

end

Hi A .... The option to block updates is greyed out on my install of SSE..... If Beth doesn't control this option setting does that make them look more or less competent ....?

 

Well .... mod authors are being very quick in supporting v39 but Just Knock hasn't been updated yet so my load would be inoperable if I didn't play in Off-line mode.....

 

Why would I even want to update .... Finally after 2 years SSE runs properly ..... Who knows what this update may break ..... Beth and mod devs would have to come up with something compelling before I would voluntarily update ...... Modders fixed the wolf howl ages ago .....

 

To the guy that says SKSE64 breaks your game .... Not in my experience .... My install hasn't even burped ... For the first time since Oldrim came out I play without even thinking of ctds ....

 

 

I do see your point ..... but you yourself have described Beth releasing an update which breaks aspects of the game and then eventually fixing it....... I read it trying to figure out whether to update.......

 

It is all about cost and benefit ......... If CC can benefit modders more than the Nexus then the cost is worth the benefit. Right now it is hard to see any benefit to these updates.... and significant risk of the players time wasted troubleshooting and losing saves due to corruption.

 

And dividing the modding community .....

 

I am curious ...... objectively what benefit to players does this update have. Hearthfire is a underappreciated DLC so perhaps player made Hearthfire homes with more functionality would be nice......... but this is not stated as a purpose of this update directly.

 

 

 

 

[GrndZero]

Having trouble trying to figure out why the OP option is greyed out. When I go to the updates tab mine is able to be set to update only when I launch it. Running it through skse doesn't enable the code to update it so it seems to be working fine.

[TheWilloughbian]

Having trouble trying to figure out why the OP option is greyed out. When I go to the updates tab mine is able to be set to update only when I launch it. Running it through skse doesn't enable the code to update it so it seems to be working fine.

That's kind of the issue. Not that Bethesda updated/patched the game, but that there is no option in Steam to decline the update and still be able to play the game.

 

To get around it, you have to set C:\Program Files (x86)\Steam\steamapps\appmanifest_489830.acf to read only and set Steam to only update Skyrim when you launch it. Then you keep Steam in offline mod. But, you need to do all this before Steam finds out that there is an update, or you'll have to manually edit the appmanifest. Which isn't hard, but you do need to know what to edit.