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

Implement pathfinding for duality #4

Closed
Barsonax opened this issue Jan 29, 2017 · 1 comment
Closed

Implement pathfinding for duality #4

Barsonax opened this issue Jan 29, 2017 · 1 comment
Assignees

Comments

@Barsonax
Copy link
Owner

Barsonax commented Jan 29, 2017

Summary

This applies to the Pathfindax.Duality project.

In order to integrate pathfindax with duality it needs to be easily accessible from other components. The following steps have to be done to achieve this:

  • Create a PathfinderComponent component which implements a IPathfinder interface. The completed paths should be checked in the before update of the core plugin.
  • Create a PathfinderManagerComponent will find all IPathfinderComponents in the scene and store this in a public static property.
  • Since the way the pathfinder is accessed might be changed in the future and static properties do not give you this flexibily there needs to be a layer of abstraction between the static property. A Proxy class which sits between these systems is suited for this.

Analysis

This makes it possible for other classes to easily request a path.

@Barsonax Barsonax added this to the Basic functionality milestone Jan 29, 2017
@Barsonax Barsonax self-assigned this Jan 29, 2017
@Barsonax Barsonax changed the title Implement a pathfind component for duality Implement a pathfinding for duality Jan 29, 2017
@Barsonax Barsonax changed the title Implement a pathfinding for duality Implement pathfinding for duality Jan 29, 2017
@Barsonax
Copy link
Owner Author

Implemented on develop

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant