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 like the Ball Lightning gun too, but not in survival mode. Enemies get too strong too fast in that mode to make the Ball Lightning Gun a viable option.
and then there's that (what I think is a) Glitch where if you pick it up, no more guns spawn in anymore until the next game. I don't know why it happens exclusively with the Ball Lightning Gun, it just does. Also the gun tends to spawn in my path and I end up teleporting into it at random, effectivly resulting in my prompt death afterwards.
That's why I want the Gun Locking feature in Survival mode. So that I can run around and focus on killing and evading enemies and not have to dodge into a gun because it's in the safest route.
Yes I was surprised when I first did it, I noticed how a Padlock appeared on the gun icon, and then I suddenly couldn't pick up any new guns. Very useful feature for when a rare gun appears and you get it and don't want to lose it by accident. Like the Revolver, that gun is overkill especially when you upgrade your firepower by even just a little bit.
I made sure that check box was checked. The gun locking does work in normal stages, but not in survival. That's what the original post is about.
Yes I'm running windows.
Also, the problem recently fixed. I don't know how, I changed nothing, but I reflexivly tapped the Gun Lock button in one match and it started to work again.
There's something fishy going on there, and seems like the problem is not as obvious as it might first seem. I've had very similar report from another user before, and it also got fixed by itself. We'll keep an eye out for that.