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
This seems like an annoying visual-only? bug, so best to report it on the official forums:
https://bethesda.net/community/category/59/pc
Because it happened multiple times before when i clicked a bit slower, from the first one it went up to 200 already (would still be going up) when the caps from the second one started arriving and it reset it again. Also the average caps for the whole quest were 300 and definitely not 100 per guy or even less (once clicked on 4 such sources and only got 300 in the end, clicked in other rooms once or twice and got 300 for each click without resetting.
ALSO!: if you slow down the video to 0.25 speed you can very well see after the second guys caps finished at 300 the third guys caps reset the whole thing.
Thanks but i'm not sure if it's visual only, in other quest levels where the average was definitely 300 caps per guy killed/additional sources i had the same problem and it was very obvious since i got 300 caps per guy when slow clicking and only about 100 per guy when fastclicking, all in all 1000 or 300 caps makes a big difference. I think it's more than a visual bug. Watch the video on 0.25 speed, after the 2nd guy the reset for the 3rd guys caps arriving is very obvious.
Thanks for the heads up, i wonder if i've been losing out on some caps myself.
Thank you, i hope more people can test it/look out for it, i mean it might very well be i'm wrong or it's just happening for me.