Ao Jun, constant stealth and dragon breath while walking??

Ok I know the screenshots look like he was landing but I'm telling you, he never took flight. 

This happened to me today, but it was a Nightingale, not an Ao Jun. So, less of an issue (no weapons), but it was stealthed and hovering about a foot above the ground, dancing around on a beacon. Had to ditch taser bot (no lock) for a flamer in order to kill it.

Report it to Pixo. They can add it to the list of bugs they're working on...

Just speculation: perhaps this is to do with the disguise unit?

Maybe someone here with a disguise unit and an Ao Jun could try out using them together and try activating stealth at different points to see if they can replicate and report this.

I have seen a Leech with disguise unit and it seemed to have the bubble. My thinking though is that there may be some unusual (buggy) interaction between the disguise unit and a stealth based bot like Ao Jun. Perhaps if the Ao Jun goes into stealth and is attacked while in stealth enough to trigger the disguise unit that somehow they go into double stealth and don't come out of it again when landed. IDK just speculation at this point.

The old cycle the router to get stuck in stealth bug. Stealth bot pilots are the worst. A lot of them intentionally lag to make their stealth last longer by appearing to hover in stealth to the other players or to lag teleport across the sky in an Ao Jun making them near impossible be to hit even with Quantum Radar.

Do you have ANY evidence for this, or are you just making stuff up again?

On what?  Both were openly discussed and commonly reported in the Specter era.  It was common practice to internationally lag to get your Specter's stealth jump to last longer.  There were tons and tons of reports of this from players that would jump at the same time as a red specter, the read one would float in the air making the blue player land and end stealth 1st then kill the blue player before its stealth wore off.  International lagging was confirmed in these thread as a tactic that was employed by people actually doing it  There was also the common tactic of cycling the wifi connection or router during a stealth jump to get the Specter to get stuck in permanent stealth.  There were numerous examples of this being wide spread and patches had to be put out to stop it.  I see the intentional lagging with Ao Jun all the time.  The bot will hover in the air in stealth before landing and will lag teleport across the sky making it difficult to hit while it has no problems taking out bots withe dual Avengers and built in auto flame thrower.  The bot benifits heavily from a little bit of lag and we KNOW this tactic has been employed on purpose in the past.     

     

The getting a bot stuck in stealth mods happened on more than one occasion. Pix would fix it with a patch but then reintroduce the same problem in a later update and players would exploit it again. I believe it was acidently discovered by players messing with their connection to produce slight lag. We had confirmation of intentional lag either on the forum or somewhere else of a player stating that this was common practice and talked about in their discord.

If the stay in stealth exploit really was back I would think we would see it more frequently than the handful of times it has been reported here with Ao Jun. It possible that it is back and Ao Jun pilots are unable to expoit it as efficiently as the old Specter pilots or that is it much more difficult to reproduce with Ao Jun.

I reported a player doing this. Video is on YouTube.

Full stealth and flame ability while walking around till death. He did same thing with second Jun. No flight, just immediate stealth on the ground.

This is one of MANY known bugs that have been reported to Pix. This is kind of similar to the old bug where Inky would get caught on something and end up staying in infinite stealth. The lack of give a 「dookie」 with this update from Pix is starteling...nearly everything is bugged somehow.

If it becomes rampant then they will hot fix it like the last 2 or 3 times.

Yes, so it’s a fault that affects all bots, so there’s no reason to single out non-legacy bots as other posters have done.

It’s your choice to run incapable legacy bots and hide in lower leagues. Singling out and criticising particular meta or old meta bots because they are susceptible to a game wide bug, whereas your old junk isn’t, just reveals your self interest and undermines your credibility.