Make the sacrifice. Everyone wants BLU to do all content, but Yoshi said this would be why they couldn't.


			
			
				Make the sacrifice. Everyone wants BLU to do all content, but Yoshi said this would be why they couldn't.

			
			
				I feel this is sort of self fulfilling. They were afraid people were going to be jerks about optimizing the class, so they made it explicitly sub-optimal. So now we need to show them what for by putting up with a twenty level gap and a significant ilevel difference, because if we can't do that we're proving them right that we couldn't put up with a level 70 BLU because they have X skill slotted.
The Topic Creator could, if he were being as picky as the logic behind Blue mages design choices imply, specifically ask for an optimal team, or ban other classes they don't like.

			
			
				Of course, now I've run into someone forming a party finder to run Blue through Tam Tam to get the spell, with BLU locked out from the second DPS, so I'm feeling Salty. Time to burn down the servers.I feel this is sort of self fulfilling. They were afraid people were going to be jerks about optimizing the class, so they made it explicitly sub-optimal. So now we need to show them what for by putting up with a twenty level gap and a significant ilevel difference, because if we can't do that we're proving them right that we couldn't put up with a level 70 BLU because they have X skill slotted.
The Topic Creator could, if he were being as picky as the logic behind Blue mages design choices imply, specifically ask for an optimal team, or ban other classes they don't like.





			
			
				Ha, no. I'm in the process of farming level 50 dungeons for a Lux weapon. It would be easy to let a BLU tag along to learn some skills, but I refuse to support this crippled Limited Job design I spent weeks arguing against. If they could actually level up and do all content it would be a pleasure to form parties as equals and have discussions about optimal skills.
Graphics
MSQ
Viper


			
			
				Isn't that what you're doing, though, by reaffirming why they set it up that way in the first place?
Maybe, but they could also decide "have had too many people with only water cannon so blu's are auto kick", even if they're max ilvl. Lower level can easily be seen as a way to mitigate the drama, by locking Blu's out from meaningful content in the first place so no one complains about them.I feel this is sort of self fulfilling. They were afraid people were going to be jerks about optimizing the class, so they made it explicitly sub-optimal. So now we need to show them what for by putting up with a twenty level gap and a significant ilevel difference, because if we can't do that we're proving them right that we couldn't put up with a level 70 BLU because they have X skill slotted.
The Topic Creator could, if he were being as picky as the logic behind Blue mages design choices imply, specifically ask for an optimal team, or ban other classes they don't like.





			
			
				It's not. They said BLU would be excluded for not having chosen or obtained optimal skills for content. I'm not excluding them for having the wrong skills, I'm excluding them for having the wrong level. I treat all jobs the same in that regard.
The situation is a catch-22. In order for BLU to become unlimited players would have to prove they'd group up with an unlimited BLU, which we can't do because for that BLU would first have to be made unlimited. The option to not reaffirm the devs was made impossible by the devs. I can't do Expert roulette and Orbonne with BLUs and show I have no complaints about it. I can only carry BLUs through old content, which shows the devs that I've accepted BLU in its limited condition. They look at participation stats to confirm whether content was a success or not (Eureka).
You were asking the wrong crowd to "make the sacrifice". People who support Limited BLU are welcome to show their support in action by grouping with BLUs now and also a year from now.
Graphics
MSQ
Viper
| 
            
               | 
          ![]()  | 
          ![]()  | 
          ![]()  | 
        
| 
            
               | 
          
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.

  Reply With Quote



