Gearing in 7.0 is a self inflicted wound for BW. All the "need" this, that, or the other is irrelevant. It isn't about need. It's about the options for a portion of the population being completely excluded from attaining gear because BW said so. The game has gone from "Play the way you want" to "Play the way we tell you." A lot of unforced errors in 7.0 and BW seems disinterested in listening to players at this point and, if anything, have doubled down. IMO it's rather disheartening and disappointing BW is forcing change on it's player base with such disregard.

I, personally, am astounded how bad this expansion is going to be. BW took 2ish years during covid to brain storm a cool expansion and this is what we got. Seriously? This is what the best and brightest at BW have to offer? Just astounded and insulted.

Inflation in the game functions the same way it does in the real world. Perhaps with less subtleties. BW could increase the supply. Instead of 5 items being available on the GTN, have 30. If there is more to buy competition for sales would increase lowering prices. BW could pump the game with credits. This is a major contributor to the inflation. IMO, the only thing that hasn't been addressed is the Fee to put items on the GTN. Instead of basing the fee on the item, base the fee on the price the item is being put up fort. Increasing the fee would help 2 fold. Would help discourage over the top pricing. Since you're paying a larger fee for the higher asking price. Would also pull credits out of the economy over time. I would institute this change in Price Tiers. Hypothetical example. 1-500000 credits is 6%. 500000-10000000 is 12%. 10000000 - 10000000 would be 15% and so on. Just made up numbers....Just an idea.

I may not like what you say but I'll defend your right to say it. BW provides in-game tools to handle this. Use them. What you don't like is subjective. It isn't BW's responsibility to police chat. You are more than capable of doing that yourself. If BW did police chat, what happens when something you want to talk about is prohibited? What then? If you want someone or something censored expect yourself to be censored at some point.

There are 4 total. After running 20+ characters through this mission I've never had any issues. Which ones have you clicked and which one are you trying to click? The main issue people have with this mission is related to not clicking all the junctions. While there is always a chance for a bug to appear through updating other things in the game, I do not believe that to be the case here. Being standoffish and assigning blame isn't going to help.

I use a few different name generators. Using 2 names I have no issues creating characters. If someone is unable to name a character their favorite name, there are a few things. The game is 9 years old. A lot of names have been used. Find out who has the name. Offer to buy the name. IS it gonna happen 2 secs into the game. Nah, but you can do it if it means that much to you.

Just a terrible decision. Hugging 1000 wookies was bad enough. 2500? Absolutely not. First off, the title you get is horrendous. 2500 wookies for a terrible, terrible title. Ummmm....NO. Why not come up with a better title, laziness, instead of 2500 wookies total make the terrible title achievement 2500 wookies but include the previous achieves. Like most other similar achieves. Why this great departure?

I have 2 of the 4 mounts and entering the code does nothing for me.

I do have the feeling that the SWTOR BW people are just soaking up paychecks til the end. Things have been sub-par for a while now. Nothing indicates that will improve anytime soon. We all need to face the fact that the game is coming to an end. Short of some monumental event, expectations should be set accordingly.

The game will continue limping along til EA finally decides to put it out of it's misery. Recently updates and patches are buggier. Content has slowed. BW punishing players for problems BW created and left unfixed. We shall see. The game does not have years and years of content and improvements coming. It's past its prime by quite a bit.

If only there was a way to test patches before going live. Like a Test Server or something. This would help them out with squashing some of the major bugs and allow players to give feedback on what's going on in the patch.

Here in lies the problem. Was it intended or not? I'm of the opinion that this was originally a bug and BW failed to do anything about it, til now. They have no choice at this point since they ignored it. They'll have to give everyone 700 and move on.

I still believe that the cap raising to 700 was an error, bug, what have you, caused by the double xp patch. I think they saw it. They realized they couldn't rectify the error without messing up the double xp and the BH event, that was messed up anyways. I think they decided to leave it place. Once a new patch was released, 6.1.2, they decided to revert the error caused by the double xp patch. They expected no one would say anything or care. Players would just be leveling anyways so crafting wouldn't be an issue. Everyone saw that you could get to 700 without having to pay and decided to max out their crafting skills. Now that the mistake has been corrected they are saying "in some situations" "certain players" are having an issue. They bugged it up. Failed to correct it when they noticed it. Left it in place for 3 months. Now they have decided to correct the issue. I would bet the farm they knew all of this at the time. They just need to say it. We messed it up. It wasn't meant to be a thing. It was a thing so we're removing the requirement for level 700 crafting. They can parse who paid and who didn't. Find something to compensate the ones that paid and move on. It seems they're going to stick to their guns and call it a "bug." Pure nonsense.

Is the answer. The file is a part of Windows. Just because you didn't do anything to your computer doesn't mean MS didn't do something to your computer. I'd recommend google searching the file, you won't have to type much, and see if the solutions fix your issue.

I have had this issue since 6.0 was released. It's very annoying, I thought I read somewhere this was a known issue, but I maybe mistaken.