This node of the Character Service Transfer FAQ... "How does the Legacy system work with the Character Transfer Service?" http://www.swtor.com/support/helpcenter/5313 ...is missing information for users who have Legacies both on the origin and destination server. It should explain that: a) the transferred characters will join the Legacy on the destination server (the FAQ seems to indicate that the transferred characters would keep the Legacy name from the origin server, but in this special case they will adopt the Legacy name on the destination server) b) Legacy unlocks from the origin server will be merged into the Legacy on the destination server c) if the Legacy level on the origin server is higher than the Legacy level on the destination server, the Legacy level on the destination server will be raised to that of the Legacy on the origin server.

Thanks for the info!

This is a duplicate of an in-game bug report. Testing with a level 17 trooper called "Bug" on PTS. I cannot be 100% sure, but I was under the impression that I had completed all bonus missions I was assigned on Coruscant; when I left for the Republic Fleet, the only Coruscant missions left in the Mission Log were (untracked) Heroic missions. I logged out while being on the Fleet. Now that I logged back in, I have a mission called "Prison Punishment (Bonus)" in my tracker (state: "Defeat Justicar Prison Defenders: 7/8"). The mission doesn't seem to be "attached" to a "main" mission in the Mission Log. I have no idea what the main mission was, and whether I completed this bonus mission and got credit for it. All I can say for sure is that when I left Coruscant, I only had one tracked mission in the Tracker (my class mission, "Public Relations") and that I haven't seen a "detached" Bonus mission in the Mission Log before (in the Tracker, yes, if the main mission is untracked, but never in the Mission Log). Even after abandoning all Heroic missions, the bonus mission is still present. Something's fishy there. I have not tried abandoning the Bonus mission, in case anybody at BW wants to investigate the state of that toon. Screenshots available, if needed.

Thanks for confirming the problem and putting me on the right planet! And, yes, my PTS toon is a trooper (I probably should've added some extra info to the forum post that I didn't have to include in the in-game bug report, instead of just copy-and-pasting it). Did you see the problem in the test build (1.1.4) on the PTS - or did you experience it on the live servers? If the latter, it's probably not a high-impact bug.

This is a duplicate of an in-game bug report. I cannot offer steps to reproduce yet, here's what I did in the session (at least what could be related to the bug): - I logged in (PTS), I was in the market area under the Senate plaza on Coruscant - I sent my companion off to craft a barrel (armstech) - I accepted an additional mission on the Senate plaza - I used a taxi to travel to the Black Sun sector - While I was in flight, the companion returned from the crafting job - After arrival in the Black Sun sector, I reengineered the barrel - I picked up another mission - I went off to kill some Black Sun people - at some point I noticed that when I wasn't moving for a second or two, the weapon on the back of my companion started flickering at a frequency of ~5 Hz, then I noticed it was rendered alternately on my avatar's back and on the back of my companion. When it was rendered on my back, it was rendered in addition to the weapon I was already wearing (its parts were sticking out of my gun). I have made screenshots showing the weapon alternately on my companions and my avatar's back; if you want them, let me know where to put them. - Whenever I moved or fought, everything was fine. When I stopped moving, the weapon started flickering again after a second or two. - When I tried to unequip the weapon (C window, click on "Companion" tab, right-click on weapon slot), the swtor client crashed to the desktop [after relogging, the weapon was in the inventory, so unequipping worked server-side, but the client ended up in an unexpected state] I will update this post if I find steps to reproduce the problem. Update: didn't find a way to reproduce, I kinda hope the client automagically sent some kind of crash dump to BW. Would be a shame if this turned out to be a real issue after deployment to the live servers.