Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
resurrect 1
Reloading a save prior to entering that part of the bastion is the best thing to do
setstage dunBlindCliffQST 100
Well just to be clear a death script has been writen into the save. So no, there is no console command that can complete the Quest, only move it to its last stage.
The Quest mentioned is forever borked in this save.
I've tried recycleactor (which works, but doesn't finish the quest).
I've tried resurrect 1 (but it never works, it just says "compiled script not saved", tried with the base and the ref id.
Those id's are:
00023AB0
00077C60
I've moved myself to the ref id, but nothing is there anymore.
I didn't know about the unoffical patch, so it's possible that I did the quest, didn't realise the glitch until recently, and since doing the quest installed the unoffical patch, but that should still let me setstage. That it won't disappear is bugging the hell out of me. I have spent so many hours in this game now, if I have to restart I'm going to just be frustrated.
because those that wrote the scripts didnt add every possible situation to be checked for.
what so causes a lot of broken stuff. over time.
since its missing a lot of condition checkl
and condutional memory leak issues that can ocur
due to the half complet scripts..
thats mostly the cause for broken quest and more...
then again you will never be able to have a game to forsee all conditions,
since it would cause a long check delay, if its to many conditions to be checked.
and since creation engine is written in C and C++ and partly assambler you either have:
if, else, case and catch situation
and those a have a limit of how many checks can be done.
without causing a to big of delay.
if and else is more delay causeing then catch,
but even still catch has a upper limit untill its also will cause a delay.
and those condition verification can
if there are to many conditions to be checked: so cause preformance issues.
No-one tells you before you get the game that you will inherently have bugs :( . I wouldn't even mind if I could at least put a bandaid on after, but I don't want quest objectives on there that I can't do :(
With Fallout76 Bethesda has shown its real ugly face very openly to see for everyone. I saw that face already before, but i havent thought they would be so stupid/greedy/ignorant to be so open about it lol. Well i know for sure that this company will not get ONE FCKING cent from me in the future. But i doubt that the general consumerdrone-crowd will do the same, after 2 shiny trailers all is forgotten and thiefs and liars will still have their steady income...
If next TES game is as bad as we all fear, I won't be trying it.