Vairelome wrote: For what it's worth, BP's brand new yellow is bugged...sort of like Patch was bugged when he was first introduced. The in-game description should delete the final word "instead" and replace with "as well." Oh, and the numbers are 175/260, not 175/250, so yeah...if you've got 12 TU banked, 9 yellow gives you +1305 in strikes, not +750.
locked wrote: Edit: hmm... Just got 3 strike tiles, which would be correct. Maybe I had bias first time?
Justdangit wrote: Also got 6 strike tile. It also doesnt consume the TUAP. Not sure if either factor are working as intended. As far as i know D3 everything is buggy and everything is working as intended until they change it(even then...).
Mondo wrote: I also decided to try this out myself and I only got 3x224 (my BP is not 166) with 9Y and 12 TUAP. I managed to pull this off twice during my match and I only got 3 strike tiles each time.
ironsmudgie wrote: Mondo wrote: I also decided to try this out myself and I only got 3x224 (my BP is not 166) with 9Y and 12 TUAP. I managed to pull this off twice during my match and I only got 3 strike tiles each time. I wonder if it only bugs if you have EXACTLY 12 TUAP. In the pictures above the one with only 3 tiles had 13 TUAP and the one with 6 tiles hqd exactly 12 TUAP.
onBattlePlan() { reduceYellowAp(9); battlePlanAnimation(); if(teamup_AP < = 12) { place_normal_strike_tiles(); } if(teamup_AP > = 12) { place_op_strike_tiles(); } }
eidehua wrote: I guess it's coded like this:onBattlePlan() { reduceYellowAp(9); battlePlanAnimation(); if(teamup_AP < = 12) { place_normal_strike_tiles(); } if(teamup_AP > = 12) { place_op_strike_tiles(); } } I actually can't think of an if/else that would cause this issue