Jump to content
Sign in to follow this  
Replacement

BUG: Tanker Alternate builds force Armor selections

Recommended Posts

Steps to reproduce:

1: Create a tanker, choose to start with your T2 armor power instead of T1.

2: Choose an alternate build (level 1).

3: Train up to next level.

Expected Result: Choice between T1 and T2 Armor power

 

Actual Result: T2 power is selected; T1 is grayed out.

 

Tested with: level 50 tanker.

Primary: Willpower

Secondary: Electric Melee

 

Maybe this has been a thing with alt builds forever and I'm only now finding out about it?

 

EDIT: I went to try this again with my 3rd active build and it did not occur.  It only happened when I went to Build 2.

Edited by Replacement

Share this post


Link to post
Share on other sites
2 hours ago, Replacement said:

Steps to reproduce:

1: Create a tanker, choose to start with your T2 armor power instead of T1.

2: Choose an alternate build (level 1).

3: Train up to next level.

Expected Result: Choice between T1 and T2 Armor power

 

Actual Result: T2 power is selected; T1 is grayed out.

 

Tested with: level 50 tanker.

Primary: Willpower

Secondary: Electric Melee

 

Maybe this has been a thing with alt builds forever and I'm only now finding out about it?

 

EDIT: I went to try this again with my 3rd active build and it did not occur.  It only happened when I went to Build 2.


Can you replicate this with any other armor set?


Playing CoX is it’s own reward

Share this post


Link to post
Share on other sites
On 11/8/2019 at 2:48 PM, Myrmidon said:


Can you replicate this with any other armor set?

Trying to simply replicate even the first go-round at the moment.  This time it's WP/Claws.  When I set active build to #2 or #3 and go to train up and I get this:

Build2.thumb.png.c0dafd468e80a60e573af96494d9b69c.png

 

(hey, I really like the little plus sign on attached pictures to insert into post)

 

Level 20, but only trained up to 14 on the 1st build.

 

Logging out and back in (or rather, getting booted for afk and logging back in) seems to have fixed the issue...

 

At which point, I can't even recreate the original bug.

 

All sorts of weirdness here.  Don't know what to think.

 

 

 

  • Thanks 1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×
×
  • Create New...