**Mastery Loadouts**
Due to issues related to the release of Mastery Loadouts, the "free swap" period will be extended.
The new end date will be May 1st.
Options

AW matchmaking 2 hours early and high ground tactic unchanged….

GrubGrub Posts: 258 ★★★
in General Discussion
Kabam has some explaining to do.

Comments

  • Options
    CrusaderjrCrusaderjr Posts: 1,059 ★★★★
    high ground is 15seconds rather than 10 seconds now xD
  • Options
    KnightZeroKnightZero Posts: 1,416 ★★★★★
    Crusaderjr said:

    high ground is 15seconds rather than 10 seconds now xD

    That's for High Ground 1. High Ground 2 is still 10 seconds.
  • Options
    GrubGrub Posts: 258 ★★★
    edited November 2021
    Some alliances were switching members too before war oof.

    Talk about bad timing.

    I mean they have to scrap this war matchup and delay a week I assume?

    @Kabam Miike @Kabam Zibiit @Kabam Vydious needs some urgent attention
  • Options
    Tx_Quack_Attack6589Tx_Quack_Attack6589 Posts: 607 ★★★
    It was an hour early, if your switching members you wasted 2 weeks of off-season.
  • Options
    GrubGrub Posts: 258 ★★★
    Tx_Quack_Attack6589 said:

    It was an hour early, if your switching members you wasted 2 weeks of off-season.

    It was like 1:45 early
  • Options
    GrubGrub Posts: 258 ★★★
    Tx_Quack_Attack6589 said:

    It was an hour early, if your switching members you wasted 2 weeks of off-season.

    Not really. Aq just ended yesterday. And there was still plenty of time left to replace members.

    There’s a reason war placement / enlistment is timed and on a schedule.

    Let alone some alliances could have forgotten to enlist yet and missed it because of a kabam error. I sure would be pissed off they pulled the trigger early.

  • Options
    ItsDamienItsDamien Posts: 5,626 ★★★★★
    Grub said:

    Tx_Quack_Attack6589 said:

    It was an hour early, if your switching members you wasted 2 weeks of off-season.

    It was like 1:45 early
    Accounting for the clocks going back on Sunday for DST too?
  • Options
    GrubGrub Posts: 258 ★★★
    ItsDamien said:

    Grub said:

    Tx_Quack_Attack6589 said:

    It was an hour early, if your switching members you wasted 2 weeks of off-season.

    It was like 1:45 early
    Accounting for the clocks going back on Sunday for DST too?
    Daylight savings time is always account for and the time is fixed back to normal. The only time when it’s not is when an AQ is currently ongoing.

    Either way. It was early regardless of DST.
  • Options
    KnightZeroKnightZero Posts: 1,416 ★★★★★
    ItsDamien said:

    Grub said:

    Tx_Quack_Attack6589 said:

    It was an hour early, if your switching members you wasted 2 weeks of off-season.

    It was like 1:45 early
    Accounting for the clocks going back on Sunday for DST too?
    Yeah. Accounting for everything, war is starting 2 hrs earlier than usual.
  • Options
    Tx_Quack_Attack6589Tx_Quack_Attack6589 Posts: 607 ★★★
    Grub said:

    Tx_Quack_Attack6589 said:

    It was an hour early, if your switching members you wasted 2 weeks of off-season.

    Not really. Aq just ended yesterday. And there was still plenty of time left to replace members.

    There’s a reason war placement / enlistment is timed and on a schedule.

    Let alone some alliances could have forgotten to enlist yet and missed it because of a kabam error. I sure would be pissed off they pulled the trigger early.

    Hmmm aq cycle was 2 weeks, got it
  • Options
    KnightZeroKnightZero Posts: 1,416 ★★★★★
    Tx_Quack_Attack6589 said:

    Grub said:

    Tx_Quack_Attack6589 said:

    It was an hour early, if your switching members you wasted 2 weeks of off-season.

    Not really. Aq just ended yesterday. And there was still plenty of time left to replace members.

    There’s a reason war placement / enlistment is timed and on a schedule.

    Let alone some alliances could have forgotten to enlist yet and missed it because of a kabam error. I sure would be pissed off they pulled the trigger early.

    Hmmm aq cycle was 2 weeks, got it
    Waiting till before war start if definitely late, but you don't get new members from thin air. It takes time to find folks that fit the alliance. So it isn't hard to believe that new members joined after yesterday's AQ cycle ended. Should have joined a bit earlier yeah, but the other point you're raising is rubbish.
  • Options
    GrubGrub Posts: 258 ★★★
    KnightZero said:

    Tx_Quack_Attack6589 said:

    Grub said:

    Tx_Quack_Attack6589 said:

    It was an hour early, if your switching members you wasted 2 weeks of off-season.

    Not really. Aq just ended yesterday. And there was still plenty of time left to replace members.

    There’s a reason war placement / enlistment is timed and on a schedule.

    Let alone some alliances could have forgotten to enlist yet and missed it because of a kabam error. I sure would be pissed off they pulled the trigger early.

    Hmmm aq cycle was 2 weeks, got it
    Waiting till before war start if definitely late, but you don't get new members from thin air. It takes time to find folks that fit the alliance. So it isn't hard to believe that new members joined after yesterday's AQ cycle ended. Should have joined a bit earlier yeah, but the other point you're raising is rubbish.
    It doesn’t matter. The normal start time wasn’t adhered to.

    They penalize alliances for not enlisting on time as well. This is the same damn thing.

    Enlistment starts at 3pm PST like clockwork every damn war. There was no notice of a change.

    Every alliance is entitled to do whatever they want because it was within their allotted time for enlistment.
  • Options
    KnightZeroKnightZero Posts: 1,416 ★★★★★
    edited November 2021
    Grub said:

    KnightZero said:

    Tx_Quack_Attack6589 said:

    Grub said:

    Tx_Quack_Attack6589 said:

    It was an hour early, if your switching members you wasted 2 weeks of off-season.

    Not really. Aq just ended yesterday. And there was still plenty of time left to replace members.

    There’s a reason war placement / enlistment is timed and on a schedule.

    Let alone some alliances could have forgotten to enlist yet and missed it because of a kabam error. I sure would be pissed off they pulled the trigger early.

    Hmmm aq cycle was 2 weeks, got it
    Waiting till before war start if definitely late, but you don't get new members from thin air. It takes time to find folks that fit the alliance. So it isn't hard to believe that new members joined after yesterday's AQ cycle ended. Should have joined a bit earlier yeah, but the other point you're raising is rubbish.
    It doesn’t matter. The normal start time wasn’t adhered to.

    They penalize alliances for not enlisting on time as well. This is the same damn thing.

    Enlistment starts at 3pm PST like clockwork every damn war. There was no notice of a change.

    Every alliance is entitled to do whatever they want because it was within their allotted time for enlistment.
    Oh I agree. It is late, but as long as you do it before the allotted time, that's all that matters. If you're given a time for event start/event end and they change it, whether by 15 mins or 2 hours, it's their fault. Unless prior notice is given. Which it wasn't.
  • Options
    Wiredawg1Wiredawg1 Posts: 504 ★★★★
    Kabam Boo said:

    Hi folks, we're so sorry about the 2-hour discrepancy. We've recently had a time change in our region and it's caused some confusion with our timers. Unfortunately, in order not to impact other areas of AW, we will have to wait until next Tuesday to implement any corrections.

    As for the High Ground description, we confirm that it's purely a text issue. The team has double checked to make sure that the proper High Ground difficulty was implemented on each Map. The text issue will be fixed next Tuesday as well.

    We apologise in advance for this delay but it is in the best interest of AW for now to keep it this way until the team can safely implement any changes next Tuesday. Thank you for your patience and understanding!

    Lol you are kidding with that excuse as to why is 2 hours late? That reasoning might work if was an hour or the simple fact Mondays aw was not effected
  • Options
    Tx_Quack_Attack6589Tx_Quack_Attack6589 Posts: 607 ★★★
    Wiredawg1 said:

    Kabam Boo said:

    Hi folks, we're so sorry about the 2-hour discrepancy. We've recently had a time change in our region and it's caused some confusion with our timers. Unfortunately, in order not to impact other areas of AW, we will have to wait until next Tuesday to implement any corrections.

    As for the High Ground description, we confirm that it's purely a text issue. The team has double checked to make sure that the proper High Ground difficulty was implemented on each Map. The text issue will be fixed next Tuesday as well.

    We apologise in advance for this delay but it is in the best interest of AW for now to keep it this way until the team can safely implement any changes next Tuesday. Thank you for your patience and understanding!

    Lol you are kidding with that excuse as to why is 2 hours late? That reasoning might work if was an hour or the simple fact Mondays aw was not effected
    Mondays war placement was an hour earlier then normal so clearly it was affected just not as much
  • Options
    KnightZeroKnightZero Posts: 1,416 ★★★★★
    Tx_Quack_Attack6589 said:

    Wiredawg1 said:

    Kabam Boo said:

    Hi folks, we're so sorry about the 2-hour discrepancy. We've recently had a time change in our region and it's caused some confusion with our timers. Unfortunately, in order not to impact other areas of AW, we will have to wait until next Tuesday to implement any corrections.

    As for the High Ground description, we confirm that it's purely a text issue. The team has double checked to make sure that the proper High Ground difficulty was implemented on each Map. The text issue will be fixed next Tuesday as well.

    We apologise in advance for this delay but it is in the best interest of AW for now to keep it this way until the team can safely implement any changes next Tuesday. Thank you for your patience and understanding!

    Lol you are kidding with that excuse as to why is 2 hours late? That reasoning might work if was an hour or the simple fact Mondays aw was not effected
    Mondays war placement was an hour earlier then normal so clearly it was affected just not as much
    That should have alerted them by itself that it needed to be looked at.
    It might look fine, but planning war around work isn't easy. It's very frustrating to have these time shifts.
  • Options
    KnightZeroKnightZero Posts: 1,416 ★★★★★
    Kabam Boo said:

    Hi folks, we're so sorry about the 2-hour discrepancy. We've recently had a time change in our region and it's caused some confusion with our timers. Unfortunately, in order not to impact other areas of AW, we will have to wait until next Tuesday to implement any corrections.

    As for the High Ground description, we confirm that it's purely a text issue. The team has double checked to make sure that the proper High Ground difficulty was implemented on each Map. The text issue will be fixed next Tuesday as well.

    We apologise in advance for this delay but it is in the best interest of AW for now to keep it this way until the team can safely implement any changes next Tuesday. Thank you for your patience and understanding!

    What about AQ? Is that still scheduled as normal?
Sign In or Register to comment.