Game Guides Archive
Thread: Tuesday Tips May 31st Armor Break
These Tuesday tips are turning into a "Let's point out an obvious fact that evidently for some reason the devs know nothing about" session.
SonGouki wrote:
Except that the Armor Break specials for Brawler/Swordsman and Jedi Lightsabers are busted at the moment. The lower version of the abilities are actually increasing the damage taken by the target MORE than the improved versions...
He beat me to it.
SonGouki wrote:
Except that the Armor Break specials for Brawler/Swordsman and Jedi Lightsabers are busted at the moment. The lower version of the abilities are actually increasing the damage taken by the target MORE than the improved versions...
Blimigerite wrote:
These Tuesday tips are turning into a "Let's point out an obvious fact that evidently for some reason the devs know nothing about" session.
SonGouki wrote:
Except that the Armor Break specials for Brawler/Swordsman and Jedi Lightsabers are busted at the moment. The lower version of the abilities are actually increasing the damage taken by the target MORE than the improved versions...
Really TH...what say you try to not inflame this community anymore and post tuesday tips about game features that actually work properly.
This tip being putup reminds me of the line from Attack of the Clones
"Lost a planet, Master Obi-Wan has. How embarrassing … how embarrassing." —Yoda
KnightHawk420 wrote:
Blimigerite wrote:
These Tuesday tips are turning into a "Let's point out an obvious fact that evidently for some reason the devs know nothing about" session.
SonGouki wrote:
Except that the Armor Break specials for Brawler/Swordsman and Jedi Lightsabers are busted at the moment. The lower version of the abilities are actually increasing the damage taken by the target MORE than the improved versions...
Really TH...what say you try to not inflame this community anymore and post tuesday tips about game features that actually work properly.
or better yet, rather than give us tips about skills we all know that dont work, give us info about the huge problem taht respec caused.
Thunderheart wrote:
The information is much appreciated
TH, we could probably help you a lot with more information if you could post more information about reported bugs and what you have found out. In this case you commented on this issue and we could give you feedback of what we have found out.
Message Edited by Bermag on 06-01-2005 04:15 AM
GangaWolf wrote:
This is a basic problem with just checking the code rather than testing. It is clear from testing that armor is being reduced improperly because of an incorrectly coded mathematical equation.
It is disheartening to hear all you do is ask the Dev "does the code look right?" rather than saying "we've received hundreds of bug reports on this - I know the code looks right but let's run a quick test anyway to be 100% sure." If you had spent even 10 minutes doing this, you would have discovered what all of your playerbase - that you are choosing to ignore - already discovered.
This issue highlights how you are treating bugs TH. It just isn't right - *WE* are doing your jobs for you, testing software that obviously no one tested internally - and you still choose to ignore us. For shame, for shame.
Message Edited by GangaWolf on 05-31-2005 05:09 PM
QFE.
The right way toget bugs fixed is to go sit down nextto the Dev responsible, log into a live server,/respecto an appropriatecharacterand reproduce the bug.
"Looking at the code"is the wrong way round: the dev is trying to convince you that his code is working, instead of you trying toconvince him that the actual live production server behaves in a way that differs from what was intended. And that's why 90% of bugs stick around for months and months.
Bermag wrote:
Thunderheart wrote:
The information is much appreciated
TH, we could probably help you a lot with more information if you could post more information about reported bugs and what you have found out. In this case you commented on this issue and we could give you feedback of what we have found out.
I suggest you publish a list of reported bugs and what the status are on each bug (like "Unconfirmed", "working on a fix", "Working"). I am sure you have a list liek that internal, question is however if you want to make it public (I can understand that you don't want to make it public for marketing reasons). One option would be to publish it on the correspondant forum and let the corrs get you feedback from the community. Each correspondant probably has their own favourite bugs.
You really need to improve the communication. Information need to flow in both directions. You ask use to report bugs/problems but we almost never get any feedback.
I can live with bugs taking time to fix and that you need to give priority (even if I don't as a player agree with some priorites which are made for marketing purposes but I understand you need to think about profit), but I can't accept the current lack of information from devs (which had hit an all-time low since CU beta).
Anyway, thank you for answering in this thread (and for last week about root). The comments you made in these two threads have been the most useful feedback post-cu. Please continue to do so.
Message Edited by Bermag on 06-01-2005 04:15 AM
QFE
TH, if you don't want to post a buglist for apparent reasons, could someone at SOE read the correspondants top list and give a short answer on each of them? That would go along way to calm down and please the community really.
A answer like "Working as intended", "Need more feedback", "Testing in progress", "Devs at work, "ETA on publish to testserver [date] would be great to start with, then we could get a discussion going about the bigger topics.
Yep, it hurts to try to take care of your product and customers, but if you don't you loose both, thats a real life fact.
You push the game to Live full of bugs with some crock of a PR excuse like "we need more testers so we're going to test it in Live".
I reported this bug in April before the CU went live (using /bug on TC).
I reported it again here while Swordsmen could still respec;
http://forums.station.sony.com/swg/board/message?board.id=swordsman&message.id=63159
A couple of days later the jedi found the same problem in their version, here;
http://forums.station.sony.com/swg/board/message?board.id=jedi&message.id=878009
Yet again you profess ignorance in a Tuesday Tip.
----
"I gotcha and I'm hearing you. I've spoken with the developer and looked at the code with him. The code does indeed show a higher percentage than 45%."
----
I don't really care if you've had a vision from god telling you that the code works like you think it does. Simply try it. It doesn't.
----
"I'd like to work with you folks to understand how you are seeing this number so we can duplicate it internally."
----
You already can. You have the bug reports from pre-Live. You have the correspondent system, where the issue is reported.
----
"(Sorry, but I haven't played a melee character since the CU yet)"
----
If you think this is a relevant comment then that about sums things up. You have a test server. You have correspondents. YOU DON'T NEED TO HAVE NOTICED IT YOURSELF IN YOUR SPARE TIME! Do your job.
[And now, the exact same thing I posted during last Tuesday's debacle...]
In the four most recent general posts made by you and Tiggs you have players begging that you stop adding new content and use the time to fix the damn game instead. Think about that for a moment!
Things can't get much worse. Luckily you supposedly have a system in place to start from these depths and begin doing things right. You have a network of correspondents again now (having replaced most of those who quit, mostly due to not being listened to when they told you what was happening with the CU) so USE THEM.
Have someone READ the correspondents posts. Each one of them is telling you the issues each profession has right there.
There is no need for you to post a "tip" like today's to suddenly have it explained to you where the most vital problems are.
The players know where the problems are.
The players are telling you where the problems are.
Stop adding new, irrelevant content.
Read what the correspondents write as they do your job for you.
Design fixes.
Now, stop. Don't let a dev touch a keyboard! THINK!
Now you've thought about it, start fixing it.
QFE! Bravo
UncleSecti wrote:
Unbeleivable.
You push the game to Live full of bugs with some crock of a PR excuse like "we need more testers so we're going to test it in Live".
I reported this bug in April before the CU went live (using /bug on TC).
I reported it again here while Swordsmen could still respec;
http://forums.station.sony.com/swg/board/message?board.id=swordsman&message.id=63159
A couple of days later the jedi found the same problem in their version, here;
http://forums.station.sony.com/swg/board/message?board.id=jedi&message.id=878009
Yet again you profess ignorance in a Tuesday Tip.
----
"I gotcha and I'm hearing you. I've spoken with the developer and looked at the code with him. The code does indeed show a higher percentage than 45%."
----
I don't really care if you've had a vision from god telling you that the code works like you think it does. Simply try it. It doesn't.
----
"I'd like to work with you folks to understand how you are seeing this number so we can duplicate it internally."
----
You already can. You have the bug reports from pre-Live. You have the correspondent system, where the issue is reported.
----
"(Sorry, but I haven't played a melee character since the CU yet)"
----
If you think this is a relevant comment then that about sums things up. You have a test server. You have correspondents. YOU DON'T NEED TO HAVE NOTICED IT YOURSELF IN YOUR SPARE TIME! Do your job.
[And now, the exact same thing I posted during last Tuesday's debacle...]
In the four most recent general posts made by you and Tiggs you have players begging that you stop adding new content and use the time to fix the damn game instead. Think about that for a moment!
Things can't get much worse. Luckily you supposedly have a system in place to start from these depths and begin doing things right. You have a network of correspondents again now (having replaced most of those who quit, mostly due to not being listened to when they told you what was happening with the CU) so USE THEM.
Have someone READ the correspondents posts. Each one of them is telling you the issues each profession has right there.
There is no need for you to post a "tip" like today's to suddenly have it explained to you where the most vital problems are.
The players know where the problems are.
The players are telling you where the problems are.
Stop adding new, irrelevant content.
Read what the correspondents write as they do your job for you.
Design fixes.
Now, stop. Don't let a dev touch a keyboard! THINK!
Now you've thought about it, start fixing it.
