pathfinder supports 3 different types of maps. Systems (more) and connections (more) can be added to them. Maps are also referred to as "Chain Map" or "Chain":
Up to 5 different maps can be used simultaneously. Alliance maps require appropriate rules to be created.
Each map has a "scope" that affects how systems will be added automatically to it:
If "map tracking" is on, new systems (more)
and connections (more)
will be automatically added to the current map (more).
This can only work if your current position is known by pathfinder.
The map scope (more) defines which systems are affected.
The connection scope (more) will be auto-detected (e.g. wormhole connection).
This is achieved by calculating the jump distance between your current system and system you came from.
right click somewhere on the map to open the context menu.
Locked systems (more) can´t be selected.
The "Grid snapping" option can be activated on the "Map Menu" (). Systems will snap to a 20x20px grid. A grid overlay appears on the map.
The "Magnetizing" option can be activated on the "Map Menu" (). If active, systems effect each other while move/drag&drop and will rearrange themselves automatically on the map. This prevents system "overlapping"
The "Compact" option triggers a "compressed" map layout. Active Pilots are shown "inline" next to the name of a system.
The "Update counter" starts counting backwards during map interaction. While the counter is active, no data is pushed to server.
Once the counter hits 0, all map date will be stored and active pilots will receive the map updates.
There is no need for any safe/edit buttons.
Systems are represented by rectangle boxes on a map (more). Pilots can interact with systems like "delete systems" (more) or "move systems" (more).
Any system on a map can be set as "active" by click.
Just one system per map can have an active state.
The active system has a light yellow shadow.
Additional system information is shown below the map.
Systems can be renamed with an alias by double-click the name. System aliases are stored server side and are visible to any pilot on the map.
Any "K-space" system in "New Eden" has a fixed "Security status" between -1.0 and +1.0.
"W-space" systems always have a Security status of -1.0.
They can be distinguished into "Classes" [C1 - C6].
The label color of a system indicates the "Security Status".
| K-space | ||
| H | High security system | 1.0 - 0.5 |
| L | Low security system | 0.4 - 0.1 |
| 0.0 | Null security system | 0.0 - -1.0 |
| W-space | ||
| C1, C2 | Low class wormhole | -1.0 |
| C3, C4 | Mid class wormhole | -1.0 |
| C5, C6 | High class wormhole | -1.0 |
| W-space | ||
| C12 | Thera class wormhole | -1.0 |
| C13 | Shattered wormhole | -1.0 |
| C14 - C18 | Drifter wormhole | -1.0 |
| A-space | ||
| A | Abyss system | -1.0 |
The border color indicates the current status of a system.
The status can be changed by using the context menu (more).
Effects of wormhole systems are shown by a at the top right of a system.
If a system has active pilots, a tooltip is shown with the current number of pilots.
Systems with active pilots are bigger than empty systems and provide morermation than others.
During mouseover the () icon more detailed information is shown.
right click a system on the map to open the context menu.
Systems can be marked as Rally point.
When a new "Rally point" is set, you can optional enter a message and set various "Poke" options, in order to send notifications to other active pilots.
Slack and Email pokes require a valid map configuration (map settings dialog) before they can be used.
Waypoints can be set to systems. Waypoint options are identical to their in game options.
Any system that is not "Locked" (more) can be deleted from a map.
Connections between systems are represented by solid lines. Any connection requires two systems that are connected together.
Systems can be connected to each other by several ways.
Each connection has its own "Scope". Scopes represent connection types that exist in game.
Maps can be filtered by specific scopes (more).
The "Scope" of a connection can be changed by using the context menu of a connection (more).
Wormholes go through various mass stages over lifetime.
To reflect the mass status on map, wormholes can be flagged.
The status can be changed by using the context menu (more).
Wormhole connections have a "max jump mass". Ships whose total mass exceed this mass, can not go through the hole.
The size of a wormhole can be set by using the context menu (more).
The lifetime information of a wormhole indicates roughly what kind of time is remaining on the wormhole before it dies of natural causes.
Wormholes set to "EOL" (End Of Lifetime) can automatically be removed from the map 4h later on (check map settings).
EOL status can be set by using the context menu (more).
right click a connection on the map to open the context menu.
Wormholes can be labeled with a save mass flag.
Let your mates know about critical connections that should be mass-saved
(e.g. H security exits).
Connections can be detached by several ways.
The two endpoints of a connection support drag&drop for either twitch the connection to a a new target system or use the context menu for endpoint specific actions.
right click a connection endpoint on the map to open the context menu.
A connection endpoint (e.g. wormhole, stargate,..) can be flagged as "bubbled". Bubbled endpoints have a mark around them on map.
The "Signature table" of a system is shown below the map. Any active system (more) has its own "Signature table". Signatures found in a system can be added to the table in order to share information. The table represents a record of the current scan process of a system.
The scan "Progress bar" is a visual indicator for the scan progress of a system. You can see how many signatures are scanned already and what is left. Anytime a new signature is added to the "Signature table" the "Progress bar" will be updated automatically. The bar color indicates the progress.
The "Signature reader" functionality allows pilots to add and update multiple signatures at once. In order to copy signatures from "EVE" to pathfinder, do the following steps.
Advanced pilots can skip number 3.!
Make sure, you have the right system marked as active (more).
click the browser tab were pathfinder is open. Then press ctrl + v.
pathfinder automatically detect the data format and updates the "Signature table".
Signatures can be detached by several ways.
The concept of map sharing is pretty complex and powerful. By default all sharing options are disabled, so there is no reason to be concerned about map security.
All map types (more) can be temporary shared with allied entities e.g. for "Joint-Ops".
The map type is preserved for the period of sharing (private maps can be shared with other users, corporation maps can be shared with other corporations,..).
Do the following steps to share your map with your friend/allied corporation/allied alliance:
pathfinder comes along with several visual charts graphs. In order to provide the pilot with useful information about his environment, data visualisation is a good way to compress the amount of relevant data.
The "Route" search module is available for any active system (more). Each system jump is represented by a with the color of its "Security status" (more).
| 1-0 | 0.9 | 0.8 | 0.7 | 0.6 | 0.5 | 0.4 | 0.3 | 0.2 | 0.1 | 0.0 | -1.0 |
The "Recent activity" bar chart is available for any active system (more). The chart shows all ship kills in a system during the last 24h. If pathfinder detects recent kills (within the last hour), a small label is shown above the graph.
pathfinder supports desktop push notifications. The first time this kind of notification is send to a client, a Browser security question must be confirmed.
In order to test desktop push notifications click the "Notification test" () option in the main menu.
Events that trigger desktop notification.
pathfinder can log user statistics for each map. Activate User statistics for a map in the map settings dialog.
User statistics can be globally disabled for some map types on this installation.
In order to provide the pilot with useful information about his environment, data visualisation is a good way to compress the amount of relevant data.
Just as the "Statistics" logging (more), which is primarily useful for character comparison,
pathfinder logs a lot more useful stuff "under the hood". Some of these map specific logs can also be seen by the users.
Map specific log settings can be changed for each map individually; see map settings dialog ().
Some log methods might be globally disabled for some map types (more).
When enabled, pathfinder will write a physical log file with map related events. There is UI in the "map information" dialog available (log file viewer).
Map logs can also be send to a Slack channel. This requires a valid "WebHook" configuration for your map.
Slack´s Webhook API has bad response times, use this feature with caution! It can slow down other map updates.
Map logs can also be send to a Discord channel. This requires a valid "WebHook" configuration for your map.