-
Notifications
You must be signed in to change notification settings - Fork 53
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
Sensing position of met robots #1535
Comments
Maybe the robots that share the same ancestors are friendly? For other robots, we could have a handshake system where the robots have to mutually meet (within some timeout). A game state map of initiated handshakes in the last tick(s) could be checked when meeting robots and if the handshake is completed we would update those robots friendly set. |
In the adversarial case, I might not want the Though, perhaps there is a case for an alternate command, |
Re: limited range, see
I guess that makes sense, I'm just trying to prevent unnecessary complexity. |
Closes #1535 # Demo scripts/play.sh -i scenarios/Testing/1535-ping/1535-in-range.yaml --autoplay
There are now a lot of entity sensing commands (related: #1171), but a dearth of robot-sensing commands.
Define a new command named
ping
for obtaining relative coordinates to an already met robot (i.e., you have obtained a "reference" to that robot). This command would be enabled by atransponder
device (perhaps, required by both robots).The physical justification/rationale could be that initially meeting "face-to-face" allows exchange of "transponder codes" between friendly robots.
This may call for a new
Robot
attribute that distinguishes between robots that are "friendly" or not. Perhaps we should not be allowed togive
items to an unfriendly robot.Avoiding "instantaneous communication" loophole
This functionality should have a limited range so that information can not be leaked over great distances.
The text was updated successfully, but these errors were encountered: