Guild Launch News
SNEAK PEAK: Version 3.6 - Major Raid Attendance Improvements
We plan to release Guild Launch Version 3.6 on Thursday if all the testing goes well. This version contains the usual bug fixes and tweaks but also contains a major set of improvements to attendance tracking in Rapid Raid. We are adding the following:
1. The CT_RaidTracker mod is getting a new slash (/rt ...) command: /rt addattendance. This will import as an event called "Attendance". It is identical in all respects to the /rt addwipe command except it is more descriptive of what you are doing and if you are using to track attendance it wont require editing the event.
2. Every Event type on the Manage Event Type list can now be configured as to whether it contributes to attendance calculations. This would allow you to turn off attendance contribution for wipes, bonuses, penalty events, etc. and only track attendance events for attendance, etc. This sounds simple but it is key functionality to provide the power and flexibility we envision for our attendance tracking.
3. The Raid Details page now has a "Attendance by Event" link. This link goes to a page that lists each event in a raid and the attendees for each event. It also contains an edit button if a change needs to be made to the event.
4. We are adding the ability to "Clone" an event. On the raid details page you will have an option to clone an event as another event type. This would let you do some actions that could take a long time otherwise very quickly. For instance, if you want to award a bonus for attending an entire raid you could clone the last boss kill event as a bonus event and in two clicks you would have a new event with all the same attendees as the event you cloned. Items are not cloned, only attendees. You have the option of overriding the default target event value or using the default.
5. We call this "Cummulative Attendance". We are adding the ability to create an event in two clicks has every attendee in the raid, regardless of event, as an attendee. This will primarily allow people who want any attendee of a raid to get an attendance bonus to do this very quickly.
What does all of this do?
All of these features, and existing ones, work together to provide attendance tracking that is unparalleled in any existing DKP system that we know of. Both from a tracking standpoint and an ease of use standpoint. We will be providing advanced documentation when we release the functionality to ensure that people know how to use it.
For instance, if you want to do raid based attendance you can do the following:
1. Create a "Raid Attendance" event.
2. Mark it as the only event that contributes to attendance.
3. When a raid is complete add a "Cummulative Attendance" event for the raid of the "Raid Attendance" type.
Now you have raid based attendance on the Members page, and it's only a little bit of one time setup and 2 extra clicks per raid.
But, let say you want to do more complex attendance. Lets say you want to count the first and last boss of every instance for attendance. You would:
1. Once the boss events are in the system mark the first and last from each instance as contributing to attendance.
2. Do nothing more
Now your attendance will reflect the first and last bosses. So a person who always bails before the last boss, will get lower attendance percentages then a person who attends the full raid.
And, if you want the "Quick and Dirty" Attendance then do the following:
1. Mark only the first boss from each insatnce as contributing to Attendance.
2. Run the raids and if a person attends the first boss kill, they get attendance.
Easy and low maintenance.
These features, together, as a group add alot of power to our attendance tracking and a ton of flexibility and we're looking forward to seeing what people come up with.
-Stephen
1. The CT_RaidTracker mod is getting a new slash (/rt ...) command: /rt addattendance. This will import as an event called "Attendance". It is identical in all respects to the /rt addwipe command except it is more descriptive of what you are doing and if you are using to track attendance it wont require editing the event.
2. Every Event type on the Manage Event Type list can now be configured as to whether it contributes to attendance calculations. This would allow you to turn off attendance contribution for wipes, bonuses, penalty events, etc. and only track attendance events for attendance, etc. This sounds simple but it is key functionality to provide the power and flexibility we envision for our attendance tracking.
3. The Raid Details page now has a "Attendance by Event" link. This link goes to a page that lists each event in a raid and the attendees for each event. It also contains an edit button if a change needs to be made to the event.
4. We are adding the ability to "Clone" an event. On the raid details page you will have an option to clone an event as another event type. This would let you do some actions that could take a long time otherwise very quickly. For instance, if you want to award a bonus for attending an entire raid you could clone the last boss kill event as a bonus event and in two clicks you would have a new event with all the same attendees as the event you cloned. Items are not cloned, only attendees. You have the option of overriding the default target event value or using the default.
5. We call this "Cummulative Attendance". We are adding the ability to create an event in two clicks has every attendee in the raid, regardless of event, as an attendee. This will primarily allow people who want any attendee of a raid to get an attendance bonus to do this very quickly.
What does all of this do?
All of these features, and existing ones, work together to provide attendance tracking that is unparalleled in any existing DKP system that we know of. Both from a tracking standpoint and an ease of use standpoint. We will be providing advanced documentation when we release the functionality to ensure that people know how to use it.
For instance, if you want to do raid based attendance you can do the following:
1. Create a "Raid Attendance" event.
2. Mark it as the only event that contributes to attendance.
3. When a raid is complete add a "Cummulative Attendance" event for the raid of the "Raid Attendance" type.
Now you have raid based attendance on the Members page, and it's only a little bit of one time setup and 2 extra clicks per raid.
But, let say you want to do more complex attendance. Lets say you want to count the first and last boss of every instance for attendance. You would:
1. Once the boss events are in the system mark the first and last from each instance as contributing to attendance.
2. Do nothing more
Now your attendance will reflect the first and last bosses. So a person who always bails before the last boss, will get lower attendance percentages then a person who attends the full raid.
And, if you want the "Quick and Dirty" Attendance then do the following:
1. Mark only the first boss from each insatnce as contributing to Attendance.
2. Run the raids and if a person attends the first boss kill, they get attendance.
Easy and low maintenance.
These features, together, as a group add alot of power to our attendance tracking and a ton of flexibility and we're looking forward to seeing what people come up with.
-Stephen
Last edited by GL_Support on Mon Feb 18, 2008 9:58 am; edited 1 time in total
Still no way to view / edit the events in a particular raid from the individual raider perspective?
or is this what I was looking for?:
or is this what I was looking for?:
Quote:
3. The Raid Details page now has a "Attendance by Event" link. This link goes to a page that lists each event in a raid and the attendees for each event. It also contains an edit button if a change needs to be made to the event.
Oberan wrote:
Still no way to view / edit the events in a particular raid from the individual raider perspective?
or is this what I was looking for?:
This will accomplish what you want. Instead of looking at an indiviudal raider and checking the events, you can scan the individual events for the raider. It will address the needs you've expressed in the past in a slightly different way.
Essentially, if someone says "I was there for the whole raid on Friday and don't have full credit" you can quickly find out which event they are missing from.
The other thing this view gives you using the event perspective instead of the individual raider perspective is a quick overview of the per person/per event attendance. So you get a 1000ft. view easily.
-Stephen
or is this what I was looking for?:
Quote:
3. The Raid Details page now has a "Attendance by Event" link. This link goes to a page that lists each event in a raid and the attendees for each event. It also contains an edit button if a change needs to be made to the event.
This will accomplish what you want. Instead of looking at an indiviudal raider and checking the events, you can scan the individual events for the raider. It will address the needs you've expressed in the past in a slightly different way.
Essentially, if someone says "I was there for the whole raid on Friday and don't have full credit" you can quickly find out which event they are missing from.
The other thing this view gives you using the event perspective instead of the individual raider perspective is a quick overview of the per person/per event attendance. So you get a 1000ft. view easily.
-Stephen
GL_Support wrote:
Stephen, could I get this version of the mod, so I can work with you to add the listme changes, and hopefully the epgp pricing? I would really love to see those features implemented, and since you pushed off the release date, I want to work on those changes this weekend.
1. The CT_RaidTracker mod is getting a new slash (/rt ...) command: /rt addattendance. This will import as an event called "Attendance". It is identical in all respects to the /rt addwipe command except it is more descriptive of what you are doing and if you are using to track attendance it wont require editing the event.
-Stephen
-Stephen
Stephen, could I get this version of the mod, so I can work with you to add the listme changes, and hopefully the epgp pricing? I would really love to see those features implemented, and since you pushed off the release date, I want to work on those changes this weekend.
Here is the 3.6 version with the listme feature, still working on the EGPG costs feature.
http://pf.guildlaunch.com/guild/library/19337/CT_RaidTracker.3.6.with_listme.zip
http://pf.guildlaunch.com/guild/library/19337/CT_RaidTracker.3.6.with_listme.zip
Ok, here is the costs version, if you have it set to ask for costs AND auto set ep gp costs, whenever the edit costs windows are shown, it will auto populate the input text box with the correct epgp cost. If you right click an item in the raid tracker window, and edit the costs, and auto set costs are turned on, it will default to the standard epgp cost.
http://pf.guildlaunch.com/guild/library/19337/CT_RaidTracker3.6-costsNlistmes.zip
New option:
Edit Cost window with cost pre-populated:
http://pf.guildlaunch.com/guild/library/19337/CT_RaidTracker3.6-costsNlistmes.zip
New option:
Edit Cost window with cost pre-populated:
How the "listme" feature works:
Whenever a raider is sitting, for them to get credit in RT, they either need to be in the raid, or manually joined using the /rt join <PlayerName> functionality.
As we allow our players to do whatever they wish to do while wait listed, we have to re-join them to the raid after they leave the raid. I added the listme feature to do nothing more than automate the /rt join functionality.
Pros:
1) the person running RT does not need to do manual /rt joins when a player logs on and wants to get wait listed. This can suck during a boss fight.
2) It puts a time stamp in the players note so you can see who is currently wait listed, and what time they sent the listme. You can use this as a pseudo wait list to see whos available.
Cons:
Your player base have to become adjusted to using it.
Caveats of use:
1) They have to be OUT of the raid before sending the "listme"
2) Each and every time they leave the raid, they have to resend to the person running RT, a tell of "listme"
3) The listme tell HAS to come from the main or the person who wants to be in the raid, not his alt, or friends. The mod reads the name of the person sending the tell, to determine who to list.
4) The person running RT needs to open it up at the start of the raid. The mod does not recognize a "selected" raid until you do so.
Whenever a raider is sitting, for them to get credit in RT, they either need to be in the raid, or manually joined using the /rt join <PlayerName> functionality.
As we allow our players to do whatever they wish to do while wait listed, we have to re-join them to the raid after they leave the raid. I added the listme feature to do nothing more than automate the /rt join functionality.
Pros:
1) the person running RT does not need to do manual /rt joins when a player logs on and wants to get wait listed. This can suck during a boss fight.
2) It puts a time stamp in the players note so you can see who is currently wait listed, and what time they sent the listme. You can use this as a pseudo wait list to see whos available.
Cons:
Your player base have to become adjusted to using it.
Caveats of use:
1) They have to be OUT of the raid before sending the "listme"
2) Each and every time they leave the raid, they have to resend to the person running RT, a tell of "listme"
3) The listme tell HAS to come from the main or the person who wants to be in the raid, not his alt, or friends. The mod reads the name of the person sending the tell, to determine who to list.
4) The person running RT needs to open it up at the start of the raid. The mod does not recognize a "selected" raid until you do so.
baldylox wrote:
im going to try your vers with the listme added in. right now im use EKwaitlist even though its nice, ive not figured out how to add peeps to my imports using it...plus i can maybe lose 1 addon :D
That mod is much better for wait lists... I just use the notes as a pseudo one. I just like it as it ties into attendance.