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
A case large enough so you can adapt any GPU if upgrades, a medium CPU that allows for upgrades, and a PSU powerful enough so you can fit a dual GPU if requested later on.
Now devs changed so many things in the game while in early access but at a time where story mission jobs were already scripted, you may encounter this many times (or over budget repairs) if you build over the minimalistic way.
When those missions were scripted, it was at a time when labor + parts were only a single price, AND FURTHERMORE you were paied full amount, no matter what (yes yes, even if an OC did the trick to reach the score...).
So in older days it was only logical to build minimalistic, as you made all the money anyway, so the cheaper parts to reach request, the more money you were making.
And since, devs never really though that going back over those jobs script was a good idea...
So older players tend to still keep using the same minimalistic tactic, and never face those issues.
So in your case, if the job has no deadline, just keep it until you unlock the 2080's, and never ever build again (unless it's necessary) with the best available part on story jobs.
For RNG jobs, no issues, you can do that.
Ok, thanks. It was only a difference of like $20 vs. the minimum, but I get that not giving him the best would avoid a situation like this.
@Devs
Devs you might want to just make this mission insta-complete (the computer arrives and the objective is already green) in this situation. I'm sure that's an easier fix than trying to re-script for a bunch of variables.
Yup, I saw that. Thanks.