Tsuey / L4D2-Community-Update

Help us shape the potential future of L4D2 vanilla.
69 stars 22 forks source link

[c1m3] Ai Survivor Bot Nav bug #104

Open CootieDwagon opened 2 years ago

CootieDwagon commented 2 years ago

when you have an ALL ai bot survivor team on c1m3_mall, after they trigger the panic event, the bots, not matter what, will ALWAYS gather here and get stuck, as well as continue to jump off and get incapped. this was tested on versus as you can see, but i also tested this in none versus mode and the same issue still happens.

I've no idea why they just gather here, is there a ladder? this was tested in vanilla and the bots gathered here to die. i also tested this with a plugin that allows bots to actually turn off the alarm, and they STILL get stuck here

https://steamcommunity.com/sharedfiles/filedetails/?id=2625041261

Nesciuse commented 2 years ago

It seems team with only survivor bots ignores nav blockers and just tries to use the escape_route. Could possibly be fixed by adjusting the nav blockers on the escalator to have affectsflow keyvalue changed to 1 and other things accordingly not to break flow.

CootieDwagon commented 2 years ago

Yeah it seems they try to walk up an escalator that is not there

On Sun., Oct. 10, 2021, 9:50 p.m. Nesciuse, @.***> wrote:

It seems only survivor bot team ignores nav blockers and just tries to use the escape_route. Could possibly fixed by adjusting the nav blockers on the escalator to have affectsflow change to 1 and other things accordingly not to break flow.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Tsuey/L4D2-Community-Update/issues/104#issuecomment-939634209, or unsubscribe https://github.com/notifications/unsubscribe-auth/AUA5SZXDMF2VWPMTRIFCL73UGJGHTANCNFSM5FW7BWDA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

maxim-fedotov-1997 commented 1 year ago

So, year and 4 months later, I have only one small "logical" question regarding this issue... Surely it's not that hard to add the "affectsflow 1" keyvalue to the parts of navmesh on that problematic escalator? Just wondering. It is a wonder that first fork (past the fallen over door dropdown) actually can re-route escape_route where it needs to go to. But then, I suppose it's much more impactful to the progression than a mere "escalator here or there" in bounds of just one small room.

alexiscoutinho commented 1 year ago

and other things accordingly not to break flow.

@Nesciuse What other things? In my quick test, just setting affectsFlow seemed to solve the issue.

Nesciuse commented 1 year ago

"just setting affectsFlow" where ? There are 4 possible escalator positions and you want pure bot team to path correctly for all combinations. Current logic is that nav areas on the escalators are initially blocked and later when escalator spawns it's unblocked. So just setting affectsFlow on each would mean no ecsape route can generate. That's why I said "and other things accordingly" because it requires changing the logic a little more than just adding affectsFlow.