Commando Archive
Thread: Whats the deal?
My droid shop on Kettemor is going to be stocked heavily with Bounty Hunter Droids tonight. I realize there is a dreadful shortage, and will do my part to help out.
My shop is south of Theed: -4306, 3313
In the last 2 weeks I have seen my Seeker and Probe droids sales drop to nothing. I had a store dedicated to just those 2 items and sent emails and such to all the BH's I knew of. Nothing has made them come over to my store and make a purchase. I am even below the competition in my area and it still doesn't draw any sells.
I ended up dropping the store because of the very reason that it just wasn't worth keep relisting my items. Also, with the seeker bug out there BH's are taking full advantage of it and I think that is another reason why my sales are at zero.
Anyway thats my 2 credits. =)
http://forums.station.sony.com/swg/board/message?board.id=jedi&message.id=249618
So I am confused. It seems the forum at the link above says that the method of unlocking ones slot will not change in publish 6.
Whats the deal?
Read the FAQ's. it's a common problem
copied directly from the Image Designers FAQ by NJ62
Q: my partner has an outstanding image design offer. What is that and how do I fix it?
A: That usually happens when you spam a macro too quickly for your partner to keep up with accepting, or when one of you goes LD during a design. The following fix may work, but this is a tricky and annoying bug.
- If your partner has an outstanding offer:
- target self using control-1
- type /im
- target partner
- type /imagedesignSetValue blah blah
- partner accepts
- target self using control-1
- If you have the outstanding offer
- target partner
- type /im
- target self using control-1
- type /imagedesignSetValue blah blah
- you accept
- target partner
Note this doesn't end the bug, it just passes the bug. The only known fix is a server reset.
I tried it didnt work
. Guess ill have to wait till the server resets. I looked at the faq b 4 posting lol.
Note this doesn't end the bug, it just passes the bug. The only known fix is a server reset.
If you read the FAQ then you saw that. Then you would have known the only true fix is a server reset, then you wouldn't have had to ask the question.... do you see where I'm going with this?