Weaponsmith Archive

I agree with the previous poster. If you really want this problem fixed as soon as possible, publish instructions on how to reproduce it. Every time an exploit is released into the public domain, SOE has released a hotfix within days. The fact that Taurin acknowledged it means one of two things is happening.

1. It's proviing difficult to fix. (Unlikely, since it's easy to reproduce).

Or

2. The number of people taking advantage of the exploit is low and patching it is not a high priority. (Likely)

Information dissemination lights fires and gets things done.

Mozzerking

P.S.

I promise I won't look. Honest.

For some strange reason I agree with your logic although it seems counterintuitive. If you want to stop this bug/exploit then tell everyone how to go about it so that more resources are put on the problem. I'm kind of surprised that it isn't on the web somewhere already (or maybe it is) because this has been happening for-just-about-ever.

Still awaiting a solution

/Bump/

Hint 1: The bug is transposing the current item stats onto the next item

Hint 2: You need advanced component to make this bug work

Hint 3: It doesn't work all the time, more like 10% of the time

Hint 4: Try dropping . . . .

/force push

Hint 5: Let's not give everyone clues on how to do it, eh? =P

Hint 5: Let's not give everyone clues on how to do it, eh? =P

---------------------------------------------

Why not - if SOE isn't going to do anything about it everybody might as well start using it.

Phew...that was alot of reading. From what i just read there seems to be 2 types of people writing.

1) Those who know of an exploit(meaning controllable and not random) where people are transposing krayt guns onto new schematics that do not need the tissue. Fine, this is a BUG and needs to be fixed.

2) Those who have had freakish success making a random gun/component. Now, this is NOT an exploit unless someone can do this at their will. My question is can this be done @ will?
If yes, DEVS fix this shi.t, if not then keep it, its a great way of giving weaponsmiths like me who are bored something to look for when crafting.

I have read about exploits, including duping resources, credits and now this. If some people have figured out how to transpose schematics and are killing the profession with their uber guns, i hope they get banned. I really hope that number 2 is just random and happens once in a blue moon and is not controllable, cause that really makes crafting more interesting and allows weaponsmiths to differentitate themselves rather than being drones.

And I do agree with the previous people who have said that the best way to get a fix is to allow more people to know about the exploit as well as it gives other a chance to recover from this threat to THEIR economics. Think about it, if 10 smiths on 1 server are exploiting they are making millions of credits while HONEST smiths or smiths who just don't know are seeing their profits dwindle. Would it not be better if more smiths had a chance to exploit so that in the end, it all evens out? If everyone has uber guns they are no longer uber. An uber gun is only uber when it is rare, remember that.

If I figure it out i'll post how. Kinda stupid to let someone abuse it while everyone else suffers. If everyone knows then who cares if it gets fixed since everyone can do the same. They can take all the time they want to fix it then, since no one will get an advantage from it.

Hmm just noticed that they edited my sig.

I like my new ont though.

wouldnt krayt guns still be better than the new avg exploited guns? I'm assuming this bug lets you make better than usual parts overall, or is this a bug that lets you make a schematic with krayt stats but not use up a krayt tissue.

in atleast one case the bug allowed someone to make a krayt ABPH and transpose those stats to a non krayt ABPH which was then turned into a schematic. I would bet this is the 'real' reason behind the 100 unit 'fix' on TC. Its not a bug fix, it just requires the exploiter to buy a tissue every 100 items instead of every 1000.

Well another week of defeaning silence has gone by in regards to this bug now ........

Can our correspondant find out if the time table for fixing this bug is being measured in weeks or in months as history has already shown that days wasn't the scale SOEis using.