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
I did this with Strong and Mr. SRB man.
It would seem you're not doing it right.
The developer doesn't see this as a problem regardless.
They've stated that they do not support the usage of the console.
http://www.gamespot.com/articles/bethesda-warns-against-using-fallout-4-pc-console-/1100-6432513/
And you're using mods on top of this. How is this problem in any way related to the developer?
One thing I'll say: Never restart. You break something, there's a great chance you can fix it. Just never use "MarkForDelete" unless you know what you're doing.
Are you sure it works according to my tests setting the affinity should work fine but the cooldown protection they put in place prevents you from triggering the next peice of the dialog after one try. To be absolutly clear you can use this once but you can't keep razeing the affinity and triggering there conversations you need to wait 15 min after you trigger the dialog.
As for the developer not seeing this as a problem I don't really care how they see it. As a coder myself and as someone who did a lot of modding with BG2, Skyrim, and fallout 3, this is just bad craftminship. I know why they put in the safegard but it was implemented very poorly you need to make sure it is very compatmentalized otherwise weird stuff like this starts happening. But that's just my two sense.
Also if you check the mod it's supposed to remove the safegard but it appears to not have any effect. :(
A. It works, it worked for me and I've gone through 4 play-throughs of bug-hunting, ca_affinity has never cross my mind as remotely botched.
You must select the right npc, then either setav or modav CA_AFFINITY. Then you need to trigger an affinity changing event in-game, meaning doing something the companion hates or likes. Then the game will update the companion's dialogues to allow for the next conversation.
B. As a computer engineer myself, I don't see how a debugging menu coders wrote for their programs that's not intended for consumers require any safeguard -- if I'm testing an edge case and I want to see what event causes an error of sorts, I'd hope I wrote the debugging menu to allow for this.
B. look I'm not going to argue about this. I still think it was a oversight but It's not important.
A. So lets be clear on the goal. useing hancock as an example I want to be able to "setav CA_AFFINITY" and then take some drugs which will trigger his conversation. I want to be able to do that again and again still I reach the end of his dialog tree were he is eather 1000 or 1100 depending on if I romance or not.
Here are my resaults so far.
hancock currently = 265
step 1
1.
"setav CA_affinity" set the affinity to 500 then I take some drugs which Hancock likes. = conversation triggers
step 2
2.
"setav CA_affinity" set affinity to 750 then I take some drugs which Hancock likes. = conversation does not triggers
The reason for this is that there is cooldown when your character likes something in this case (takeing drugs). This was implemented inorder to stop players from maxing out a companions affinity right away. However because setting the affinity doesn't tricker the dialog right away it means that this cooldown is interfearing with this jarryrigged process of getting your companion to like you.
So I guess I shound't be angry at the guy that developed the cooldown system. I should be angry at the guy that added the extra veriable that said the dialog had to be triggered by a like event rather then just setting it to trigger at 250,500,750,1000. Like anyone else would have done.
The cool down for doing certain actions does exist, but you can do other things to trigger the affinity event. The cool down is not shared among different events.
For example, when I start a new game try to increase affinity, I had planned my moves so that for each companion I have a series of things to do to accelerate the process.
i.e.: I set Hancock to 250, take mentat, finish talking, then I immediately set affinity to 500 and go to Dassie, or whatever the Ghoul vendor's name is, talk to her about being a ghoul, be nice etc. etc., instantly trigger another affinity event. I then go to Hotel Rexford, talk to Vault-tec Rep, be nice and invite to Sanctuary, instant affinity event.
Then I go to Mccready, do the thing for one of the guys in Hotel Rexford, ask for more money, now go do his personal quest, come back, take hancock and take drug again. Done. And everything in Good Neighbor is good for McCready because I can ask for money and he likes the action.
The cool down is there for a reason: so the obvious act to repeating the same easily doable action cannot be abused to make certain companions easy to please.
Quick Saving / Quick Loading instantly resets the cooldown.
Mentat -> Quicksave/Quickload -> Mentat -> Quicksave/Quickload -> Repeat 20x FTW.
To cut a long story short, I got impatient so skipped the 750 and changed it straight to 1000.
One Quicksave, Quickload, just to be save, and doing something he likes later boom last talk and Romance check.
So don't get a talk at one of those points try skipping it.
Hope this helps.
Oh and before I forget The 250, 500, 750 and 1000 worked without problems with Piper, Cait, Codsworth and Preston, so it should work with the others to which I haven't mentioned.
With Danse I did the 250, 500 and 750 checks so far no probs, haven't done much BoS quests.