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

[#396] Entities: Pathfinding [$50] #503

Open
gdude2002 opened this issue Jun 24, 2017 · 5 comments
Open

[#396] Entities: Pathfinding [$50] #503

gdude2002 opened this issue Jun 24, 2017 · 5 comments

Comments

@gdude2002
Copy link
Contributor

gdude2002 commented Jun 24, 2017

Bountysource bounty

This issue is part of this story, Completing entities in Glowstone (#396). To make the work easier and bounties fairer, we've split it into multiple issues.

Anyone can participate in the completion of this issue, which will be a major turning point in the development and the possible use-cases for Glowstone as a Minecraft server alternative.


Before getting started! If you are unfamiliar with Glowstone, please remember that Glowstone is a complete rewrite of the Minecraft vanilla server, aimed to be a better alternative to other software like Spigot. You are by no means allowed to push code to this repository based on Mojang's own platform (whether it be Forge, MCP, decompiled binaries, etc.) Doing so will cause in the rejection of your Pull Request. You are allowed to use other resources like the numerous wikis that exist on the Internet (Minecraft Wiki, wiki.vg, etc.) as well as trial-and-error.


Pathfinding

Glowstone currently lacks a 3D pathfinding tool for entities to reach a specific target. Keep in mind that dozens of entities may be running pathfinding actions simultaneously, which may hinder the performance on the server. This pathfinding algorithm would need to be able to not affect performance too much, while being a rough equivalent to the Vanilla functionality.

  • Decide on an appropriate pathing algorithm, which may be A* (currently used in Vanilla) or one of its many derivatives. Based on my personal work and research on this, A* seems much more efficient and appropriate for 2D environments, but less so with layered 3D environments. The decided algorithm would have to be implemented with the concept of a 3D voxel world in mind (not a closed environment!)

There is a $50 open bounty on this issue. Add to the bounty at Bountysource.

@Salil999
Copy link

Salil999 commented Jan 2, 2018

Interested in working on this. If A* is used, what heuristic are we looking at? Manhattan distance is what I'm presuming...

@aramperes
Copy link
Member

I would think that Euclidean distance heuristic would be used. Even though the world is just a set of cubes, mobs (entities subject to Pathfinding) don't have to follow the grid. They can go from A to B diagonally.

@smartboyathome
Copy link
Contributor

One thing to check as you work on this is the affects of precision on whatever algorithm you use as you get close to the default Minecraft world border at 30,000,000 blocks. While in Vanilla this doesn't happen at 30,000,000 blocks, if you mod it to remove this limit, you'll see entities start to fall into loose lines. Youtuber AntVenom has done some good exploration around this: https://www.youtube.com/watch?v=uHWoB9GCSYk

@Salil999
Copy link

Salil999 commented Jan 3, 2018

Got something in there: #799

Although I don't know how to remove all the odd formatting errors that are on CircleCI.

@gdude2002 gdude2002 changed the title [#396] Entities: Pathfinding [#396] Entities: Pathfinding [$50] Sep 15, 2019
@mastercoms
Copy link
Member

@creatorfromhell You can probably propose #924 as a resolution for this issue, for the bounty.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Bounties
Backlog
2017Q4
Backlog
Development

No branches or pull requests

5 participants