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
What example do you have of it exposing enemy positions? Are you referring how it gives new buildings a bright blue color that be seen very easily?
Blueprints to block AI is an issue and a possible fix I think would be to allow sight through anything that isn't fully built. Could be something
10 bmats for bad placement isn't that punishing. I'd be happy if it were 1. it has to be something.
So if you start trying to build some foxholes and the enemy kept blowing your defenses before you could even finish, you'll be sending more bmats down the drain from just taking the risk of building to defend. I think that's a little too punishing for defending. Even just one, that's still one less bmat that could have finished a wall or be used to block a sandbag with, kidding.
I still think just making the blueprint seethrough and no collision until at least one bmat is put into it would fix a lot of the problems with blueprints.
Yes? It sounds good but I'm trying to think of how that could be a bad situation. No idea at the moment.
Could you explain what you mean by "Expose enemy positions"?
So trying to push defenses into an area can be very hard when enemy can see you building on the other side of the wall and just chuck grenades at you.
Making blueprints visible only to the team building them would help with that most likely, but that's unfair to the defending team (if you're building you SHOULD be vulnerable to some extent). Maybe reduce the radius that blueprints are visible? I don't know how that could work though.
Now can someone clarify the whole exploit part? I've seen groups of players that will actively knock out a defense network then build up a sandbag infront of the concrete pillboxes as a cheap way to knock them out versus spending 5 HE grenades to pop it.
the exploit part is.... you can place a blueprint from range infront of a defensive structure preventing it from firing. then run in and do one or two hits with the hammer and it stays there. if anyone thinks that is not an exploit they are delusional.
the only way to combat this is with gunnests as they seem to be able to throw a grenade, but foxholes, pilboxes and sunken pillboxes are susceptible to this behaviour. Some people do however place a sandbag out of range of the grenade but within range of the gun to allow them to get close enough to use things like rpg for a quick way to destroy a line of defence. once the blueprint is placed you are safe to stand behind it. you can even go to the extent and place a foxhole or pillbox infront of a defence built it out and then jump in with enough HE to destroy the defence in front without harm.
If i see my team doing it I tell them off, if i see the enemy doing it I tell them off. If they dont stop i will report them.
No defence is safe from Smoke + HE and satchels. why do people chose to exploit if this is the case?