Well, there are two things here... hardcores that just hate everyone not-hardcore and say they suck, and people that really do suck. I'm *not* hardcore (I've yet to even go on a raid in NR), but most of the people from my ex-roomie's guild I've run with, well, suck. When 2 80 hunters are pulling about the same DPS that a 75 boomkin pulls.... well I think you get the idea.
i am a casual player. i'm not in any guilds -- well, except for the guilds composed entirely of rl friends. i have never done a raid. i rarely bother trying to get into a group for a pug instance because the time of day i tend to play makes it hard to find the obligatory tank/healer combo (a rant for another day). i have done quite a bit of pvp tho.
my sense is that providing dual spec for people from early levels would allow people who generally solo to have an alternate spec designed for group quests (if they wanted). hopefully that would add more people to the lfg mix.
i am a casual player. i'm not in any guilds -- well, except for the guilds composed entirely of rl friends. i have never done a raid. i rarely bother trying to get into a group for a pug instance because the time of day i tend to play makes it hard to find the obligatory tank/healer combo (a rant for another day). i have done quite a bit of pvp tho.
my sense is that providing dual spec for people from early levels would allow people who generally solo to have an alternate spec designed for group quests (if they wanted). hopefully that would add more people to the lfg mix.
More friendly players that're looking to improve their gear for their off-spec, so they mix in with people that just turned 80, tyring to get their heroic gear, etc etc.
There's also the pvp/pve element, that was my first thought for both my mage and warrior. I can finally spec to tank, because I know later, I can switch back to my sweet sweet Titan's Grip and go run around in WoW War II. ^_^
usePreviewTalentSystem = GetCVarBool("previewTalents")
-- The API uses Talent Groups, indexed by a number
numTalentGroups = GetNumTalentGroups() -- 1 or 2 if you have bought the stuff
activeGroup = GetActiveTalentGroup()
SetActiveTalentGroup(newGroup)
-- this seems to be handled like a spell with a casting time.
-- When preview mode is set in the CVar, the following API may be used:
AddPreviewTalentPoints(tab, index, offset, isPet, talentGroup) -- offset can be +1 or -1, at least
ResetPreviewTalentPoints(isPet) -- the absence of talentGroup raises suspicions about it's presence above.
LearnPreviewTalents(isPet)
pointsSpent = GetPreviewTalentPointsSpent(isPet, talentGroup)
pointsUnspent = GetUnspentTalentPoints(isInspect, isPet, talentGroup)
-- The existing API is modified as follows:
name, icon, spent, background[B], previewSpent[/B] = GetTalentTabInfo(tab, isInspect, isPet[B], talentGroup[/B])
name, icon, tier, column, rank, maxRank, isExceptional, meetsPrereqs[B], previewRank, meetsPreviewPrereq[/B] = GetTalentInfo(tab, index, isInspect, isPet[B], talentGroup[/B])
tier, column, isLearnable[B], isPreviewLearnable[/B], ... = GetTalentPrereqs(tab, index, isInspect, isPet[B], talentGroup[/B]) -- Note that this wouldn't be backward compatible if a talent had 2 prereqs.
-- Glyph API is also updated as follows:
enabled, type, spell, icon = GetGlyphSocketInfo(id[B], talentGroup[/B])
link = GetGlyphLink(id[B], talentGroup[/B])
-- GameTooltip API is updated as follows:
GameTooltip:SetTalent(tab, index, isInspect, isPet[B], talentGroup[/B])
GameTooltip:SetGlyph((id[B], talentGroup[/B])
Let's see.. to make a blizz talentcalc or wowhead string importer loading the preview to primary or secondary spec?
That's not what that function does. SetActiveTalentGroup will swap between your talent specs, not assign individual talent points or preview points. As noted in jerry's post, SetActiveTalentGroup will act much like CastSpellByName, as if it is a spell being cast to magically transpose your character's knowledge from one specialization to another.
It's not what I meant, but regardless of that switching spec will require a lexicon or a "summoning" process no?
(forgot about that so my point is moot anyway)
It's not what I meant, but regardless of that switching spec will require a lexicon or a "summoning" process no?
(forgot about that so my point is moot anyway)
my sense is that providing dual spec for people from early levels would allow people who generally solo to have an alternate spec designed for group quests (if they wanted). hopefully that would add more people to the lfg mix.
More friendly players that're looking to improve their gear for their off-spec, so they mix in with people that just turned 80, tyring to get their heroic gear, etc etc.
There's also the pvp/pve element, that was my first thought for both my mage and warrior. I can finally spec to tank, because I know later, I can switch back to my sweet sweet Titan's Grip and go run around in WoW War II. ^_^
1000g for dual spec, Equipment Manager fiddling, new movable/resizable quest tracker, and lots more
Let's see.. to make a blizz talentcalc or wowhead string importer loading the preview to primary or secondary spec?
That's not what that function does. SetActiveTalentGroup will swap between your talent specs, not assign individual talent points or preview points. As noted in jerry's post, SetActiveTalentGroup will act much like CastSpellByName, as if it is a spell being cast to magically transpose your character's knowledge from one specialization to another.
(forgot about that so my point is moot anyway)
Not anymore. You click a button and 5 secs later, you're something else. No cooldown either. See this:
http://blue.mmo-champion.com/1/15198918444-maybe-dual-spec-was-a-bad-idea.html
Talented would need to do that if it still want to replace the Talent UI (and not load it).
Its intended for Dual-Spec. They removed the requirement and lowered the level requirement to 40. Dunno about glyphs