Forum Discussion

ensign1's avatar
8 years ago

Post combat lock.

I thought the last upgrade was supposed to take care of this? Still happening a lot in wrath 11 mostly when attacking the big alliances.....What's going on??

30 Replies

  • Can you clarify? Are you attacking 2 player bases or 2 forgotten bases?
  • 2 player bases in PvP.
    Normally after the 2 minute attack time you should get the 'locked for your alliance', but more than once in a while, I get 'post combat lock' as I would have seen it if another alli had attacked it.

    As I understand it I should be able to attack the same PvP enemy again at once after the combat timer (2 min) runs out...
  • I am informed that what you are seeing is by design. As @chertosha suggested, it part of the combatting of lockdown exploit.
  • Ok? Well might be me that's thick here, but how will that help with base-locking? it only extends the attack period with an extra 30 sec. I never tried base locking but can't really see how that would help...
    And what in that case can I do/not do to avoid getting post-combat lock?
    It can't be because I hit 2 bases at once since others get it too.
  • I can't answer these questions, but maybe on Monday @EE_Elephterion will :wink:
  • These extra seconds are added to the PCL of the attacker, making it harder to continuously cover a base with the same account. It seems you've triggered that for your attacks. How big is the difference between your Offense and the target Defense?
  • Same thing happening on tiberian 16 since years. 100% sure it's a bug. When you attack a base in pvp... normally... you have 30 seconds to prepare your next attack... And you can strike immediately... to prevent
    support weapons... But sometimes... after 2-3-4 attacks... the behavior changes and you see "post combat lock" Like if the game was thinking that you are attacking a forgotten base. So you can't strike immediateliy after the "Under attack by tou" You have to wait 30 stupid seconds... and be quick... if not... the guy can move. Here we are used to play with that bug... But because I saw a post... I decided to comment. This is totally random situation. And occurs on lvl 66 off against lvl 65 defs. Or any other off-def configuration.
  • Yes, you are punishing PvPers way too much in a game that is supposed to be a war game.

    And yeah, what difference in levels triggers this post-combat lock nonsense?
  • chertosha's avatar
    chertosha
    New Adventurer
    6 years ago
    let's start by saying that pvp-locking was the biggest problem with the game for a couple years (2016-2018) and made the game nearly unplayable
    preventing lockdown was a hard nut to crack and took several iterations
    in the first iteration of the patch it was introduced that if you attack somebody 15+ levels higher, you get those extra 30 seconds delay
    but that did not fix the problem completely because people found smart ways around it that made things even worse
    the final patch that seems to have solved the issue for most intents and purposes - was never spelled out in detail so that it is hard to figure out exactly when the extra 30 seconds happen and also hard to find a way around it
    i believe that there are two extra precautions: if you are attacked then you get preferential right to attack back for 30 seconds, and in addition your right to continue attacking is discarded seemingly randomly
    this random (or seemingly random) feature is what prevents a reliable lockdown strategy from being designed and solves most problems with lockdown pvping
    the extra 30 seconds one gets here and there is a small price to pay for solving a huge problem, imho

About Tiberium Alliances Technical Issues

Having problems running the game or a script? Get help with Command and Conquer: Tiberium Alliances with the community!1,660 PostsLatest Activity: 9 days ago