[RG] Initial bot implementation with configs #1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
AlanSpatial
reviewed
Mar 15, 2024
| } | ||
|
|
||
| private bool TryFindNewTarget(bool resetVelocity) | ||
| private bool TryFindNewTarget(bool resetVelocity, bool targetClosest = false) |
There was a problem hiding this comment.
Deterministically choosing what player the Bot/Ball Targets
Theres a few ways you could go about this,
- Currently the owner of the ball is fully in control of it for the whole game. When a bot blocks a ball it could takeover ownership of the ball and dictate the new target from there.
This was actually my original plan. Each time the ball targets
youor a localbot, you takeover the ball so that you sim it locally. Remove any network lag etc, but I felt it made the code a little messy and obviously vulnerable so for now we have single ownership on the ball.
- A bot could pre-decide if it will block and who it will target and sync this state. Then when the ball hits the bot the master-client it will read the state and make it happen.
- You can message between networked clients with RPCs using our networking service.
2 is probably this simplest to add to the current code.
There was a problem hiding this comment.
Thanks Alan! I'll think about this and see what changes can be made 👍
AlanSpatial
approved these changes
Mar 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Video demonstration: https://www.loom.com/share/408d1d185704492ca24fc4206445a6e6?sid=5c105e98-c980-4e9f-80b7-ef7c55047b38
Hey Spatial team! We finished up the initial bot discussed last week, and it’s working great! As you’ll see in the video, the bot is configured to move randomly during a random interval of time, keep a minimum distance from other players/bots, miss the ball with a certain probability, and target the nearest player with a certain probability. All of these configs are adjustable via a config pane in the editor.
The only roadblock we encountered here was that the logic for which player to target existed in the BallControl.cs file, rather than the Bot.cs file. Ideally, all bot logic would exist in the bot file, but if the ball and bot are not owned by the same client, it was unclear how to have a bot alert or tell the ball which player to target. Is there a “messaging” system that allows synced objects to communicate? TLDR; the original code treats the ball almost as its own character that decides who to target, but it may be beneficial to have the bots decide that for themselves? If not, we can leave it as is and have target selection not be part of the bot logic.