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 entirely breaks a feature of the game and I'm not long off refunding a few copies from me and friends.
Been waiting over a month since purchase and enemies still do this: https://www.youtube.com/watch?v=THV20sH34fI
Please fix next patch or we're all refunding. (probably)
Very disappointing communication and update frequency for a game not sold as Early Access.
I have i5-4690 and I haven't noticed any improvements. Although for me it wasn't that bad, on CP E1M9 (Castle) it still takes about 5 seconds to save.
I think you meant precached.
yes please fix the respawning, it makes co-op so different when bullets are kinda useless, you start looking more for things to destroy the bodies, iam not sure about the old blood but i think burning deaths should stop spawning to make the aersol and other weapons more useful when respawns are on.
Bloated Butchers still have poor AI and low aggression compared to other versions of Blood. They don't launch their projectile attacks nearly as much as they should, and will sometimes even wander off away from the player.
I've had both these issues since the launch of Blood Fresh Supply.
Running this beta version of the gog version btw.
Saving is as slow as it was in 1.9.6.
Edit: (Both quicksave and normal saves)
Edit 2: to be clear, saving worked fine and quick for me in the launch version.
Hello, thanks for letting us know about this issue. It has been fixed and will be in the next BETA update.