AutoNote

Description

Tracks the classes, roles, and specs of the members in your raid group and fills out template NSRT notes accordingly. Automatically swaps notes any time an encounter is successfully completed. Notes are updated any time changes occur in the raid (spec swaps, roster changes, etc.)

How To Use

In the notes tab, click "New Note", add a name, and select the difficulty. In the text box, place your template note for the encounter and click "Save Note". Right click the note to edit the name, activate the note, or delete the note. The first note for a boss is automatically activated. If you wish to select a different note to be used for that boss, then you will need to set it to active.

Sample tempalte which assigns the first Death Knight in the raid to use AMZ at 2:16:
time:136;ph:1;tag:Deathknight1;spellid:51052;

Use lowercase color codes to avoid any potential conflicts with tag replacement!

Available Tags

Use any of the following tags with a number to assign a raider that fits that criteria. Tags with no corresponding raid member will return N/A. In cases where multiple classes have the same spec name, the class name is appended to the spec.
E.g. Unholy1 will be replaced with the name of the first Unholy DK in the raid.

Ignoring Replacements

Occasionally some undesired text may get caught in the pattern matching. If this happens, place the text noReplace at the beginning and end of your text to force ignore any replacement.

Example:

Hiding Text

If for some godforsaken reason you need assignments to be calculated on the back-end without displaying, you can hide them by wrapping them in the hideStart and hideEnd tags.

Example:

Priority-based Assignments

Linear

Assigns raid members to each group contained within the groupStart and groupEnd tags.
Line 1 indicates how many raiders to assign to each group. You can either provide a single number or a comma-delimited list of numbers where each number corresponds to the number of raiders to assign to that group.
Line 2 is the list of tags which you would like to be assigned to each group.
Any remaining lines are considered a group where {{}} is where the assigned groups will be placed.

Example:

Alternating

Assigns raid members alternating between each group contained within the alternateGroupStart and alternateGroupEnd tags.
Line 1 indicates how many raiders to assign to each group. You can either provide a single number or a comma-delimited list of numbers where each number corresponds to the number of raiders to assign to that group.
Line 2 is the list of tags which you would like to be assigned to each group.
Any remaining lines are considered a group where {{}} is where the assigned groups will be placed.

Example:

Forced Assignments

In the previous group assigns, any tag placed within the {{}} tag will force fill that role in the tag while still counting it towards the number of players assigned to the group.

Example:

No Duplicates

When using the above group assigns, you may have multiple tags which a single raider can fit the criteria for.
E.g. a hunter may fit the tags Hunter1, Marksmanship1, and Ranged1.
Any group assigns between the noDuplicateStart and noDuplicateEnd tags will avoid assigning the same raider twice to those groups.

Example:

Group References

When using the previous group assigns, you can later reference a group assign by using the format #GroupName:PlayerTag.
The group name is determined by the text left of a colon. To reference it, make sure to remove all white space.
In addition to the typical class, spec, or role tags, you can also use a plain number to reference the nth person assigned to that group. Each tag is specific to that group, so #Left:Unholy1 refers to the first unholy in the left group

Example:

It's important to note that if you have a group such as "Group 1: Unholy1", that #Group1:Unholy1 refers to the first unholy in this group. It does NOT refer to the first unholy in raid group 1. That is referenced by "Group1_Unholy1".