Jump to content

Slicing Lockbox Changes Intended?


lull

Recommended Posts

The statistics on your link are interesting, but the results drawn are faulty. Presuming that critical success on a mission is truly a random event and green boxes are the culprit (to the point of yielding less that a white box). How can crits not detrimentally affect the abundant missions yet favorably affect the rich missions?

 

Its because abundant missions return green lockboxes on crits, and white otherwise. Rich missions return blue lockboxes on crits, but green otherwise. Because of this, a crit on an abundant mission is a slight loss, while a crit on a rich mission is a huge gain.

Link to comment
Share on other sites

  • Replies 253
  • Created
  • Last Reply

Top Posters In This Topic

Basically unless you crit you're losing credits sending companions out on slicing missions. So pretty much I'm not sending companions out right now. Nor am I logging on alts. I'll be looking for some other way to make credits cause that is not reliable enough.
Link to comment
Share on other sites

I did the math (see #191, above).

 

Admittedly, I only ran 400 missions post-1.2 for that analysis, but given that the standard errors are so small for everything but the rich missions, and I can work around that with the math I went through above... running more missions to collect data... isn't the best use of time.

 

Maybe a better way of presenting the previous post is like this:

Average earnings by type / grade of mission
 5 Abundant         5 Moderate              5 Rich            6 Abundant         6 Moderate 
    249.2381            368.2857            178.8148            166.3246            229.7692 
      (38.61)               (57.31)               (250.38)              (29.95)               (30.76)

 

 

according to this you can still make a tiny profit from the lock boxes (about 10% of what it used to be) so slicing can still make decent credits when you get a mission discovery to sell on the GTN. but even if you are very lucky and crit often your better off going with a different mission crew skill such as diplomacy which gives you companion gifts to sell.

Link to comment
Share on other sites

Response to my ticket on this issue, sounds promising:

 

Greetings [REDACTED]

 

 

I am Protocol Droid [REDACTED], Human-Cyborg Relations.

 

I have received your transmission regarding an error that you have encountered where in the Credit Rewards for the Crew Skill, Slicing, yields credits that are lower than the amount needed to start the Gathering Mission. Rich and Bountiful missions are also yielding very low amount of credits as rewards. Thank you for bringing this matter into our concern and we understand that this issue can cause a great deal of frustration and/or confusion.

 

Rest assured that your report has been forwarded to our development team, who will investigate further. Please be aware that when a ticket is escalated for such an investigation, it will no longer be visible to you through the in-game helpcenter.

 

We regret that we will be unable to provide you with further updates on this issue, but recommend checking the latest patch notes at http://www.swtor.com/patchnotes for information on any fixes or changes related to this issue.

 

We would like to apologize for any inconvenience this may have caused, and to thank you again for the valuable feedback you have provided. Please do not hesitate to report any other issues you may encounter while playing.

 

Galactic Support is our specialty...

 

 

Sincerely,

 

Protocol Droid [REDACTED]

Star Wars: The Old Republic - Customer Service

Link to comment
Share on other sites

For me it's just getting frustrating. It feels like we do this every patch, and only once was there ever any word (or even apology) from Bioware acknowledging a change to Slicing (back when it was way too profitable). If I'm not mistaken, not once has there ever been any culpability or ownership of a bug introduced to Slicing (whether beneficial or not). There will be numerous posts on these forums with hard data substantiating our claims, yet the silence from Bioware is deafening.

 

I'm still a fanboy, but that kind of disregard is disheartening and disappointing.

 

I think all we're asking is someone saying, "Hey. This is a bug. Our bad. We're working on it. We'll let you know when we know more."

 

And while I'm wishing, if it was a bug through some kind of tweak, it'd be nice to at least have something in the patch notes saying that they're tweaking or playing with Slicing to tune/balance it. That way, we'd have some warning that a bug might be rolling out and thereby stave off the tinfoil hats.

Link to comment
Share on other sites

Response to my ticket on this issue, sounds promising:

 

Greetings [REDACTED]

 

 

I am Protocol Droid [REDACTED], Human-Cyborg Relations.

 

I have received your transmission regarding an error that you have encountered where in the Credit Rewards for the Crew Skill, Slicing, yields credits that are lower than the amount needed to start the Gathering Mission. Rich and Bountiful missions are also yielding very low amount of credits as rewards. Thank you for bringing this matter into our concern and we understand that this issue can cause a great deal of frustration and/or confusion.

[snip]

 

Galactic Support is our specialty...

 

 

Sincerely,

 

Protocol Droid [REDACTED]

Star Wars: The Old Republic - Customer Service

 

Wow, looks like they might fix this! The response I got (a week ago) was to the effect that everything was working as intended and that they couldn't help me with anything.

Link to comment
Share on other sites

I'm feeling it as well. Ironically enough, I swapped underworld trading for cybertech just before 1.2 released, since I like to have a toon on each side for slicing and didn't have one atm. Did I know about this ninja nerf? NO. But as I returned to my trooper after having a mediocre experience on my other toons post 1.2, I realized something. I was losing credits on slicing missions. A LOT OF CREDITS.

 

Some of the feedback seems positive, so I can only hope that Bioware is trying to address the problem. Otherwise, leveling slicing is going to be a HUGE cash dump until the very end, in which you have to gamble on getting a crit or losing half of your investment. They can nerf crits; I don't care. I thought they were a little high anyway. But please, for God's sake, don't kill our returns on everything else.

Link to comment
Share on other sites

Its because abundant missions return green lockboxes on crits, and white otherwise. Rich missions return blue lockboxes on crits, but green otherwise. Because of this, a crit on an abundant mission is a slight loss, while a crit on a rich mission is a huge gain.

 

Thank you!

 

Ok THIS explains what I've been seeing!

I've done almost exclusively Moderate and Abundant missions.

For almost every mission, I'd get a lockbox with more (not always a lot, but at least some profit) credits in it then the mission cost to run, UNELSS I've critted.

At first I tought it was because they reduced the amount given on a crit because they expected you to make it up from selling off the schematic/Mission discovery, but Green Lockboxes being bugged makes much more sense.

 

Here's my logs since 2.1:

 

 

Chacter/ Mission/ Cost to run/ Lockbox Results / Mission discoveries, schematics, Aug Materials

 

NOTE: Mission M6 = Moderate tier 6, M6t= Moderate Tier 6 Augment parts etc

Bounty Hunter t=Torian m=Mako g= Gault b=Blizz

g M6 1415 1993

b M5 990 1735

t A6 1485 1467 Pur Slic (340)

t A6 1485 943 Pur TH (340)

m R5t 2430 8 Blue

g A5 1075 1493

b M5 990 1260

t A6 1485 2142

m R5t 2430 8 Blue

g M4 665 1319

b M4 645 986

t A6 1485 1935

m R5t 2430 8 Blue

g A5 1075 1804

b M4 665 695

t A6 1485 1904

m R5t 2430 8 Blue

g A5 1075 1686

b M4 665 1182

t A6 1485 2104

m A5 1135 915 Pur Inv (300)

g A5 1075 1315

b M4 645 711

t A6 1485 1385 Pur Inv (340)

b M4 665 976

g A5 1135 752 Pur Inv (300)

m M6 1415 1798

t A6 1485 1485

b A5 1135 1205

g A5 1075 1703

m M6 1415 1485

q A5 1135 1232

 

Sith Warrior: k=Jessa q= Qunn

j M5 990 1435

q B5t 2150 6 Blue

j M5 990 1352 Ship Schem 370

J A5 1135 1641

q A5 1135 821 Pur TH (300)

j M5 990 1235

q R5t 2315 8 Blue

j M4 645 790 Blu Slice (250)

q B5t 2150 6 Blue

j A5 1075 1504

q A5 1075 1324

q A5 1075 1395

q M6 1415 2145

q M6 1415 1615

q M6 1415 1928

j M5 990 1302

q A5 1135 1801

j A5 1075 1515

q A5 1075 1335

j M4 645 746

j A5 1135 1749

q A5 1075 775 Pur Scavange (300)

j A5 1135 1342

q M6 1415 2095

j A5 1135 1006 Pur Scavange (300)

q M6 1415 1366

q M6 1415 2084

q M6 1415 1530

q M6 1415 2060

j A5 1075 1169

q A6 1415 1639

j A5 1075 1336

q A6 1485 1575

j M6 1415 1547

 

Smuggler: b= Bowdar c=corso r=Risha

b M5t 1225 2 Blue

c M4 665 1157

r M5 990 1305 Pur UT (300)

c A5 1075 1520

r A5 1135 1833

b A5 1135 1530

c A5 1075 1181

r R4t 1590 8 Blue

b M5 990 955 Pur Scav (300)

c A4t 850 4 Blu

r R4t 1590 Schem 240 Synth; Schem 240 Arms; 10 Blu; 5 Pur

b M4 665 667

c M4 645 943

r R4t 1590 8 Blue

 

Jedi Knight T= T7 K= Kira x= Ship Droid

T A4t 880 4 Blue

K M4 665 897 Blu Dip (230)

x M5 990 0 FAILURE

T A4t 880 33 Schem, 6 Blu, 3 Pur

k A4t 850 4 Blue

x M4 665 820

T A4t 880 4 Blue

K M4 645 989

x M4 665 844

T R4t 1590 8 Blu

K M4 665 Blu UT (250)

x M4 645 1217 Blu TH (250)

T R4t 1590 8 Blu

K M4 665 751

x M4 645 1330 Blu Inv (220)

T R4t 1590 8 Blue

K A4t 880 Schem 280 Arms, 6 Blue, 3 Purp

x M4 645 964

 

 

Link to comment
Share on other sites

Wow, looks like they might fix this! The response I got (a week ago) was to the effect that everything was working as intended and that they couldn't help me with anything.

 

Yeah, I got this response AGAIN. Except this time I asked if it was WAI - why were there no patch notes, no developer comments, no reponses to threads/tweets, etc. I was politely told (effectively) to shove off, and that I should take it up with BWAcommunity. I mean WTH are THEY going to do about it.

 

Oh well, I am going to continue tweeting SWTOR daily until I get some sort of response from them (I'm not going to harass the personal twitter accounts though)

Link to comment
Share on other sites

I can understand the Devs wanting to reduce the yields from Rich and Bountiful missions, but I do wish they'd done that by toning down the profits from critical success, not making every non-crit a massive loss. And like I said before, what really rankles me is that they didn't even give us a warning like they did last time they (justifiably) nerfed Slicing.

 

How is it understandable? Slicing was not that profitable, and from what I am seeing in my bug report response, the change was intended to balance the crew skills. The logical conclusion then is that Bioware wants crew skills to be money losers. Thus, no use doing them.

Link to comment
Share on other sites

Wow, looks like they might fix this! The response I got (a week ago) was to the effect that everything was working as intended and that they couldn't help me with anything.

 

I submitted a bug report today and got the 'working as intended' response. I will wait for more reliable data from Bioware, either in the form of a fix or a post/tweet about this.

Link to comment
Share on other sites

ok i have news... :):)

i had a chat with an in game CSR today and was told that "these changes to the green lock-boxes was completely un-intended as there was meant to be no change to them in patch 1.2."

 

this was a reply to a question i made re the green lock boxes being broken (yielding approx 60% less) in the missions you send your companions on, the quest reward ones AND the gathered boxes.

 

so it seems that if this is correct it may have been an un-intended consequence of the slicing changes :) so hopefully there will be a yellow post soon.

 

(id copy paste the convo as proof but you cant copy paste in game CSR convos :( )

** just realised i could have screen shotted it :( <-- massive sadface

Edited by DerekMiller
adding a bit
Link to comment
Share on other sites

Hey all, thank you for reports into this issue. We escalated this to the development team and after investigation, got confirmation that this was a bug.

 

It's being worked on now and a fix should be rolled out in a future patch. In the meantime, it'll be added to our known issues list.

Link to comment
Share on other sites

Hey all, thank you for reports into this issue. We escalated this to the development team and after investigation, got confirmation that this was a bug.

 

It's being worked on now and a fix should be rolled out in a future patch. In the meantime, it'll be added to our known issues list.

 

 

Thank you very much for letting us know. Given the past record of non-communication about slicing nerfs, this is a major step in the right direction. Even were it an intentional (but nonsensical) nerf, we would want to know about it.

Link to comment
Share on other sites

Hey all, thank you for reports into this issue. We escalated this to the development team and after investigation, got confirmation that this was a bug.

 

It's being worked on now and a fix should be rolled out in a future patch. In the meantime, it'll be added to our known issues list.

 

Agreed with the post above. Thanks for telling us. I've slowed down my slicing missions considerably because of this. It's nice to know that it's unintentional. I appreciate the response!

Link to comment
Share on other sites

Hey all, thank you for reports into this issue. We escalated this to the development team and after investigation, got confirmation that this was a bug.

 

It's being worked on now and a fix should be rolled out in a future patch. In the meantime, it'll be added to our known issues list.

 

stephen were you the little droid i spoke to?

 

HAHAHA BTW THANK YOU, i really appreciate this response as it will put behind everyone the crazy speculation and i am glad that at some point it will be fixed , whenever i dont really mind atleast we know what the story it is. so yeah really appreciated :)

 

and as to my prediction/hope of a yellow post, it was the next one.. :) winnah

Edited by DerekMiller
Link to comment
Share on other sites

Thank you very much for letting us know. Given the past record of non-communication about slicing nerfs, this is a major step in the right direction. Even were it an intentional (but nonsensical) nerf, we would want to know about it.

 

Honestly, it seemed kind of obvious to me... White lockboxes (from any source) unchanged... blue lockboxes (from any source) unchanged.. green lockboxes (from any source) diminished returns. That kind of behavior screams bug to me. ;)

 

Glad to hear I was right.

Link to comment
Share on other sites

Hey all, thank you for reports into this issue. We escalated this to the development team and after investigation, got confirmation that this was a bug.

 

It's being worked on now and a fix should be rolled out in a future patch. In the meantime, it'll be added to our known issues list.

 

Thanks for the confirmation and happy to see it's on the "get fixed" list.

Link to comment
Share on other sites

Hey all, thank you for reports into this issue. We escalated this to the development team and after investigation, got confirmation that this was a bug.

 

It's being worked on now and a fix should be rolled out in a future patch. In the meantime, it'll be added to our known issues list.

 

That's nice to hear Stephen but what is the point of testing and reporting this on the PTS if you don't take action until it's reported on live. This was reported both via /bug in game and I created a post detailing the results of 100 slicing missions in the PTS forums.

 

Testing is only of value if you act on the feedback.

 

Alodar :)

Link to comment
Share on other sites

Hey all, thank you for reports into this issue. We escalated this to the development team and after investigation, got confirmation that this was a bug.

 

It's being worked on now and a fix should be rolled out in a future patch. In the meantime, it'll be added to our known issues list.

 

1.2 introduced a lotta new (and old) bugs Stephen - may I ask if these were oversights from the internal QA team or is it due to the lack of testers you were able to transfer over to the PTS? I'm just shocked that so many made it through and it worries me that quality may not be a priority for Bioware any longer...which I HATE to even think of given your past reputation as a company.

Link to comment
Share on other sites

Hey all, thank you for reports into this issue. We escalated this to the development team and after investigation, got confirmation that this was a bug.

 

It's being worked on now and a fix should be rolled out in a future patch. In the meantime, it'll be added to our known issues list.

 

I knew it. Thanks for taking the time to acknowledge the problem. Now please include in the weekly patch next week :p

Link to comment
Share on other sites

Hey all, thank you for reports into this issue. We escalated this to the development team and after investigation, got confirmation that this was a bug.

 

It's being worked on now and a fix should be rolled out in a future patch. In the meantime, it'll be added to our known issues list.

 

I (and I imagine many others) greatly appreciate your response. Thank you.

 

Since we have received the desired response, would a moderator please close this thread?

Edited by lull
Link to comment
Share on other sites

Hey all, thank you for reports into this issue. We escalated this to the development team and after investigation, got confirmation that this was a bug.

 

It's being worked on now and a fix should be rolled out in a future patch. In the meantime, it'll be added to our known issues list.

 

Thank you very much for this response. I am still confused, and concerned that as recently as yesterday, CSRs via the bug report feature in game were giving responses that this was an intended change. As these folks are your primary front line contact with your customers, it is a major issue for them to be giving wrong information to the customers. Even the 'we've escalated' response is better than what I got yesterday. If I had not been a more community orientated person, that response would have angered me, and likely meant my being very angry at your company for a long time, until this was revealed as a bug and fixed in a more publicly noticeable way.

 

Again, thank you for your response, and I am relieved to hear this is a bug, and will be fixed. Sadly, I already made a big loss on a lot of cases when 1.2 hit, but I will look forward to going back into heavy production on slicing missions once this is fixed.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...