Skip to content
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

Feature movement teleport #182

Closed
wants to merge 3 commits into from

Conversation

luken
Copy link
Contributor

@luken luken commented Oct 9, 2015

This is currently stacked on top of #181, I assume #181 should be merged first...

@Gjum
Copy link
Member

Gjum commented Oct 9, 2015

I do not understand why this has to be part of movement at all. The server can send position updates all the time and we already handle them. And a teleport command interface isn't really needed IMO.

@Gjum
Copy link
Member

Gjum commented Oct 9, 2015

A teleport thing that would fit in spockbot would be the gamemode 3 teleport.

@luken
Copy link
Contributor Author

luken commented Oct 9, 2015

The time it takes to start the teleport after the command, hit the ground after a teleport is started are both non-deterministic so adding in idle delays isn't always successful at stalling long enough.

This interface allows you to tell when a teleport command had completed and the bot was in final position. This allows for more accurate debugging of pathfinding (it seems to not like it when you start the path calc still in the air).

@luken
Copy link
Contributor Author

luken commented Oct 20, 2015

Getting old. Closing. I've pulled teleport into a 'Commands' custom plugin I am using, if there is interest in having this feature included let me know and I can submit the 'Commands' plugin.

@luken luken closed this Oct 20, 2015
@luken luken deleted the feature-movement-teleport branch October 20, 2015 17:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants