File structure based TACO pathing generation tool for Guild Wars 2.

Download the latest Marker Pack

Download Latest Marker Pack

Features

• Janthir Lowlands

1. Warclaw Caches
2. Buzzy Treetops Jumping Puzzle
3. Vale Brazier Jumping Puzzle
4. Hidden Achievments

• Janthir Syntri

1. Warclaw Caches
2. Major Kodan Caches
3. Charted Titan Ore Gather Nodes
4. Rotten Titan Amber Gather Nodes

• Mistburned Barrens

1. Warclaw Caches [In progress]
2. Ruins caches [In progress]
3. Gather nodes [Heatstone, Obsidian]
4. Event/Achievment locations

Building

Requires GO Version 1.21 or higher

1. https://go.dev/doc/install

Building the default marker pack from scratch

1. go build
2. ./gw2_markers_gen -n ShellshotMarkerPack
3. copy build/ShellshotMarkerPack.zip to your blish/taco marker pack directory (Typically C:\Users\{user}\Documents\Guild Wars 2\addons\blishhud\markers)

Build your own marker pack

1. Build the package generator: go build
2. Create a marker pack directory XXXMarkerPack
3. Add your catagories directory. XXXMarkerPack/categories
4. Define categories using Directory Structure. Example: XXXMarkerPack/categories/Janthir/Chests generates the Category: Janthir.Chests
5. Any edge category requiring configuration (including icons), may be defined using a .cat file instead
6. Add your maps directory. XXXMarkerPack/<group>/maps
7. Add a map you intend to add markers for. Example: XXXMarkerPack/maps/Janthir/JanthirSyntri
8. Create mapinfo.txt in your map directory containing the map id. EX: id=1554 (Can be easily found using the "Marker Pack Assistant" module from blish)
9. Create any number of .poi and .trail files containing marker location information. (any sub directory structure may be used)
10. Generate your package zip file: ./gw2_markers_gen -n XXXMarkerPack

Appendix

Directory Structure

maps directory

• Location for storing map information
• Every directory 2 levels deep under the maps directory MUST definte a map [see description below]

map directory

• No Directory structure is required
• The root or subdirectory MAY contain any number of .poi files
• The root or subdirectory MAY contain any number of .trail files
• MUST contain a mapinfo.txt file defining the mapid.
• MAY contain a barriers.txt file for trail creation. (defines regions path generation is unable to cross)
• MAY contain a paths.txt file for trail creation (defining a list of paths/shortcuts. Typically these are bouncing mushrooms or ways to bypass barriers)
• MAY contain a waypoins.txt file for trail creation (used to generate starting location)

categories directory

• Location for storing category definitions
• Directory structure determines category name.
• Directories MAY contain .cat files for defining attributes
• EX: categories/Janthir/Chests/MajorCaches.cat generates the Category: Janthir.Chests.MajorCaches
• Display Names will be generated from directory names (spaces will be added When casing alternates)

assets directory

• No Directory structure is required
• General location for storing assets (images/binary trail data)
• No verification takes place
• Compiled assets are placed in this directory [See compiled_assets for more information]

compiled_assets directory

• No Directory structure is required
• All files in any subdirectory of type .atrl or .rtrl will be compiled
• Location for storing trail definition files that will be compiled to .trl files
• Assets compiled from this directory will be stored in the assets directory
• EX: compiled_assets/mytrails/trail1.rtrl will be compiled to assets/mytrails/trail1.trl

User directories

• All files/directories inside your marker pack root directory will be zipped into the output path file.
• This can be used to add any custom data required

File Extensions

.cat file format

• Every line defines a key/value pair describing category attributes. (See https://www.gw2taco.com/2016/01/how-to-create-your-own-marker-pack.html for a list of valid attributes)
• Key/Value MUST be separated by the = sign
• All non Key/Value pair lines will be skipped

.poi file format

• Line 1 MUST reference a marker category present in your category directory. EX: category=ShellshotMarkerPack.Janthir.GatherNodes.ChargedOre
• Every subsequent line references a single marker
• Every marker line is defined as a list of Key/Value pairs
• Value pairs MUST be seperated by the space character
• Key/Value MUST be separated by the = sign
• Every marker line MUST contain X,Y,Z position information (as copied using the "Marker Pack Assistant" module from blish)
• Every marker line MAY overwrite marker attributes
• Every marker line MAY overwrite the mapId property controlling the map the marker applies to
• Every marker line MAY contain a tag property. Used for identifying the POI during trail generation.
• Every marker line MAY contain a parent property. Used for indicating ownership tag during trail generation. (A parent must be visited before any children)
• Every marker line MAY contain a cost property. This value may be negative for adding value, or positive for decreasing. This value is used during path generation: Negative cost paths are disallowed.
• Example Line: xpos="-290.0943" ypos="32.79265" zpos="-283.0596" Behavior="0"

.trail file format

• Line 1 MUST reference a marker category present in your category directory. EX: category=ShellshotMarkerPack.Janthir.GatherNodes.ChargedOre
• Every subsequent line references a single marker
• Every marker line is defined as a list of Key/Value pairs
• Value pairs MUST be seperated by the space character
• Key/Value MUST be separated by the = sign
• Every marker line MUST contain the trailData key pointing to a .trl file. (See https://www.gw2taco.com/2016/01/how-to-create-your-own-marker-pack.html for trail creation)
• Every marker line MAY overwrite marker attributes
• Example Line: trailData="assets/trails/janthir_lowlands/honeybey_jp.trl" color="ffffffff"

.rtrl file format

• File specifies a list of POIs that should be visisted in order
• Path starts from the first POI in the file
• POIs in the file will be visisted in order
• All Lines MUST be a list of Key/Value Pairs seperated by the space character
• Key/Values MUST be seperated by the = sign
• Line 1 MUST contain the mapid key (and other keys will be ignored)
• Subsequent lines MUST contain X,Y,Z position information (as copied using the "Marker Pack Assistant" module from blish)
• All Other Keys are ignored
• Lines without position information are skipped

.atrl file format

• File species auto-generation of an optimized path starting from any waypoint, and visisting all nodes
• order of POIs in the trail is NOT guaranteed in the final path
• Every line defines a key/value pair describing map information
• Key/Value MUST be separated by the = sign
• The file MUST contain the map key
• the file MUST contain a file key
• the file MAY contain a fromWaypoint key indicating path generation should start from a map waypoint
• the file MAY contain the start_xpos, start_ypox and start_zpos keys. If all are specified, and have valid information, path generation will start from those coordinates rather than using waypoints
• All Other Keys are ignored
• Lines without position information are skipped
• The map value MUST match the name of a directory in your maps folder
• The file value MUST be a valid path relative to the map directory defined in the map field

.trl file format

• File definition used by GW2 Pathing.
• Contains encoded mapid, and points location along a trail

File Definitions

mapinfo.txt format

• Every line defines a key/value pair describing map information
• Key/Value MUST be separated by the = sign
• The file MUST contain the id key
• The file MAY contain the max_value key. Used for defining resource limitations during path generation.
• All other information in the file will be skipped

barriers.txt format

• All Lines MUST be a list of Key/Value Pairs seperated by the space character
• Value pairs MUST be seperated by the space character
• Key/Value MUST be separated by the = sign
• Every line MUST contain X,Y,Z position information (as copied using the "Marker Pack Assistant" module from blish)
• Every line MUST contain a name key
• All lines sharing the same name key will be used as a pair with order defined by file order.
• Lines may contain the Type key
• Example Barrier definition:

xpos="100" ypos="0" zpos="50" name="barrier-1"
xpos="100" ypos="0" zpos="50" name="barrier-1"
xpos="10" ypos="0" zpos="0" name="barrier-1" type="downonly"
xpos="10" ypos="0" zpos="100" name="barrier-1" type="downonly"

• Each Barrier MUST contain exactly 2 entries
• Invalid lines will be skipped
• Invalid barriers will be ignored, and generate warnings

paths.txt format

• All Lines MUST be a list of Key/Value Pairs seperated by the space character
• Value pairs MUST be seperated by the space character
• Key/Value MUST be separated by the = sign
• Every line MUST contain X,Y,Z position information (as copied using the "Marker Pack Assistant" module from blish)
• Every line MUST contain a name key
• All lines sharing the same name key will be used as a pair with order defined by file order.
• Lines may contain the Type key
• Example path definition:

xpos="100" ypos="0" zpos="0" name="path-1"
xpos="100" ypos="0" zpos="10" name="path-1"
xpos="100" ypos="0" zpos="30" name="path-1"
xpos="200" ypos="0" zpos="50" name="path-2" type="mushroom"
xpos="200" ypos="0" zpos="100" name="path-2" type="mushroom"

• Invalid lines will be skipped
• Invalid paths will be ignored

waypoints.txt format

• All Lines MUST be a list of Key/Value Pairs seperated by the space character
• Value pairs MUST be seperated by the space character
• Key/Value MUST be separated by the = sign
• Every line MUST contain X,Y,Z position information (as copied using the "Marker Pack Assistant" module from blish)
• All other keys will be ignored

Path Types

• mushroom defines a one-way bouncing musroom path from begining to landing location
• oneway defines a path that can only be taken in 1 direction. (typically if it requires gliding/falling)

Barrier Types

• downonly defines a barrier you can decend from, but not climb. (used for steep cliffs)