RaidTracker Frequently Asked Questions
General RaidTracker Questions
This is for RaidTracker 4, the new version.
RT 4 will ship the DKP code as an addon, and it will be included in RT. However the admin needs to enable this to use it. (This is disabled by default.) In any case, I'd suggest contacting your admin
Yes. RT has complete customization. I recommend checking the manual for more details.
Installation questions
Version 4 can support RT 3 themes (but not earlier versions.) Do check out the Styles page for details.
In RT 3, it is easy to add instances by going into Admin view, and in the
Location tab. You also need to add the icons in .png format in
/images/locations to make it visible.
Note that I have stopped playing World of Warcraft until
further notice so I have not been in touch with the game.
Permissions were changed in two ways: the "self override" moved into Account preferences, and also several keys were consolidated or eliminated. Because of this, there was no easy way to remap RT2 keys to RT 3.
New user questions
It is very possible that either your admin has upgraded RT, or linked the accounts to another copy of RT. Try to log in first. If that doesn't work, or if you know that it was upgraded, then hit the forget menu option, and follow the procedure. In the worst case scenario, contact your admin, who can help fix the account for you.
You can always try to click on the Forgot menu option at the top. Then follow
the instructions to create a new password for your account. If that doesn't work,
contact your admin so you can have your account reset.
There have been known issues of older browsers (particularly IE 7) not accepting
cookies without a privacy policy in older versions of RT. Check the bottom left
for cookies, or upgrade or switch browsers. Also, while RT may degrade well for
older browsers, support for versions before IE 8 are at your own risk.
For most character changes (level, name, raid role, most deletes), you can change this yourself in the Character menu. However, there are exceptions to this, some examples follow:
- If you cannot edit your settings, check with the authorized people who can make these changes: there may be a group policy on this.
- RT uses the role of the current (or default) character in settings when you sign up or switch characters--unless an event planner has done otherwise. You may switch the role in settings and use the workarounds. But it is highly recommended to let an event planner change this for you (by leaving a comment).
- If you created a character of the wrong class and is not the main or only character you may try to delete it and recreate the character. This is not recommended as you may lose credit and possibly points for all events with this character. It is recommended to contact an admin to change it.
Events, raids and subscriptions
RT 3 allows you to sign up in 3 ways. You can also show disinterest (say "no" to an event), but this requires the 3rd option. You can:
- To easily say yes, just hover over the event, and click the OneClick™.
- You can also click on the event, where you also have the OneClick™ button to say yes.
- Clicking on the event takes you to the Event details, where you can select your interest, character and any possible notes. Then click the submit button at the bottom.
If you have the permissions, you can do this by selecting the event to subscribe to. In the Details tab, select the character, the status, any comment if any, and then click the change button at the bottom. DO NOT click the OneClick button, as that is just for simple subscription with your primary character.
RT 3 will tell you what the problem is simply by going to the event. Look at
the bottom, as it will tell you if you are not logged in, not active, past the time
to subscribe, or if you are on Confirmed or Restricted list.
If you are not logged in, please do so, and then try again. For all other problems
listed above, you need to talk to an admin or an Event planner/leader about it.
If you are the leader, your subscription is automatic, and cannot be changed until you pass the leadership to someone else (or to no one). Once this happens, then you must ask to get your subscription changed.
There are many ways to find out, and all but one requires you to be logged in. A newsticker across the top, icon and/or status notice in Main view, or event tooltip as well as in Event view (under Status.) The only one that does not require logged in (if accessible) is in Event view, and look in the Subscriptions list.
User permissions/ranks
RT 3 does allow you to insert a rank between two ranks seemlessly. First, the new rank is inserted at the end, then the rank orders get sorted by order. RaidTracker will then sort the ranks by order automatically. For example, if you have 7 ranks, and want to insert the rank above the last one, you must set the last one to any number higher than what order you set the new rank (RT will renumber the ranks).
There are three factors to consider when inserting (or reordering ranks). First, any two ranks cannot have the same order. Secondly, a new rank is inserted with the order 100, before it is sorted into the proper spot. Finally, you cannot insert an RT rank above the Admin (1st RT Rank). The system needs an admin.
Certain local settings are vital to RaidTracker to keep it working right. The statuses can have their names changed but cannot be deleted or added because it is vital to subscriptions. Other things like RT admin rank and the "none" location cannot be altered or deleted (apart from changing name) to ensure a fallback. And finally, all categories require at least one key item.
It is suggested if you create keys at the beginning before you roll it out to the public. Avoid deleting or modifying. It is easier to add to the system than it is to delete.
Yes, this is possible. You will need to set the permission "Event|Add" to the
lowest rank you wish, and also in Admin/Events, set the "Leader on Create" to Yes.
(If you set it to Prompt, it will ask when created, which is probably not ideal
for a guild calendar.)
When this is set, the member who created this event will have control of this event
and no one else (unless the Event|leader permission is set). The leader will be
able to do almost everything except DKP and delete subscriptions (unless the account
has the rights already). However, stats are tracked for these like normal. So it
is still recommended to install another copy, and link accounts to make one act
like a guild calendar.
The leader feature in RT 3 allows one person to take control of the event. Users can recognize who is in charge of the event, and the leader is automatically placed on the Confirmed list. The leader can change details, move subscriptions and even change characters or roles. Stuff that event planners can normally do.
A leader however, does not naturally inherit the priviledges of deleting subscriptions, or DKP. Also, other accounts cannot control events that don't have the "event|leader" priviledge set. And finally, leadership may be passed on, either to another person, or to no one. The latter returns an event to normal control.
Yes. In Admin/Accounts, set the "Account Activation" to High. This way, only those with the account|inactive permission can activate accounts when necessary, and accounts that are inactive can only modify their profile/characters.
An answer recommended in earlier RT versions is to create a new RT rank at the lowest level and assign no privileges to it. This is not recommended in RT 3 as privileges and subscription model were changed.
Active accounts have access to normal access to RaidTracker depending on their
RT rank. This includes subscribing to events, creating characters, and the like.
Inactive accounts cannot subscribe to events, or interact except to modify their
own account settings (preferences, characters, etc.) In fact, in RT 3, once an
account is inactive, it no longer appears in event subscription screens in any way.
Reasons to make or let accounts inactive vary, but here are some examples:
- Shared RT account database to make one exclusive (like for alliances)
- Accounts on leave of absence (will not show as not subscribed in event list)
- Players who have left guild (for stats, or for a temporary wait period).
- Screening accounts before activating.
If you want, you can. Do note that once an account is deleted, all stats tied to that account are gone,
including attendance, and possible points. If you don't wish to ruin the stats (like for recent events),
you can make an account inactive.
To delete or deactivate an account, you may do so in the group list, or their own account page.
In RT 3, you can choose to share account data (which includes characters) with different installations of RT (version 3.00+). But you can choose to not include certain accounts on a certain installation. The active accounts can access RT features. This allows one to use one copy for a guild, and another copy as a alliance between two or more guilds, with the same log on, but restricting access to those not in guild on certain copies.
Deleting an account will delete the account from all installations relying on the same account table. Note that in 3.00 this will not clean up subscriptions of deleted players in other copies automatically.
Event/Raid management questions
The short answer is no. But you may make it possible if you choose to alter some features. If you just want to track the total amount of events users have participated in, and don't use DKP (or use another system to track it), you can use the points system in RT. Assigning 1 or more points for events that are important, while 0 for other events not worth it.
If you wish to use the more "advanced" stats, like statuses, tracking over a time frame, or you do use DKP in RT, it is still recommended to install another copy and link accounts.
RT 3 allows you to change alts or roles in an easier method than previous versions. Hover over the player in question, and click the character to use, or the role to use.
Yes. In Group view as well as Account/Transactions, you can choose to track for a recent previous number of days. Lifetime will track counts of all events past or future. The default can always be changed in Admin/Display.
Yes. 3.00 shows a bar above the subscriptions table in the Subscriptions tab. The counts show the total role count on the Event list or the whiteboard. Note that 3.00 will keep counts of those on event list only, not whiteboard.
Points/DKP
Note: DKP may be used to keep it simple. But whatever your system is called, assume that DKP is like currency, like Gold.
**this is a work in progress **Absolutely not! It's not enabled by default. If you don't want to, or you have your own system, you can continue to use it.
Yes, both in pure form as well as zero-sum fixed list system.
While your rules on DKP may vary, if you can utilize any of the following features:
- Points awarded to group by event, boss, or time*
- Points awarded to individuals by any means*
- Bidding system
- Spend half, Spend all, or systems that have minimum points, minimum % of account DKP, maximum points, maximum %, or a combination
- Fixed item cost, or an item table
- Zero-sum *
- Systems that allow accounts to "pool points" among characters
* Zero-sum does not allow award points. Points are awarded when another person buys an item (which is averaged out and awarded to the rest of the group.)
Support is a vague term, though there are some systems that may be harder to use with RT. Despite adding DKP/points to RaidTracker, RT is still designed to be in line with the KISS principle. You can create addons and introduce it to RT. Here are some examples, and the workarounds should you choose these rules:
- Suicide Kings, (Top person in the list falls to the bottom after getting loot). Workaround is if you can convert list to a point value, then use award and Purchase maximum.
- Weighted point system for event. The workaround is if you do the math for points.
- Ni Karma: A complicated system where you can use karma/points to add to rolls. You can workaround the karma by using points and award 50% (set as minimum/maximum), but the dice roll counts: you're on your own.
- Decay/tax system: RT ties points to events, so you could create an event and use penalty on each account for a tax.
- EPGP system, or one that relies on more than one type of points tracking.
- Rolls, or anything with a random number generating system
- Bank accounts. You can create a new account (and then include into events) if needed.
There are many reasons. RaidTracker tried to implement the easiest approach when it comes to DKP. Since most transactions involving DKP are done on events, limiting the user interface to put DKP in events allowed the easiest way to manipulate DKP. It also allows people to say "Yeah, I got item foo on the bar event. In addition, it allows one officer to upload DKP transactions after another without conflict (like if internet issues happened).
The difficulty in having this policy is that rogue transactions (award or purchase) must be tied to an event. There are three workarounds, depending on your settings:
- You can create an event (like one for 5 minutes ago), and use this event to award/deduct points for that character. However, this may not be good if characters must be part of the event, and you track attendance carefully. (You'd have to add a subscription for that character in this case.)
- You can add the line (award or purchase) to the next line. But do not use this if a member downloads the list and uploads it. Point totals will not be correct, and this item may be forgotten.
- You can add the line (award or purchase) to a past event. It may look out of date when timestamps are concerned. Also, if the character must be part of the event, you may have to look further (or look in the account's transactions to choose an event).
Due to time restrictions getting RT 3.00 released, the DKP module was postponed to 3.10. There are portions of the DKP system in RT 3.00, but was disabled due to the lack of time to test it. Upgrading to 3.10 or later will resolve this.
The tour page for the DKP Events shows one tab, as proof of concept. There were three problems that made me rethink the user interface: When bigger parties and more items added, the page can get unwieldly long. The interface also did not accomodate for zero-sum and item tables properly. Finally, neither the table, nor the summary table alone could display both available points and transactions properly, so splitting into both a summary and list view was the best thing to implement the DKP.
Character pooling will change what RT relies for total points (i.e. you need to spend a % of points). The "Total" at the bottom of the table is accurate. But as RT ties DKP to events, the character is going will be the default character to be awarded/deducted points, especially if either DKP is limited to attendees, or the event DKP officer tracks from within the event and not from DKP (e.g. downloads the list from RT to use an addon in WoW, then uploads the list).
Another thing to consider if using zero-sum, purchase an item may put you in the negative.
This will vary on multiple factors: if the two characters are on the same account, whether limit DKP to subscriptions is enabled, if character pooling is enabled, and how strict your group is at tracking subscriptions. You will not need to transfer if both characters are on the same account and character pooling is enabled. But if pooling is turned off, or other situations are enabled, this is much more difficult.
If you can, try turning off the "Limit to current subscriptions", even if it's temporary. This affects only new transactions entered. Then choose the last event. You will need to make 2 DKP transactions: a penalty for the one transferring out of, and an award to the one it's going to. You could also make a new event for 5 minutes ago (up to two if it's 2 characters on the same account), and enter the 2 transactions. However, this will affect stats if "Limit to current character" set.
Yes. While it's not possible to restrict decimal points, if you have a bid system that does not allow one to go below zero, set the maximum to 100%. (This does not apply if zero-sum is turned on, or an item table is in use).
TBA