Really, come on!! We can only make 10 loadouts across all specs? How about 10 for each spec ffs. Do you really need to save a few kilobytes of data that badly?
I tried to make a PvP, M+, Raid, and general kit for each of my three specs. But apparently that’s too much.
I like your idea of a load out for each type of content per spec. So since druid exists then they should offer 16 loadouts per character or 4 per spec. Does that sound reasonable?
You can make more. Make a load out → click “share” → copy the link/letter thing → save those to notepad or something.
Imagine playing all 4 specs of a druid in pvp and pve… that sounds like a nightmare with 10 loadouts…
Time to start some spread sheets for talent layouts rofl.
This is a helpful tip/workaround if blizzard doesn’t address the issue. I hope this helps the guy out.
Yeah 10 loadouts don’t seem like enough if it’s per character and not spec. Druid would definitely struggle if the player enjoys all 4 specs.
The problem is, why is the limitation 10? You shouldn’t need external sources if they offer saving a loadout in-game.
I can foresee having a loadout per boss/dungeon/open world content/pvp, etc just for this bm hunter.
Not really sure the reason for this constraint. 10 across all specs seems a little limiting depending on the type of content. Raid can have multiple load outs for one spec and if you’re the person that offspecs heals/tank in the raid group or M+ group or use different specs because you have 2 or 3 dps specs / heal specs. That loadout count gets maxed real quick. Please change. This feature was supposed to be there to make it easier on people.
> Anyway, like I was sayin’, loadout is the fruit of the sea. You can raid loadout, m+ loadout, pvp loadout, quest loadout, farm loadout. There’s uh, tank loadout, dps loadout, healing loadout. Cleave target, aoe target, single-target. There’s pineapple loadout, lemon loadout, coconut loadout, pepper loadout, loadout soup, loadout stew, loadout salad, loadout and potatoes, loadout burger, loadout sandwich. That- that’s about it.
It’s the same with how many achievements you can track. Thought it was a bit annoying but oh well.
“Ten loadouts is more than anyone will ever need.”
-Unnamed WoW dev
I agree, and the 10 loadout limit makes no sense. Especially for those of us who play multiple specs and have multiple builds that we want to try out. What’s the downside to having more loadouts, especially since they gave us a great talent tree with so many options and iterations? What’s the harm in increasing it?
It feels like some intern was testing it and said “well I only ever play 2 specs, nobody would ever need any more” and that was that.
Blizzard, please listen! I am not a pro player but I exactly experienced this problem. 10 loadouts per spec is completely reasonable even for a casual player.
Super smart idea 
I think the main problem is that they can’t switch between them so easily in game. But I think it’s a good move to do this with loadouts people don’t use often anymore.
That said it would be AWESOME to have unlimited loadouts. You could have one for each raid boss and M+ key.
Oh I thought it was per spec too. Thats a shame.
Between me its solo builds, pvp builds, dungeon. Dont plan to raid until lfr then I might make raiding builds. Thats like 4 per spec.
Then adding the niche talents for some dungeons… who knows.
There’s gotta be an add on somehwre that will allow you to save more. It’s just a 32 character string after all.
Ridiculous Ill have to put yet another add on in my game, increasing Lua errors, when clearly blizzard was trying to make their UI a one stop shop.
I mean come on Bros… Can’t you really not save that 32 char string beyond 10 per toon? Are you saving it differently? If so… Why…
Yep blizzard are cheap af (as per usual). It’s about their shareholders not their customer base. It would cost them extra (server load wise) to give that many loadouts, so to save money they restrict them. Blizzard constantly implement restrictions and gotcha’s in their development structure, i can only imagine what it’s like to work for them.
Yeah its literally a string of letters so I can’t imagine server load is a factor. We are talking bytes, not even kilobytes. My guess is they want players to NOT feel like they NEED a talent loadout for every single different encounter. I agree with this if it were limited per spec. Even if it were limited to 5 per spec instead of 10. The main issue for me is that I literally can’t play all of my specs efficiently on druid with the current classwide limit. Stupid asf
I jst dont see why we can’t have at least 3 times what theyve given uus by default. I have a loadout just for tanking Ruby Life Pools. How is this few storable loadouts decided? Because it seems like it should allow for some more variation in play.
Also, it does seem like it should be possible to keep any number of these strings in the local data and not have any server connection at all. I think this type of perpetual client storage is also needed for inspection when it comes to macros because the macro storage and functionality of storing them needs looking at also.
I think it should be possible for a player to keep a localized character profile in the local interface data, with all the desired macros and loadouts and a clean interface to recall them at any time its pertinent. The change is not really the issue at hand but rather the ability to save and recall configurations at the time of change. It doesn’t make much sense for the player to have so limited options when the opportunity for unlimited options seems so obvious.
More proof that the player base will never be happy and spends way too much time complaining over trivial matters.
Be glad changing specs doesnt cost 100000g each time (compared to Vanilla gold costs).
You have 10 load outs.
As said, you can copy others to a note pad
You can change anywhere in the world except if in combat
You can change to any spec
You can add/remove any talent with a click
Still not good enough