DBI.PathFinder 0.8.4

There is a newer version of this package available.
See the version list below for details.
dotnet add package DBI.PathFinder --version 0.8.4                
NuGet\Install-Package DBI.PathFinder -Version 0.8.4                
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="DBI.PathFinder" Version="0.8.4" />                
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add DBI.PathFinder --version 0.8.4                
#r "nuget: DBI.PathFinder, 0.8.4"                
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install DBI.PathFinder as a Cake Addin
#addin nuget:?package=DBI.PathFinder&version=0.8.4

// Install DBI.PathFinder as a Cake Tool
#tool nuget:?package=DBI.PathFinder&version=0.8.4                

Dofus Batteries Included - Path Finder

Implementation of the dofus path finder used by the DBI.Api project. This project is also published as a standalone nuget package so that it can be reused without the need of calling the web API.

Getting started

The tricky part about paths

The first issue is that map coordinates are not unique: there are multiple worlds, and multiple levels in a given world, so multiple maps can have the same map coordinates. The unique identifier of a map is its mapId. The path finder cannot use the coordinates, it needs the map ID.

The second issue is that the maps of the game can be subdivided into multiple zones dissociated zones: the player cannot go from one zone to the other without going through other maps. For example, this is a common occurence in the wabbit islands.
It means that we need to know for each map the available zones and how they connect with the zones of the adjacent maps, and we need to know the zones from which we start and end the path searches.

Thankfully, the creators of the game have included what they call a worldgraph in the game files. It is extracted by the DDC project and saved to a file called world-graph.
The graph is defined as follows:

  • Nodes are zones of a map. Most maps have only one zone but maps that have multiple dissociated areas have multiple zones. <details> <summary> <b>Example</b>: the data center API exposes an endpoint to get all the nodes of a given map, <a href="https://api.dofusbatteriesincluded.fr/swagger/index.html?urls.primaryName=data-center#/World%20-%20Maps/Maps_GetNodesInMap">try it!</a> </summary>

    Request

    curl -X 'GET' \
      'https://api.dofusbatteriesincluded.fr/data-center/versions/latest/world/maps/106693122/nodes' \
      -H 'accept: application/json'
    

    Response

    [
      {
        "id": 7911,
        "mapId": 106693122,
        "zoneId": 2
      },
      {
        "id": 10115,
        "mapId": 106693122,
        "zoneId": 1
      }
    ]
    

    </details>

  • Edges are connections between two maps. Edges have transitions: they are all the ways a player can move from the first map to the second. <details> <summary> <b>Example</b>: the data center API exposes an endpoint to get all the edges from a given map (<a href="https://api.dofusbatteriesincluded.fr/swagger/index.html?urls.primaryName=data-center#/World%20-%20Maps/Maps_GetTransitionsFromMap">try it!</a>) or to a given map (<a href="https://api.dofusbatteriesincluded.fr/swagger/index.html?urls.primaryName=data-center#/World%20-%20Maps/Maps_GetTransitionsToMap">try it!</a>) </summary>

    Request

    curl -X 'GET' \
    'https://api.dofusbatteriesincluded.fr/data-center/versions/latest/world/maps/99615238/transitions/outgoing' \
    -H 'accept: application/json'
    

    Response

    [
      {
        "$type": "scroll",
        "direction": "west",
        "from": {
          "id": 5239,
          "mapId": 99615238,
          "zoneId": 1
        },
        "to": {
          "id": 5240,
          "mapId": 99614726,
          "zoneId": 1
        }
      },
      {
        "$type": "scroll",
        "direction": "south",
        "from": {
          "id": 5239,
          "mapId": 99615238,
          "zoneId": 1
        },
        "to": {
          "id": 6586,
          "mapId": 99615239,
          "zoneId": 1
        }
      }
    ]
    

    </details>

The only missing piece is how to find the nodes of the graph that correspond to the start and end map of a path search. The data is located in the cells of the maps, that are also extracted by the DDC project and saved to a file called maps.
Each cell has a linkedZone field that is a 2-bytes value, the first byte is the zoneId.

Note: the fact that zoneId is the first byte of linkedZone is a guess, it seems to be the case but I have no guarantees.

<details> <summary> <b>Example</b>: the data center API exposes an endpoint to get all the cells of a given map, <a href="https://api.dofusbatteriesincluded.fr/swagger/index.html?urls.primaryName=data-center#/World%20-%20Maps/Maps_GetMapCells">try it!</a> </summary>

Request

curl -X 'GET' \
  'https://api.dofusbatteriesincluded.fr/data-center/versions/latest/world/maps/106693122/cells' \
  -H 'accept: application/json'

Response

[
  {
    "mapId": 106693122,
    "cellNumber": 0,
    "floor": 0,
    "moveZone": 0,
    "linkedZone": 0,
    "speed": 0,
    "los": true,
    "visible": false,
    "nonWalkableDuringFight": false,
    "nonWalkableDuringRp": false,
    "havenbagCell": false
  },
  ...,
  {
    "mapId": 106693122,
    "cellNumber": 155,
    "floor": 0,
    "moveZone": 0,
    "linkedZone": 32,
    "speed": 0,
    "los": true,
    "visible": false,
    "nonWalkableDuringFight": true,
    "nonWalkableDuringRp": false,
    "havenbagCell": false
  },
  ...,
  {
    "mapId": 106693122,
    "cellNumber": 264,
    "floor": 0,
    "moveZone": 0,
    "linkedZone": 17,
    "speed": 0,
    "los": true,
    "visible": false,
    "nonWalkableDuringFight": false,
    "nonWalkableDuringRp": false,
    "havenbagCell": false
  },
  ...
]

</details>

How to search for a path

The first step is to retrieve the game data. The easiest way is to download it from the DDC repository releases. That data can then be used to instantiate the NodeFinder and the PathFinder.

IWorldDataProvider worldData = await WorldDataBuilder.FromDdcGithubRepository().BuildAsync();
NodeFinder nodeFinder = new NodeFinder(worldData);
PathFinder pathFinder = new PathFinder(worldData);

The path finder requires the start and end node in the graph to search for a path between them. The node finder is used to find the start and end node. There are multiple ways to look for them:

  • FindNodeById, from the nodeId: the easiest for the node finder, it is the unique identifier of a node. This shifts the burden of finding the right node to the caller of the API. <details> <summary> <b>Example</b> </summary>

    Code

    RawWorldGraphNode? nodes = nodeFinder.FindNodeById(7911);
    

    Result

    [
      {
        "id": 7911,
        "mapId": 106693122,
        "zoneId": 2
      }
    ]
    

    </details>

  • FindNodeByMap, from the mapId and cellNumber: the second-best option because it always leads to a unique node. The node finder can extract the nodes in the map and the zoneId of the cell, using both these information it can find a unique node. <details> <summary> <b>Example</b> </summary>

    Code

    RawWorldGraphNode? nodes = nodeFinder.FindNodeByMap(106693122, 425);
    

    Result

    [
      {
        "id": 10115,
        "mapId": 106693122,
        "zoneId": 1
      }
    ]
    

    </details>

  • FindNodeByMap, from the mapId alone: there might be multiple nodes in a map, but usually there is only one. <details> <summary> <b>Example</b> </summary>

    Code

    IEnumerable<RawWorldGraphNode> nodes = nodeFinder.FindNodesByMap(106693122);
    

    Result

    [
      {
        "id": 7911,
        "mapId": 106693122,
        "zoneId": 2
      },
      {
        "id": 10115,
        "mapId": 106693122,
        "zoneId": 1
      }
    ]
    

    </details>

  • FindNodeAtPosition from the map coordinates: the node finder can extract all the maps at those coordinates, and all the nodes in those maps. There are high changes that multiple nodes match the coordinates. <details> <summary> <b>Example</b> </summary>

    Code

    IEnumerable<RawWorldGraphNode> nodes = nodeFinder.FindNodesAtPosition(new Position(26, -9));
    

    Result

    [
      {
        "id": 10112,
        "mapId": 99615745,
        "zoneId": 1
      },
      {
        "id": 7911,
        "mapId": 106693122,
        "zoneId": 2
      },
      {
        "id": 10115,
        "mapId": 106693122,
        "zoneId": 1
      }
    ]
    

    </details>

Using the results, we can then use the path finder to find a path between two nodes.

<details> <summary> <b>Example</b>: in this example we provide both the map ids and the cell numbers, there is only one candidate for the start and end node </summary>

Code

RawWorldGraphNode fromNode = nodeFinder.FindNodeByMap(75497730, 425) ?? throw new InvalidOperationException("From position not found");
RawWorldGraphNode toNode = nodeFinder.FindNodeByMap(75498242, 430) ?? throw new InvalidOperationException("To position not found");
Path? path = pathFinder.GetShortestPath(fromNode, toNode);

Result

{
  "from": {
    "mapPosition": {
      "x": -20,
      "y": -5
    },
    "nodeId": 5609,
    "mapId": 75497730,
    "zoneId": 1
  },
  "to": {
    "mapPosition": {
      "x": -20,
      "y": -5
    },
    "nodeId": 1667,
    "mapId": 75498242,
    "zoneId": 1
  },
  "steps": [
    {
      "node": {
        "mapPosition": {
          "x": -20,
          "y": -5
        },
        "nodeId": 5609,
        "mapId": 75497730,
        "zoneId": 1
      },
      "transition": {
        "type": "scroll",
        "direction": "north"
      }
    },
    {
      "node": {
        "mapPosition": {
          "x": -20,
          "y": -6
        },
        "nodeId": 7076,
        "mapId": 75497731,
        "zoneId": 1
      },
      "transition": {
        "type": "scroll",
        "direction": "south"
      }
    },
    {
      "node": {
        "mapPosition": {
          "x": -20,
          "y": -5
        },
        "nodeId": 7095,
        "mapId": 75497730,
        "zoneId": 2
      },
      "transition": {
        "type": "scroll",
        "direction": "east"
      }
    }
  ]
}

</details>

Features

Caching

The FromDdcGithubReleases builder supports caching to avoid requesting data from GitHub every time. Call the .UseCache(cacheProvider) to enable caching. There is a RawDataCacheProviderOnDisk that is available out of the box:

<b>Example</b>

IWorldDataProvider worldData = await WorldDataBuilder.FromDdcGithubReleases().UseCache(new RawDataCacheProviderOnDisk("./cache/")).BuildAsync();

Alternatively, you can provide your own implementation of IRawDataCacheProvider.

Forks

By default, the FromDdcGithubReleases builder reads data from the releases of the original Dofus-Batteries-Included/DDC repository. Call the UseFork("some-other/repository") to use the releases of another repository.

<b>Example</b>

IWorldDataProvider worldData = await WorldDataBuilder.FromDdcGithubReleases().UseFork("some-other/repository").BuildAsync();

Advanced usage

Finally, for more control about where the data comes from and how it is used, the FromRawData builder that asks for the data in the format that is exposed by the DDC project.

<b>Example</b>

RawWorldGraph rawWorldGraph = ...
IReadOnlyCollection<RawMap> rawMaps = ...
IReadOnlyCollection<RawMapPositions> rawMapPositions = ...
IWorldDataProvider worldData = WorldDataBuilder.FromRawData(rawWorldGraph, rawMaps, rawMapPositions).Build();
Product Compatible and additional computed target framework versions.
.NET net5.0 was computed.  net5.0-windows was computed.  net6.0 was computed.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 was computed.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 was computed.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
.NET Core netcoreapp3.0 was computed.  netcoreapp3.1 was computed. 
.NET Standard netstandard2.1 is compatible. 
MonoAndroid monoandroid was computed. 
MonoMac monomac was computed. 
MonoTouch monotouch was computed. 
Tizen tizen60 was computed. 
Xamarin.iOS xamarinios was computed. 
Xamarin.Mac xamarinmac was computed. 
Xamarin.TVOS xamarintvos was computed. 
Xamarin.WatchOS xamarinwatchos was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
0.8.5 93 10/14/2024
0.8.4 89 10/14/2024
0.8.3 79 10/14/2024
0.8.2 88 10/14/2024
0.8.1 82 10/14/2024