Mounting on the run is awesome.

Mannan would indeed make an awesome SH location. Rishii would as well, but I don't seem to see how to make the current SH models fit the planet surface.

Just to be clear here, when you buy gold, you are not raising a finger to BioWare, you are doing so to the rest of the community. Pointing at BioWare while cheating is disingenuous at best, even if the player has a legit beef somehow with BioWare. Please stop with the attempt at justifying. If you are paying farmers, then YOU are the problem.

I'm not speaking for this "event", but I would point out one thing here. As far as I'm aware, no-one is making anyone do anything. ...thus at that point it makes it a little harder to read forward with an open mind toward your post.

Thanks for the productive manor in which this is put forth OP! I'd love to see email and whisper spam addressed more productively, and I appreciate the tone of this thread. Nice change of pace.

This would reside on my top 10 wish list. It really hamstrings that character until you're in the right mood, have time, whatever, to complete the content. Might be a technical block we can't see, but sure looks like the ability to enter Odessen when you wish was simply not valued high enough IMO, because every other quest below KotFE allows this. Would love a QOL list inclusion for this.

Yeah, unless of course that is not your opinion.

Well, I beg to differ here. Males and females often look different. Birds do so a lot. Baboons don't have to look far to tell the difference....big red airbag for an *** on females.

Said no cat, ever

I'm noticing something interesting about this. I love unlocking stuff account wide, mostly because the price is right and it adds a lot of flexibility and value to my RP. So having that go on sale is an excuse to go nuts. I even anted up and bought a bunch of $CC for the first time partially in appreciation (and partially to have ammo for future store stuff), so winning all around on this one I say, and good job! HOWEVER, I am noting something odd. Perhaps this actually makes some sense to someone else? Several items have successfully opened up acct wide for various items, so the function is working as intended for most items. But in trying this on my Wetland Dewback, purchased via the GTN (via the store most likely) a few weeks ago, I SEE $200CC -50% in the left window, yet the price still shows as 200CC. And indeed buying it shows a charge of 200CC. Looking at my armor, I see a similar displays for Valiant Jedi Armor set AND Interstellar Privateers Armor set, both via the CM last years sometime. I have purchased neither unlock as I can see where that would lead. I'd pull the trigger on either if the deal was actually applying. Am I seeing a bug? Should I report? Or is this somehow explainable in a way I'm not immediately seeing. Thoughts please? And thanks for any time spent! --------EDIT/UPDATE : I went ahead and bugged it, and will report what I find. Still open to opinions of course.

In a perfect world it certainly should not, but I'll hazard the guess that this relates to the abuse of transferring characters by gold sellers.

Ahhh keypunch days. When you could literally trip and spill your code all over the lab :-D I seem recall in the mists, waiting all week for a compile time once. Now when web programming, ... I hit refresh! yep, times have changes,...these here whipper-snappers don't know how good they got er, I tell yez! ....now get them kids on hoverboards offa my lawn!

And This ^^^^ That sir est the red tears of poetry man.

How very kind of you to say I honestly can't recall the last time anyone else noted the point you made that got me a'typin', so honestly kudo's back as well.

Preface this by saying I have over a decade on the job coding, and a large portion of that spend maintaining code I and other team members wrote. There are really three elements here. First is QA. In order to do a solid QA job on a product, you have to have a solid idea of how the system works, how it was planned and how it changed during development, or updates. Coming in cold to QA a product can actually help in some ways because you are testing it with fresh eyes, but think of it like police work. You can't patrol a city effectively without knowing the neighborhoods, knowing the people and knowing the weak spots in the overall body politic. In the early days we would send a product out the door fairly confidant it had gotten a good test. To use the Pixar motto, we 'sanded the bottom of the drawers' and then we tested each one over and over with a variety of clothing and towels and anything we could think of. But frankly, as the years have progressed, there has been a creep of more and more laxed assignment of QA resources. As soon as you accept that some bugs will get through to launch, that starts being used to rationalize letting testing scenarios go unaddressed. We CAN'T catch EVERYTHING. And that drives relaxing assigning QA dollars. It sucks and I've sat almost huddled with QA colleagues as we've watched products go out the door that we KNOW aren't adequately tested. Then there are the initial coders. Now this may seen like a strange thing to say, but the more you go up the complexity scale with programming, the more your code and coding choices become akin to music and art. Now I don't mean that in terms of the quality per-say. We'd all like to think we are making beautiful code of course, but most of it is blasted out the hatch, adequate to the task by definition only, and not much more, though we all have exceptions. What I mean by 'art;' is more that there are a million permutations of how to code up a complex system, and your work becomes less a task of obvious construction, and more one of harmonizing all the bits to each other based on your own vision or gut. Then there are the QA and Coder debuggers/fixers. What that leads to is even for those coders who do a good job commenting their work, using sensible and solid practices with regard to code inclusions, file naming and folder structures, proper use of variable naming, application of objects and functions, and all manor of other choices, the end result is almost always very, very personal. Add in the pressure that modern coders are almost ALWAYS under today (being that their time is one of the most expensive bits of the process) and you end up with a very difficult brew for someone else to unwind and work through, searching for buggies to fix....or more to the point, a fix for a buggie! Thus, the point is that bringing in another outfit to debug is up to an order of magnitude (x10) less efficient than having the original authors fix and test their own stuff. It's not entirely unrelated to the concept expressed in Brooks law, which states adding coders to the late stages of a project actually makes it later that if you just bite the bullet and play out the hand. tl;dr =Their guys built it. They are really the only sensible crew to debug/fix it. ------------------------------------------------------------------------------------------ Two other things to say if I may: 1) When modern MMO code is updated, the factor of QA testers to users is very large. We are talking from around 10 people trying to play the game in such a way as to find all the 'oopsies', to in many cases MILLIONS of people playing a million slightly different scenarios, catching FAR more things, naturally! 2) One thing that I wonder about is if they are running the exact same server and DB software on QA and PRODUCTION. That is one way that a lot of outfits end up in release hell. God knows I've been in that special hell (:sigh)