-
Notifications
You must be signed in to change notification settings - Fork 20
Bot CTG gameplay behaviors #1600
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
| // Intended for use by ghost carrier team, to emulate a team that knows where enemies are likely to ambush | ||
| // Compensates for bots' lack of meta knowledge by making them prefer routes not reserved by enemies | ||
| // Adheres to cheat against bots but not against humans philosophy by not considering human players' positions | ||
| cost += CNEOBotPathReservations()->GetPredictedFriendlyPathCount(area->GetID(), GetEnemyTeam(m_me->GetTeamNumber())) * neo_bot_path_reservation_penalty.GetFloat() * 2; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is why I changed the SAFEST_ROUTE parameters for other path calculations not related to the ghost. There wasn't any existing handling with this case beyond some stubs related to combat areas, so this was the cleanest way I could think of for choosing paths as a ghoster team.
| m_isGoalCharger = m_healthKit->ClassMatches( "*charger*" ); | ||
|
|
||
| if (!CNEOBotPathCompute(me, m_path, m_healthKit->WorldSpaceCenter(), SAFEST_ROUTE)) | ||
| if (!CNEOBotPathCompute(me, m_path, m_healthKit->WorldSpaceCenter(), DEFAULT_ROUTE)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See neo_bot_path_cost.cpp for why these route type changes.
21a43d6 to
1d25c37
Compare
Description
Bot behaviors for playing CTG mode.
Toolchain