This page addresses questions specifically for the Iron Teams Challenge. Answers here do not necessarily apply to other Challenges.
If there are any questions you think should be on here, please contact Stone.
First, level your character(s) to anywhere from Level 10 to 20, following all the rules for the Iron Teams challenge, then click Import Character from your Account screen. Select your character from the list of eligible characters on your battle.net account. Please note characters MUST be in the Level 10 to 20 range, otherwise we cannot import them to our site.
Once you character is imported into the site either you or your friend can click Create Team from your Account screen. You'll be able to send out invites to characters to join your team. Invites can only be sent to characters that have been imported to the site and are not already on a team.
Yes, we are accepting Allied Races for the Iron Teams Challenge. Since these characters start at Level 20, we will be including them with 'regular' races since all teams need to 'lock in' at Level 20. It is possible that this could change at a later date.
For Allied characters, you must UNEQUIP all of your green starting gear. If you leave this gear on, you and your team will be red-flagged.
This can happen for several reasons, however, the most relevant / common reasons are: 1) Your character is not in the Level 10-20 range. 2) Your character name was already used on a WoW Challenges team and cannot be used again.
Overall, we want to try to keep teams data as clean as possible. Unfortunately at this time we do not have access to the unique internal character ID that all characters have. If we had access to this we could then allow users to re-use character names, even re-rolling the same class & race. Until then, it's easier for us to maintain the system by not allowing re-use of character names.
This is because your "Display Only Character Achievements to Others" option in Interface > Social settings has been unchecked. If you *JUST* checked it on, LOG OUT (not Exit), then try to import again. It may take a minute or two to get the Blizzard API data refreshed, there is nothing we can do about this. Patience.
Well, there are many different ways. I prefer to keep my Btag private-ish and use it only for actual gaming related stuff. So you can reach out to us by DMing us on twitter WoWChallenges or you can send me email at Stone AT WoWChallenges DOT com.
Alternatively, you can try to find me on Discord (Stone#3621): Discord.WoWChallenges.com, but I'll be honest, that's probably only a good avenue for quick / simple questions. Longer pieces of feedback are probably better sent by email.
Yes, sort of. Dungeons are allowed for groups as long as they are not running the dungeon with other non-team members. If you have a team of two, three or four, you can not queue up for LFG, however, you CAN run dungeons with just your team by traveling to the dungeon location and entering on your own. You CAN use the LFG tool if you queuing up with all five of your team members.
So basically, kills and killing blows are a bit tricky. First, let's talk about numbers: We really only look at the number of kills & killing blows (kblows) your team has after the team gets locked (first character surpasses level 20). After that we record whatever your kills & kblows are and deal with the difference since the team was locked. The numbers we are looking at will probably not match up with what you are seeing on the stats page because, again, we are looking at the kill & kblow numbers since the team was locked.
Another issue that may come up is having all team characters remain in close proxity to each other. If one or more wander too far away (perhaps to do some side-questing), they will likely not get credit for some of the kills that happened (again, not TOTAL kills... we're looking at the kill & kblows differences). Don't worry about being a level or two off from each, just level up together and you'll be all good.
To be honest, if you are all grouped up and killing stuff together, this won't be an issue. Same as the Killing Blow %. Don't worry about this. Really.
No. Originally, we allowed it, however, we're no longer going to track "Team of One" teams. This is a team challenge; part of this requires some coordination with your teammates.
Yes! This is not a silly question at all, we've never really had to worry about this kind of thing before. You ARE allowed to trade items amongst your teammates as long as they were not acquired by breaking the rules (mailing yourself stuff from another toon, etc).
We need to ensure that you actually own the character that is going to participate in the Iron Teams challenge. We create a user based on your BNet tag and BNet name (not your real name). For example, my recorded information is BNet:Stone#xxxx & Name:Stone. We do NOT show your Battle Tag to anyone except yourself. We also do not have access to your email address or real name. We do NOT have access to modify your account or characters. Battle.net information is limited to READ-ONLY (meaning we can't change anything): Battle.Tag, Battle.ID, Character Information.
Managing Iron Teams data is much easier by using your registered Blizzard account.
In order to log in with another bnet account, you will need to log out of the WoW Challenges site, then go to Battle.Net and Log Out there. When you return to the WoW Challenges site to log in, you should be prompted to supply the new other account information.
We take the image directly from Blizzard's character image render location. If the image appears to be broken it's because it's not available on their side. To fix this, you can log back into your character and click LOG OUT (not Exit). Logging out first generally kicks off a bunch of behind-the-scene update jobs on Blizzard's side like API data updates and, yep, character image rendering updates.
Overall, we're not going to touch team names unless they violate Wheaton's Rule: Don't Be a Dick. It's pretty simple, really. We'll also change team names if they are misleading or misrepresenting, whether intentional or not.