It sounds a bit like you're saying that the character you deleted is one that you created and automatically started with the expansion content. Is that what this is? If it is, then you used your free token when you created the character that you deleted. In order to start a new character the same way, you would have to buy another token from the Cartel Market. On the other hand, if the character you're trying to use to play the expansion is one that you leveled up normally, there isn't a valid reason for you not to be able to access the content.

It's just a suggestion, but instead of mailing things back and forth, you could take advantage of Strongholds. You can place a legacy cargo hold similar to your personal one that all of your characters in the legacy share. This is the way that i swap things between characters, but use whatever works for you. Like I said in the beginning, it's just a suggestion.

Personally, I would recommend Ebon Hawk over Harbinger. When I came back to the game, I started on Harbinger, but I didn't stay there. The chat and attitudes of a large number of the players there was too toxic. I saw too many new players belittled for being a noob in the chats to want to stay. I made the move to Ebon Hawk and haven't regretted it. But that's just my 2 credits worth.

If I'm reading this right, their response was correct. The part about additional customization changes being free refers to any tweaking you do to the look of the character as the new species. Changing the species of your character DOES involve a charge completely separate from the one to unlock the species itself. Now, it might have been a little cheaper to unlock it as part of the character change, but I'm not sure if that's possible since I've never tried doing it myself. The wording is a little ambiguous, but it still comes down to the fact that you were charged correctly for all that you did. I'm sorry that this wasn't what you wanted or intended. At least now you know what is entailed in changing a character's species to one that needs to be unlocked.

Dulfy usually has the most up to date guides out there, but you have to keep in mind that 5.2 is still pretty recent. They may not have gotten to posting a more up to date guide to include the changes made by 5.2 yet. There may be other guides that have been updated, but I've found that the ones there are still really helpful even when they are a little out of date. As to the damage reduction while being stunned, it can be really helpful since there seem to be a LOT of foes that like to stun you. That little extra can sometimes be the difference between winning and losing a fight. You have to decide if taking it is worth it for your playstyle or not.

Are you referring to his post or mine? I only posted a response to his to help make him aware of the rule. If you're saying that I responded as a way of promoting my own link, the same could be said about what you posted.

I responded to your post because while your post contained good points, they clouded the issue and the point of my original post. If you read my original post again you will see that I specifically state that the first thing you should check is that you traveled to the planet via your ship. My response to your post was not meant to pick a fight or argue. It was only to point out that the topic of the thread related to Belsavis and Corellia because of the alternate destinations that exist on those planets. It was also to point out that the issues that were popping up were the result of the way that the Galaxy Map, which is what you use to plot a course on your starship, had been changed. The defaut locations for those planets is not the regular destination and have been causing issues. Since I specifically stated that you need to go there via your ship in my original post. I don't understand why you insist that I've provided the wrong information while stating the exact same thing as the right information. My original post is about Belsavis and Corellia since those were the planets causing the most recent issues.

Putting your referral link in a post is against the rules of these forums. Put your link in the signature like everyone else. Putting your link in a post like this will get your post reported.

Actually, the issue that this thread was written to address IS because of the new way that the Galaxy Map works. This is meant to address the fact that both Belsavis and Corellia have alternate destinations as the default and can cause the quests to travel to them to not advance. The point is to make other players aware of this fact if they encounter situation. It is true that travel to any planet as part of the quest is often bugged if you don't use your personal starship, but that isn't what this thread was written to address.

To do it in the field, you need to buy the field respec perk from the Legacy window. If I remember right it's under Other in the Convenience section. I don't remember off hand what the credit price is, but you will need to have a high enough Legacy level to buy it. I don't remember the level either, but it's pretty easy to find in game. Edit: Ok, I looked it up in the game, and I was wrong about the location. It's in the character perk, the first tab, section of the Legacy window. You need to be level 10, have a Legacy level of 5 or higher, and spend 200k to get the field respec for a character.

It seems you got this sorted. Your other option would be to level up armstech as a crew skill and make one. With the way that companions are handled by the game now, it doesn't matter how good their gear is anymore, so you could give her something basic. Just consider this to be something to keep in mind for future characters that you might play.

The stats for your computer seem to be fine. It could be the version of Direct X, but it could also be your connection speed. It sounds a bit like things are getting bogged down when you go into things like flashpoints which is what makes me think it's connection related. I would check that and look into ways to improve your internet connection.

It's sort of a long shot, but have you checked to make sure your firewall isn't blocking the exe for the launcher. I'm not sure that this would cause your issue, but it might be worth checking out.

I've had it happen on Taris, Dromund Kaas, Korriban, and Coruscant that I can think of off of the top of my head. Oh wait, Belsavis and Nar Shadda as well. It doesn't seem to matter what class character I'm playing or what level they are since I've had it happening on one of my level 70s as well as my lower level characters. I think the 70 was on Makeb at the time.

I haven't played the class much since I came back to the game, so I don't really know the answer to your question. I would suggest taking a look in the class section of the forums. The answer is likely there though if it isn't there is always Dulfy's guides. I don't have the link on hand, but it should be easy to find the answers there as well. I'm sorry that I couldn't be more help, but I'm sure that either source will have the information.

I'm not creating this post because I have this issue though it has happened to me. My purpose is to put the information in a handy place for people to find quickly and easily since this topic seems to be popping up quite a bit lately. For anyone experiencing this problem, it's not a bug in the game in the normal sense. It's the result of the changes that were made to the way the Galaxy Map works. This "bug" has been known to happen on both Belsavis and Corellia. The first thing to check is that you traveled to the planet via your ship. Using the Galaxy Map to travel there directly has been known to cause the quest to not advance. The second and final thing you need to check is that you selected the right planet destination when you traveled there. No, I don't mean that you traveled to the wrong planet. For whatever reason. both Belsavis and Corellia don't default to the normal planet destination when you select them. Both planets have 2 destinations on them. In the case of Belsavis, there is the regular destination and Section X. The GM defaults to Section X, so you have to manually select the regular destination before you travel there. Selecting the regular one should trigger the usual jump to hyperspace and the holoterminal cut scene that follows. I hope this helps anyone who runs into this issue in the future. It's a common mistake to make when traveling to either planet, so don't feel bad if it happens to you. As always, May the Force be with You.

Yeah, my math was off there, but I was still working on my first cup of coffee when i wrote that. I had thought that it would be a 72 hour wait for transfer, and somehow my mind multiplied that as two 72 hour periods. On the plus side to it all, you got characters transferred quickly. I'm glad that it worked out well for you.

Actually, yes, I did check that. The only difference between myself and the OP that I can tell is that I"m not using the Legacy speeder training. As an example. my sentinel has speeder training 2 through his level, but the different mounts that he has like the refer a friend mount all move at walking speed.

I wish I could offer a solution, but I seem to be having the same problem. For me, the difference seems to be that it's happening with different mounts and on more than a few of my characters. The characters are varying levels, and it seems to have started after the most recent patch. I've defaulted to sprinting everywhere since that seems to be faster. All of that said, I would like to know the answer to this as well. I'll do some more testing a little later and update if I figure anything out.

I could be wrong, but as far as I understand it, the higher level legacy will be the one that becomes the legacy for that server. As far as the collection stuff goes, those things should be account wide unlocks. I know that I had one armor set that I unlocked on Harbinger before I moved to Ebon Hawk. I hadn't done any character transfers, but the armor set was unlocked on Ebon Hawk as well. Double check your collection because the collection stuff seems to be account rather than legacy.

This could be an issue that has been popping up lately with the new galaxy map. Try going somewhere like the fleet and returning in your ship. The trick is to make sure that you select the regular planet destination rather than Section X when you go. The GM seems to default to Section X rather than the regular planet destination. A cutscene involving your holoterminal should automatically trigger and things progress normal from there.

Customer service and hoping he remembers the answers to his security questions is about the only option he's going to have other than starting a new account. Depending on how long ago he stopped playing, it might be easier to get back into things by starting over. I know that it was for me when I came back to the game. I would personally suggest that he just create a new account instead unless there's a specific reason like the old account having unused CC on it that makes him want to use the old one.

The transfer trick is cheaper, but keep in mind that you can only transfer characters once every 72 hours. That means that it will take you almost a week to have the toon back on the server that you want to play on. I personally would go with the transfer option, but I thought you should be aware of the time involved.

Go into MySwtor and select My Account. In there, you will find a tab or whatever you want to call it for Forum Management. Click on that, and you will see several options related to forums like avatar and such. Just pick the one for forum signature and type your link in there along with whatever else and save the changes. It's that easy and every post you make gets your link out there without breaking the forum rules.

I encountered this issue when I was playing yesterday, and it may be the same issue that I was having. The mistake comes with the way the Galaxy map is set up now, and Belsavis is the only planet I've seen so far where this happens. The trick is that the default for the planet isn't the spaceport like it used to be. There are 2 locations you can select on the GM for the planet. You have to switch to the regular Belsavis location for the cutscene at the holoterminal to trigger. It took me a few tries before I realized what the issue was, so don't feel bad if you missed it. It's an easy thing to mistake, and they really need to fix it so that the regular Belsavis location is the default instead of Section X.