Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
Quick Links
Most Recent "Bugs" and what is SOE going to do about it?
SWGmodAlpha
Member Posts: 126
With Game Update 11 came Battle Fields, and with it came a now fairly well known exploit. Excuse me, "bug".
Basically, as long as your PVP death caused the entertainer buff to dissappear, IE, less than say ~3 mins. The next buff would essentially stack with the previous buff in some fairly predictable areas. IE, Armor and base stats. Some even claimed to stack exotic stats.
Now we have game Update 12, released yesterday, with an emergency shut down about 4 hours after the servers came up.
Why? U guessed it, an exploit. Excuse me, "bug". The offical annoucement is here:
http://forums.station.sony.com/swg/posts/list.m?topic_id=976813
We know for a fact that their are players that were aware of this exploit before GU12 went live because they knew to be on to make the items. These are the same players that SOE thinks has their best interest at heart when testing game updates on test servers. Else, this could only be a major internal issue at SOE that they are utterly failing to control or correct.
SOE has been asked, "What are you going to do about these game breaking items that people crafted before the shutdown?".
The only answer to date is silence that is deafening. How can doing nothing be the right thing to do?
Comments
Thats not right, you should post the latest response in the matter as well.
What happened is this:
Within hours of GU12 going live a bug was reported that for some meant that they had 2 sockets in their regular armor and clothing. The two sockets are intended for cybernetics only and the bug wasn't reported untill it hit live servers because the players on TC (as opposed to TCP) didn't find the bug.
TC and TCP is different, TC is basically a copy of an old liveserver so its the only place that this bug could have been discovered.
Its possible that players knew about it and kept it secret, but its more than likely that those wheren't the ones reporting the bug that hit live. Exploiters usually keep quiet about these sort of things.
I passed on the bug and information about possible reproduceable steps immediately after PM'ing back and forth with the ones experiencing it. The bug was posted on my weekly top5 list as the top1 priority. Within 20 minutes of handing over the list to the team, the servers came down.
The emergency fix targetted the remaining double socket items that had not yet been abused. Within 24 hours of the fix going live, the team was also informed that legacy items existed that needed to be handled as well. They will be meeting to discuss how to best locate these items and get them fixed. Once they find the best solution they will post about this.
Thanks Vicent and I knew I could count on you or Badger to provide an update.
What you post is correct and also vague.
No excuse for them not coming out and saying, with out being vague, that they are committed to fixing or removing the items from the game and that the items will not be permitted to remain.
However in good old SOE fashion, they say only that they will discuss and determine a fix. Sorry but that is just weak vagueness that does nothing to suggest any direction.
Based on the fact that this is the second major bug, in as many updates, that vastly affects combat game play, they need to take a stand and say something with clear direction.
I'll believe it when they put it in writting first, then actually fix it second.
I happily lack your faith.
They have said they will post about it publically when they have determined what direction they will take on this one.
Nothing vague about that, they know its going to be a problem but fixing it can be even worse with all the pre-NGE clothing out there with multiple mods on them. Its not as easy as it may appear.
I would think long and hard about the solution on this one too. If they do it wrong, they screw up all the crafters with pre-nge crafting suits with hundreds of billions in total across all servers. If they rollback tons of players will be mad because they lost billions of credits worth of trades, loot, heroic tokens etc.
Whatever the solution may be, they are ensured to piss off players.
What exactly is so hard about making a query to a database when all the parameters fo the issue are known?
They know the time frame, the date, that the items are wearables, and they know what the maximum stats should be for any crafted wearable item.
Anything "PreNGE" was made years ago so how freaking hard is it to add a date field with the known criteria?
Total and utter BS for them to say they cannot do this or it is "too hard".
The only thing that makes a database query for record removal difficult are the people involved and the tools that are available. Assuming they have the proper tools to administer and maintain their database, who is in the way?
Are they committed to fixing the problem, or are they only committed to fixing the problem if they can do it easily? What's to stop them from coming back and claiming "we don't have the resources to fix this problem"?
Sorry and in my book absolutely no excuse or reason for not coming right out and saying, "No matter what it takes, even if we have to do some manual searches, we will fix or remove these items from game.".
IMHO
You should give them a call and teach them how to develop.
I can only assume that this smart arse response is that you agree with my assessment or that you could not think of something relevent to post.
There are some basic fundemental techincal requirements and capabilities of databases, and when a database cannot be easily and effectively searched or queried, those that implemented the database failed, period.
When those in control of the database have the tools to execute the task at hand, yet the people involved allow personal feelings to get in the way of doing the right thing for customers, then the people have failed, period.
So again, what makes their database speical that looking for records when all the critierian and parameters are known or can be determined so hard?
Do they have to design a new communications satelite to make this fix work?
I can only assume that this smart arse response is that you agree with my assessment or that you could not think of something relevent to post.
There are some basic fundemental techincal requirements and capabilities of databases, and when a database cannot be easily and effectively searched or queried, those that implemented the database failed, period.
When those in control of the database have the tools to execute the task at hand, yet the people involved allow personal feelings to get in the way of doing the right thing for customers, then the people have failed, period.
So again, what makes their database speical that looking for records when all the critierian and parameters are known or can be determined so hard?
Do they have to design a new communications satelite to make this fix work?
Haha, you gotta understand they are working with a very small development team. They have other projects ongoing, so its always has been push out fix later if you got the time. They do fix major buggs after the publish youll see 12.1 and so on soon.
Hmm, well since this is a "major" fail on their part, maybe they should be pulling peeps from those other projects and fixing this pile of poo doo they created?
U know, it's called an emergency when this kinda shiz is going on.
Especially after it took them over a month to fix the entertainer hack, only to now see the same cheaters getting this hack right after the other hack was fixed, is so lame words cannot do it justice.
SOE's problems should not be the customer's problem, that is if SOE is a customer caring company? LMAO!
An update from Loche of the Dev team for SWG.
http://forums.station.sony.com/swg/posts/list.m?topic_id=978039
See last pages for his inputs.
Nice to see a real response for a change.