-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
#44459 make disabling a monster an activity with variable duration #44670
Conversation
f65dee6
to
7e98071
Compare
f246390
to
34e89f3
Compare
34e89f3
to
e7d49e9
Compare
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.
There are some merge conflicts with present master
branch.
@Autoquark are you still working on this? |
Hi, I had this ready to merge for a while but no one hit the button so it's become out of date. I could fix the conflicts but I don't know what the chances of it actually getting merged are? |
As far as I know, the only barrier to this being merged is it having conflicts and the mergers reviewing it. |
Co-authored-by: Binrui Dong <[email protected]>
Cleared some merge conflicts, need to review carefully that I didn't break something. |
Yep I mangled the merge dangit. Working on a fix now. |
…duration (CleverRaven#44670) * CleverRaven#44459 disabling a robot is an activity with variable duration Co-authored-by: Binrui Dong <[email protected]> Co-authored-by: Kevin Granade <[email protected]>
* origin/master: Rebalance bionic, fix some weird stats (CleverRaven#46212) CleverRaven#44459 make disabling a monster an activity with variable duration (CleverRaven#44670)
Did you test if Hub01s Iron Safari mission is still completable with this change? |
Summary
Balance "Disabling is now an activity that takes variable time depending on TODO"
Purpose of change
Fixes #44459
Describe the solution
Adds a new activity, ACT_DISABLE, for disabling/reprogramming a robot. Activity is disabled if the bot becomes an invalid target (e.g. hostile bot recovers from stunning) or if it moves. To prevent friendly bots from moving, added a new status worked_on which is applied during the activity and prevents them from moving.
The time to disable a robot in moves is (2000 / (electronics + mechanics)).
Describe alternatives you've considered
Testing
Tested disabling both a nursebot and disabling/reprogramming a manhack (manhacks have special reprogramming options). Tested with a friendly bot and a stunned bot, verifying that the activity is interrupted on a stunned bot when it recovers and that a friendly bot does not move during the activity.
Additional context
Consultation Request: I need suggestions for how the time for the disable activity should be calculated. Any comments on the implementation are also welcome.
Edit: I have gone with the above formula for now, suggestions from more experienced players are still welcome.