Additions:
- Data inside the notes and credit fields may span multiple lines, even within each instrument for multiplayer paths. Although every instrument must start on a new line.
Deletions:
- Data inside the notes and credit fields may span multiple lines, even within each instrument for multiplayer paths.
Additions:
- Data inside the notes and credit fields may span multiple lines, even within each instrument for multiplayer paths.
Deletions:
- notes and credit fields may span multiple lines, even within each instrument for multiplayer paths.
Additions:
- Paths for various levels of squeezing only if the actual structure of the path changes (i.e. the shorthand notation). Differences in note and tick squeezes do not constitute a new path entry.
- notes and credit fields may span multiple lines, even within each instrument for multiplayer paths.
Deletions:
- Paths for various levels of squeezing only if the actual structure of the path changes (i.e. the shorthand notation). Differences in note and tick squeezes ONLY do not constitute a new path entry.
Additions:
- If you notice an already submitted path is either outdated, incorrect, or missing information you can provide, feel free to modify the existing data.
Deletions:
- If you notice an already submitted path is either outdated, incorrect, or missing information you can add, feel free to modify the existing data.
Additions:
Tips & Advice
Deletions:
Notes and Tips
Note that multiple paths may be added to a single page through multiple actions. Unless each one serves a unique purpose, however, it's generally best to update/replace an existing path with latest and best-known information. Unique purposes might include: .
Additions:
- Valid purposes for multiple paths include:
Deletions:
- Valid purposes for multiple paths may include:
Additions:
- Don't add multiple variations of paths intended for the same purpose - instead, edit and revise existing ones to purge old/outdated information as better paths are discovered.
Deletions:
- Don't add multiple variations of paths intended for the same purpose. Instead edit and revise existing ones to purge old/outdated information as better paths are discovered.
Additions:
Note that multiple paths may be added to a single page through multiple actions. Unless each one serves a unique purpose, however, it's generally best to update/replace an existing path with latest and best-known information. Unique purposes might include: .
- Multiple paths may be added to a single page through multiple {{path}} actions.
- Don't add multiple variations of paths intended for the same purpose. Instead edit and revise existing ones to purge old/outdated information as better paths are discovered.
- Valid purposes for multiple paths may include:
- Different consoles/platforms if there's a path difference
- Paths for various levels of squeezing only if the actual structure of the path changes (i.e. the shorthand notation). Differences in note and tick squeezes ONLY do not constitute a new path entry.
- Paths that assume you miss certain difficult parts, or with a particular goal in mind (e.g. "five star guides", etc.)
Additions:
For example, "Activate on 2nd G after the break" is much better than "Activate 3rd beat of measure 127".
Deletions:
For example, "Activate on 2nd B after the break" is much better than "Activate 3rd beat of measure 127".
Additions:
If you come across a common notation that's not listed, please add a comment on that page letting us know what is missing.
Additions:
Additions:
- Shorthand notation and path notes should avoid references that require a visual to understand. The purpose of shorthand is for users to memorize and execute paths without having to figure out what it means with a chart.
For example, "Activate on 2nd B after the break" is much better than "Activate 3rd beat of measure 127".
- If you notice an already submitted path is either outdated, incorrect, or missing information you can add, feel free to modify the existing data.
Deletions:
- Shorthand notation and path notes should avoid references that require a visual to understand. The purpose of shorthand is for users to memorize and execute paths without having to figure out what it means with a chart. For example, "Activate on 2nd B after the break" is much better than "Activate 3rd beat of measure 127".
Additions:
Optimal path for: GH2 - Yes We Can - Solo - Expert, based on this path:
http://www.slowhero.com/gh2-ps2/expert/yeswecan.upper-bound.best.png∞
label="optimal"
score="282700"
short="2-2-3"
image="
http://www.bradleyzoo.com/GuitarHero/gh2-ps2/expert/yeswecan.upper-bound.best.png∞"
notes="1st Activation: 2nd single O after 4th RO chord
2nd Activation: 1st single O after YO holds
Last Activation: Extremely difficult squeeze"
credit="debr"
Generates the following:
Optimal Path
Est. Score: 282,700
Instrument |
Path Short |
Notes |
Credit |
Guitar |
2-2-3 |
1st Activation: 2nd single O after 4th RO chord 2nd Activation: 1st single O after YO holds Last Activation: Extremely difficult squeeze |
debr |
|
Learning short Path Notations
One of the most common things provided to describe paths is shorthand notation. If not familiar, these can often be quite confusing at a glance. The community has adopted standards for each instrument to concisely and accurately portray a path in a short line of text.
Notes and Tips
- Shorthand notation and path notes should avoid references that require a visual to understand. The purpose of shorthand is for users to memorize and execute paths without having to figure out what it means with a chart. For example, "Activate on 2nd B after the break" is much better than "Activate 3rd beat of measure 127".
- Everything is optional. So provide as much as you can, but don't hesitate to contribute if you don't have much to add.
- If the label field is omitted, it will default to "optimal".
Deletions:
Learning "Short" Path Notations
One of the most common things provided to describe paths is short-hand notation. If not familiar, these can often be quite confusing at a glance. The community has adopted standards for each instrument to concisely and accurately portray a path in a short line of text.
Additions:
Using the Path action: {{path}}
Deletions:
Using the Path action
Additions:
- Navigate to the song page where you wish to contribute a path.
Deletions:
- Navigate to the song page you wish to contribute to.
Additions:
If you have a path to contribute to the wiki, here's how you can help:
Deletions:
If you have a path to add to contribute to the wiki, here's how you can help:
Additions:
How To Add Paths
Overview
If you have a path to add to contribute to the wiki, here's how you can help:
- Upgrade or apply for access to edit song pages.
- Navigate to the song page you wish to contribute to.
- Either click "Edit" at the bottom of the page, or double-click somewhere inside the page.
- Change the existing {{path}} action or add a new {{path}} entry to the page.
- Click "Store" to save the changes.
Using the Path action
Here's some templates and examples for specifying paths on both single player and multiplayer pages. All parameters are optional, so you may include as much or as little information you have to describe a path.
To use the following templates:
- Copy and paste a template below into the appropriate song page.
- Remove any lines or parameters that don't apply (i.e instruments that don't exist, fields you can't provide, etc.).
- Replace the blank lines with data similar to that shown in the examples below.
Single Player
The following applies to single player pages such as solo guitar, bass, drums, or vocals.
Template
{{path
label="_____"
score="_____"
short="_____"
image="_____"
video="_____"
notes="_____"
credit="_____"
}}
Examples
Multiplayer
The following applies to all multiplayer pages referring to more than one instrument.
Template
{{path
label="_____"
score="_____"
short="
guitar: _____
bass: _____
drums: _____
vocals:_____
"
image="
guitar: _____
bass: _____
drums: _____
vocals: _____
overall: _____
"
video="
guitar: _____
bass: _____
drums: _____
vocals: _____
overall: _____
"
notes="
guitar: _____
bass: _____
drums: _____
vocals: _____
overall: _____
"
credit="
guitar: _____
bass: _____
drums: _____
vocals: _____
overall: _____
"}}
Examples
Learning "Short" Path Notations
One of the most common things provided to describe paths is short-hand notation. If not familiar, these can often be quite confusing at a glance. The community has adopted standards for each instrument to concisely and accurately portray a path in a short line of text.
To better understand these notations yourself, and to ensure you're contributing paths in a way others will be able to understand best, please refer to the
PathNotations page.
Deletions:
.
.