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 is all for the blade itself, the projectiles the blade fires I am less sure on, but I believe damage, size, and fate of fire affect them as well at least.
Phantom Strike and Outrage Module are unhelpful, because if all of your blades are on screen, the "ignores your rate of fire" clause doesn't matter: you have no blades to fire.
Burst Fire is also Very Bad for the same reason.
Bladed are standard constructs, not basic, and shields definitely work on them. I think you might be thinking of mines.
edit: i made a mistake when typing abd fixed it
Aside from your poor wording, I double checked. Blades are Standard (not Basic) and should be affected by Shielded Constructs per reading.
That said, I have a vague memory that they're actually excluded from it because Reasons (also Bastion, despite being an Advanced construct, does not get a benefit from Shielded Constructs, because then Bastion would get its own Bastion).
there's even an achievement that you get for shielded blade, lmao.