Original Post — Direct link

Previously, I reported a bug/glitch about the strange repetitive vanishing effect happening at the skirmish site for Coteaux de la Seine. In the video I provided for that report, I noted that the Heavy Calvary got stuck. What I didn’t realize then was that shooting a poison or fire arrow is what caused the Heavy Cavalry to get stuck, or rather, become disabled.

To confirm this, I engaged an independent Heavy Cavalry in Francia and was able to replicate the same outcome. Once he was hit with a poison or fire arrow... he shut down and took his due punishment.

">

For an even more interesting example, I found that the same problem applied to The Cavalier, one of the Three Nobles. This issue made killing The Cavalier really easy.
">

about 3 years ago - Ubi-Milky - Direct link
Once he was hit with a poison or fire arrow... he shut down and took his due punishment. 🤣


Hello again TheNorfolkian, thanks for reporting this!

Just to be absolutely sure, can I ask if you have any stun effects enabled on that bow at all, and can you always unintentionally stun these enemies with poison and fire arrows, no matter what bow you use?

Have you been able to test this with any melee weapons that use a poison or fire effect too, or does it only work with arrows?

about 3 years ago - Ubi-Froggard - Direct link

@thenorfolkian Thanks for the videos and information provided. I'll forward these on to the game team in the report and if they need any further information we'll get back to you here.

Edit: They'd like to know what bow you were using just in case that makes a difference?

about 3 years ago - Ubi-Froggard - Direct link

@thenorfolkian No worries, thanks for confirming. I did mention to them earlier if they can re-test on horseback as they were unable to reproduce it previously but maybe they were on foot. I'll let them know the bow doesn't make a difference for you too. Thanks again 🙂

about 3 years ago - Ubi-TheBerry - Direct link

Hey @thenorfolkian ,

Thanks for the update!

The team have found the cause and are working on a fix, which is planned for release in a future patch.

When we have the patch number / date this will be, we'll let you know here.

Thank you for your continued patience and understanding!

about 3 years ago - Ubi-Woofer - Direct link

Glad to hear you're pleased, @thenorfolkian! From what I've just read in the investigation, it looks as if trying to reproduce the bug but on horseback was successful, so it may be that the team did not attempt this initially.

We'll keep you all updated as to when the fix for this issue will be deployed, and for now, thank you for your patience! 🙂