m
→Details
(Updated with new information) |
m (→Details) |
||
| Line 28: | Line 28: | ||
== Details == | == Details == | ||
(As of 3.1, this no longer accurate. Raid indices now reorder themselves every time the raid layout changes.) | |||
Regarding the correspondance of raid indices to players: Let C be the list of players in a raid ordered by their raid index. It appears that after any series of changes is made to the raid, at the end all players from C still in the raid will retain their original ordering (even if they left and rejoined the raid), with new members existing at any index 1<i<=40. | Regarding the correspondance of raid indices to players: Let C be the list of players in a raid ordered by their raid index. It appears that after any series of changes is made to the raid, at the end all players from C still in the raid will retain their original ordering (even if they left and rejoined the raid), with new members existing at any index 1<i<=40. | ||
It also appears that your character's index will always be equal to GetNumRaidMembers() for the purposes of GetRaidRosterInfo. In other words, your character's index will always be n in a raid of size n. All other members will have indices less than n. | It also appears that your character's index will always be equal to GetNumRaidMembers() for the purposes of GetRaidRosterInfo. In other words, your character's index will always be n in a raid of size n. All other members will have indices less than n. | ||