Lmao incursion isn’t even out yet

SkyLord7000

But we already have a bug banner up for it 💀

Sime_Juric

SkyLord7000 said:

But we already have a bug banner up for it 💀

New content comes out in 24 minutes

Bendy

Hey early update bug instead of it being when active and the wondering

Drago_von_Drago

Kudos for getting the word out ahead of time. This implies they did do some live testing before turning it loose for players.

Bendy

I hope they now fix the solo event of energy harvest as apparently thats continuing when the sq goes down in a little

Kabam Jax

Yeah, it's unfortunate that we found a bug in the 11th hour.

Luckily, it's not game-breaking, but it definitely might be confusing for people, so we figured we'd rather communicate it early and try to equip people with the information they need to side-step that confusion.

SkyLord7000

Kabam Jax said:

Yeah, it's unfortunate that we found a bug in the 11th hour.

Luckily, it's not game-breaking, but it definitely might be confusing for people, so we figured we'd rather communicate it early and try to equip people with the information they need to side-step that confusion.

All good! Earlier the better!

ReignkingTW

The silver lining -- Kabam was testing!

Ashacekar

Okie, that adds up difficulty. You can't swap champs. Got it.

AverageDesi

Ashacekar said:

Okie, that adds up difficulty. You can't swap champs. Got it.

You can't swap previously swapped and used champions

Ashacekar

AverageDesi said:

Ashacekar said:

Okie, that adds up difficulty. You can't swap champs. Got it.

You can't swap previously swapped and used champions

"Previously swapped and used" term is confusing to me. Hopefully i won't need to swap. Don't want to be in the loop of death as they have stated and lose rewards. If there's bug with swapping, i m not touching swap feature.

ahmynuts

Kabam Jax said:

Yeah, it's unfortunate that we found a bug in the 11th hour.

Luckily, it's not game-breaking, but it definitely might be confusing for people, so we figured we'd rather communicate it early and try to equip people with the information they need to side-step that confusion.

I couldnt help but notice it's missing from the ever so important trello board

Wozzle007

Kabam Jax said:

Yeah, it's unfortunate that we found a bug in the 11th hour.

Luckily, it's not game-breaking, but it definitely might be confusing for people, so we figured we'd rather communicate it early and try to equip people with the information they need to side-step that confusion.

This really needs to be sent as in game message. Majority of people don’t come to the forums and neither should.

JustWantTheRewards

Ashacekar said:

AverageDesi said:

Ashacekar said:

Okie, that adds up difficulty. You can't swap champs. Got it.

You can't swap previously swapped and used champions

"Previously swapped and used" term is confusing to me. Hopefully i won't need to swap. Don't want to be in the loop of death as they have stated.

It sounds like we just can't use champions that we had previously swapped in. So if you bring Apoc just to make someone a Horseman and then swap him out, you can't swap him back in. The loop is caused by him still being an option but not allowing you to proceed unless you choose a champion you haven't already swapped out.

Unknown

This content has been removed.

Demonzfyre

SkyLord7000 said:

But we already have a bug banner up for it 💀

So you don't want them to communicate? You bash them for never testing or communicating and now you're bashing them for finding a bug during testing and communicating? Classic community forum post.

SkyLord7000

Demonzfyre said:

SkyLord7000 said:

But we already have a bug banner up for it 💀

So you don't want them to communicate? You bash them for never testing or communicating and now you're bashing them for finding a bug during testing and communicating? Classic community forum post.

If this is the only major bug this month then I think it’s fine, but I have a feeling there are going to be more unchecked if something was found the 11th hour.

HungaryHippo

This bug has been around for a while.