Lt. Commander
Join Date: Dec 2007
Posts: 120
# 31
06-14-2012, 03:02 PM
Quote:
Originally Posted by Trek17
finally someone get's it

the rest of you, LIGHTEN UP. everyone know's about the issue, but calling Cryptic a fail won't get things done
Exactly! Great looking ship, and I happy to do some non-STF related activities with it until the fix comes out.

Thanks for being upfront with the issue and giving us a heads up on when the fix is due out, I personally can wait less than a day for one thing that is missing from this long requested ship. That being said, the min the fix comes out I'lll be taking it into some STFs.
Lt. Commander
Join Date: Dec 2007
Posts: 120
# 32
06-14-2012, 03:08 PM
Quote:
Originally Posted by Trek17
even if you're not gonna, i say give Cryptic a break

this was a fan-requested ship for a good 2 years... they made it, and in their excitement, gave it to you right away. are a couple of minor issues really gonna ruin that?

answer = no

Complete agreement with your statement. Besdies any new class needs a shake-down before it goes on critical missions

I LOVE THIS SHIP. Now if only I can find someone will to train a bridge officer in gravity well at the LT position I wuill be in 7th heaven.
Lt. Commander
Join Date: Dec 2007
Posts: 120
# 33
06-14-2012, 03:11 PM
Quote:
Originally Posted by Marco_Ramius
Man you guys will complain about everything. Nothing works 100% of the time, so it has a bug, big deal. I think they do a great job even if you guys complain about every little thing. If its so bad don't play, go some where else and play some perfect game. Every game has its bugs. The problem with you complainers is that you want everything now, instant fast food style and in perfect working order. its not possible with millions of lines of code. I know thats what testing is for but it does not always catch everything.

I think the new ship is great, good job
Personally I like the new ship, but I gotta chime in here.

People are absolutely allowed to (and should) complain about things they don't like. That's called feedback. If nobody complains, nothing gets fixed. Generally, people happy with the game state are less likely to post about it on the forums, that's normal.

The developers need to know the opinions of the unhappy just as much as the happy, so they can adjust their needs based on what they're hearing. The very nature of the MMO genre means that the game is a moving target with regards to what the community wants. Saying "don't play" doesn't work, because if people who are unhappy just left the game and didn't say why, the game would end up very lonely but the devs would think it's perfect.

Even if they look like they're just being angry for angry's sake, they're a necessary part of the process.
Lt. Commander
Join Date: Dec 2007
Posts: 120
# 34
06-14-2012, 03:42 PM
As I bought this ship before it was know of the Bug, I would like to suggest a slight refund of 400 CP to all who bought the ship prior to the bug being exposed, I am not mad at all, she is a great beautiful ship. Bugs happen but at 25 dollars and it not working, when it was not posted to a test server shows a draw back that should be fixed. But amazing ship I can only wait to use here in STF's
Lt. Commander
Join Date: Dec 2007
Posts: 120
# 35
06-14-2012, 03:51 PM
Quote:
Originally Posted by ddesjardins
Besdies any new class needs a shake-down before it goes on critical missions
That is the entire point of the Tribble/Redshirt servers: To test.
Lt. Commander
Join Date: Dec 2007
Posts: 120
# 36
06-14-2012, 03:52 PM
Quote:
Originally Posted by Blurr View Post
Personally I like the new ship, but I gotta chime in here.

People are absolutely allowed to (and should) complain about things they don't like. That's called feedback. If nobody complains, nothing gets fixed. Generally, people happy with the game state are less likely to post about it on the forums, that's normal.

The developers need to know the opinions of the unhappy just as much as the happy, so they can adjust their needs based on what they're hearing. The very nature of the MMO genre means that the game is a moving target with regards to what the community wants. Saying "don't play" doesn't work, because if people who are unhappy just left the game and didn't say why, the game would end up very lonely but the devs would think it's perfect.

Even if they look like they're just being angry for angry's sake, they're a necessary part of the process.
I certainly get what you are saying, but I don't see there being much of a process here. Cryptic admitted to the issue straight up and stated when it would be fixed. What exactly do the not all that descriptive EPIC FAIL! replies add in this case?

What could Cryptic have done better? More testing IMHO. On the flipside, they also could have not owned up to it, or not advised when there would be a fix, or delayed the ships release entirely. In that last scenario we would not be able to use it in STFs... or anything else in the game.

I agree that feedback is important to the devlopment and enjoyment of STO, but if it is not constructive (evil overlords, personal attacks on devs or other players, EPIC FAIL and the like) or proportonal we run the risk of not being listened to in the future.

Just my 2CP.
Lt. Commander
Join Date: Dec 2007
Posts: 120
# 37 List of bugs
06-14-2012, 04:11 PM
So there are multiple bugs that need to be addressed with this ship:

1. can't take it into STFs
2. some have reported the console can not be used on other ships
3. can only use type 4 windows
4. some have reported scorpion and stalker fighters can not be used on it
5. phased polaron cannons can not be used on it

Anyone else have anything else to add?
Lt. Commander
Join Date: Dec 2007
Posts: 120
# 38
06-14-2012, 04:12 PM
I see now that the PDS is only usable on the escort carrier. Due to that, I will not be buying this ship. Despite how nice it is, I will save my money.
Lt. Commander
Join Date: Dec 2007
Posts: 120
# 39
06-14-2012, 04:15 PM
Quote:
Originally Posted by Marco_Ramius
Man you guys will complain about everything. Nothing works 100% of the time, so it has a bug, big deal.
Typically I would agree, but this is an End Game ship that can't do the End Game content (STFs), It is an Escort Carrier that can't use devices EVERY other Escort AND Carrier can use (Consumed-on-use fighters), combining the parts of the new ship with all the other variants makes for a crappy looking ship because of the size difference and the fact the parts don't line up. Not to mention that there are TWO test servers and it didn't make an appearance on either of them at all to actually test this thing (why do we have test servers again?). If there wasn't enough testing by the devs to notice it can't be used in STFs how did they test it, or did they?

Don't get me wrong, I am glad they finally added this thing, but a little testing would go a long way.
Lt. Commander
Join Date: Dec 2007
Posts: 120
# 40 EPIC Whatever - Reality Time
06-14-2012, 04:22 PM
As a software UX designer/developer I have been part of major releases and patches on server-side software systems for the better part of a decade. These systems have 500,000+ active users hourly, so ensuring that QA catches issues is a financially motivated process. Think: your income will stop if this fails. Not everything is perfect though, and occasionally something slips through.

We call these 'unintended consequences' or as developers say 'undocumented features'. :

When these are discovered too late (ie customer experiences the issue), the question is ALWAYS financial. Do we live with it until a patch can be scheduled - or - do we roll everything back to the pre-update. In the case of an MMO or our software (security related), server roll-backs are insanely expensive due to downtime.

A patch, usually with 24-hours notice is fine for non-mission-critical updates. MC or Mission Critical constitutes a lot of different scenarios, but it always boild down to affecting your income.

Each time we get a new set of unintended consequences, we rewrite our launch check-list. That's right - we use an old fashioned check-list to ensure each new element doesn't impact another. For those of you who do not understand software - it isn't one giant program, but thousand of separate elements that play together. Now see that model duplicated across many interconnected servers, you can visualize the potential for error. Yes, we do have tools to track everything, but to be honest sometimes one little glitch can have a cascade failure across the system.

For some companies that little glitch can come from something they didn't expect: routine server OS updates, hardware with defective software, or even an overzealous developer who added something at the last minute. I've experienced it all and YES if I could avoided it, I would have.

Sometimes in the rush to deploy, the development team is pressured to deliver by the date they themselves have come up with. Never let a developer select the date. Let him propose it, then double it for good measure. (I expect a lot of flack for that comment, but reality bites).

Sometimes in the rush to deploy - little things we assume will work, we don't bother to test. In this case ti might be something as simple as a flag in a dbase enabling access to STF's or fighter types. You can't manually edit the dbase and propagate the change on multiple servers, so a patch is scheduled.

It's not the end of the world. Nobody dies.

If it happens again, then look to the QA team with a steely gaze, and carry a baseball bat in the office.
Closed Thread

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


All times are GMT -7. The time now is 03:45 AM.