Start with events and a clear sequence
Add an event from the event palette, place it in the graph and connect it to a following event. Give the event a useful description and time. The destination must occur at the same time or later; a path that moves backwards in time is not a valid sequence.
Select a branch to edit its probability, condition and source. Keep a condition concrete enough for another reader to recognize, such as the information you would check before taking that branch. Use the application's validation messages to correct inconsistent input. If a percentage is your estimate, leave that uncertainty explicit in the description or source rather than presenting it as measured data.
Use the view that matches the task
Graph, map and split views let you focus on the sequence or its location. The initial graph view prioritizes readable events. Fit all is available when you need to inspect the whole structure, but a large graph may require zooming back in to read individual labels. Select an event or branch to open its details; closing the details panel does not delete anything.
Treat selecting, pinning and binding as different actions
Selecting an existing map object identifies a place. Creating a persistent pin records a custom location. Binding explicitly associates a selected place with an event. You can explore the map or create a pin without first selecting an event.
The map uses game coordinates separately from the graph's layout positions. Moving a graph node rearranges the diagram; it does not move its map location. Nearby map targets can snap to known presets, while the target list and expanded map help distinguish close objects. Layer controls reduce clutter and change which preset targets can be selected by snapping.
Preset camp, tower, objective and brush positions are approximate planning references. Brush presets are points, not exact collision or vision boundaries. Give a custom pin a name when helpful; an unnamed pin is also valid and gets a coordinate label for display. Dragging or editing a custom pin can update events bound to that pin, so check the intended bindings before moving it.
Keep a portable copy of your work
Local drafts autosave in the current browser. Export JSON for a portable backup, especially before replacing work with an imported file or a cloud version. Browser storage can be cleared or unavailable; local autosave is not a substitute for an exported copy. Imported documents are validated before they replace the current document.
Undo and redo apply to document changes, including map bindings and custom pins. Google sign-in enables private cloud storage within the current service limits. If another save has changed the cloud revision, resolve the conflict deliberately rather than assuming your local state is the newest version. A cloud project is private to its account; Google sign-in does not link a Riot account.
Check the patch label when returning to an old plan
The supported game patch and the Data Dragon asset version are displayed separately. An older saved event can retain a coordinate that differs from a newer preset. Review the location and bind it explicitly if you intend to adopt the current preset; do not assume that an old plan has been silently updated. LoL PATH is an independent planning tool and is not endorsed by Riot Games.