Yes the platoons were filled. I was able to do it with no problem in P2. We don’t Star this territory in that phase so then when P3 rolled around and I went it no rocket droid.
Oh wait so looks like a temporary work around is to put it on auto. The computer will deploy the rocket droid and then go back off auto and you can play it with him. I was going to auto just because I know with out the droid I can’t beat it. But then he appeared when the computer did its thing.
Yes the platoons were filled. I was able to do it with no problem in P2. We don’t Star this territory in that phase so then when P3 rolled around and I went it no rocket droid.
Interesting, would strongly suggest opening a bug report then. I know there was an issue with this mission's requirements that required a client restart yesterday, so there might be something lingering.
Oh wait so looks like a temporary work around is to put it on auto. The computer will deploy the rocket droid and then go back off auto and you can play it with him. I was going to auto just because I know with out the droid I can’t beat it. But then he appeared when the computer did its thing.
Extra interesting with this additional info, must be some leftover UI issues with that mission from the update.
Yes the platoons were filled. I was able to do it with no problem in P2. We don’t Star this territory in that phase so then when P3 rolled around and I went it no rocket droid.
Interesting, would strongly suggest opening a bug report then. I know there was an issue with this mission's requirements that required a client restart yesterday, so there might be something lingering.
Oh wait so looks like a temporary work around is to put it on auto. The computer will deploy the rocket droid and then go back off auto and you can play it with him. I was going to auto just because I know with out the droid I can’t beat it. But then he appeared when the computer did its thing.
Extra interesting with this additional info, must be some leftover UI issues with that mission from the update.
I would definitely agree. I’m going to send in a bug report still.
Replies
When I did the mission there were no issues with calling in the droid, but that was right away in Phase 2.
You're probably right, but it wouldn't suprise if a hotfix for a bug created a new bug.
Interesting, would strongly suggest opening a bug report then. I know there was an issue with this mission's requirements that required a client restart yesterday, so there might be something lingering.
Extra interesting with this additional info, must be some leftover UI issues with that mission from the update.
I would definitely agree. I’m going to send in a bug report still.
Ally Code: 189-995-319
also, please report to Answers HQ. I pinged them but its helpful to have those posts and the information they collect there.
Thank you.