 |
|
ashbery
|
|
With a month or 2 before release its only going to be bug-hunting anyway.
|
|
|  |
 |
|
Imhotep
|
|
quote: Originally posted by Nadexander
This is some kind of joke right? Only 25 beta testers and theyre making a contest out of it? |
Well, since this contest has been mentioned both on the official MOO 3 site (http://moo3.quicksilver.com/main.htm), and on their official forums (http://www.ina-community.com/forums...threadid=207203) I doubt that it's a joke.
As for only 25 beta testers that should read, 25 public beta testers. IG usually carries out most beta tests in-house therefore the 25 are in addition to the in-house team at IG (and possibly some people at QS.)
quote: This is clearly a misguided PR gesture, rather than attempt to get real improvemnets in the game. QS's attitude must be that they dont want to make any real changes so theyre just gonna hand it out to a few lucky fans and claim that it was "publicly beta-tested". |
Again since IG rarely if ever engages in public betas I agree with you that this is a PR "gesture". Though I don't believe that it is "misguided". It's about time IG began the PR machine rolling on this game.
quote: P.S. I hope at least one of these betatesters will have the decency to put their copy on kazaa so that we can get a chance to give some _REAL_ feedback to QS gives us all the old hump'em and dump'em. |
Well, I hope not. Such attitudes should make it apparent as to why IG prefers in-house testing as opposed to public testing. Especially after the "Kangamoo" incident QS and IG are a little skittish about placing this beta in the hands of the wrong people.
|
|
|  |
 |
|
system370
|
|
Wales - UK
Mar 2002 time: 05:22
|
|
quote: Originally posted by ashbery
With a month or 2 before release its only going to be bug-hunting anyway. |
Agreed, it does not bode well to begin beta testing so close to the release date. Even more reason to delay purchase until after a patch or two have been release - in addition to saving a few bucks.
|
|
|  |
 |
|
Master Marcus
|
 |
Quebec, Canada
Jan 2000 time: 00:22
|
|
quote: Originally posted by system370
Agreed, it does not bode well to begin beta testing so close to the release date. Even more reason to delay purchase until after a patch or two have been release - in addition to saving a few bucks. |
Well, for an anticipated "december" release, that means two months+ for the beta testing which is a reasonable and average time to expect a "good beta" at release, highly playable with minor bugs: face it, just like most other games. Of course the remaining bugs will be fixed, every major game is patched several times after release. In fact, expect 4 patches ( let's say, an additional 9 months- one year ) in order to have a more polished game. Just like SMAC, Civ III.
|
|
|  |
 |
|
Darks
|
|
I beg to differ with that comment, I am an Avid gamer and I have been playing Computer games for the last 15 yrs; I have played each of the MOO games at least 3 times over. I resent any remarks that the beta testers don’t know jack about playing game and are drooling over the game just to play it. I have been on countless Betas. In fact I am also on the Beta for Starfleet Command 3. So please keep your opinions to your self. I for one know how to Beta test.
I know how you feel, those of you that did not get choosen, I have tried to get on several Betas in the past and have been passed over to. So please keep the Beta tester bashing down to a minimum.
-Dark
|
|
|  |
 |
|
Darks
|
|
I was responding to the original poster of this message.
-Dark
|
|
|  |
 |
|
Xentax
|
 |
North Carolina
Apr 2002 time: 00:22
|
|
quote: Originally posted by Nadexander
Actually my opinion comes from the fact that I am a software QA (quality assurance) engineer. Most developers and many engineers who do qa (general engineers hired into qa as opposed to those with qa specialties) are NOT very good at software QA. In fact they are notoriously BAD at it. Now if this is what programming professionals do I simply _cringe_ at what a small random sampling of the game playing public might do. Really. |
I'm a software engineer, so I've got 2 cents to add on this issue (naturally). I agree with you, to the extent that I'll say that "your mileage will vary" when it comes to using anyone not specifically trained/experienced in doing QA.
Some people we've had doing system testing, who did NOT come from a QA, or even an engineering background, did a fantastic job testing -- they were thorough, they tried things the implementor didn't think of, etc.
So, random testers, IMHO, aren't "that much" more of a shot in the dark than 25 hand-picked people would be. It's also more likely to get a good cross-section of skill and interest levels. The game won't do well if only diehard fans enjoy it. It should *make* diehard fans of people new to the game, or even new to the genre.
The testers will need direction, to be sure -- they need to know that they should try *literally* anything they can think of to break the code. But you can't always use professionals to test, because it won't just be professionals using the final product. Face it, at the end of the day, people who use computers for a living reach a level of familiarity, at which they stop trying the kinds of things that people new to, or less comfortable with, computers are liable to try.
Things like "Gosh, all these extra files, I bet they don't do anything useful. I'll just delete them." Just how well will MOO3 "fail" when some of it's critical files aren't found? Only one way to find out from our side of the fence...
|
|
|  |
 |
|
system370
|
|
Wales - UK
Mar 2002 time: 05:22
|
|
Can I ask who you think make the best Moo3 Beta Testers?
Game Players? Programmers ? QA testers ?
What about people who have played Moo2 for 6 years and can name 20 bugs that still remain in Moo2? I bet none of the 25 chosen could detail the outstanding bugs in Moo2.
Just last summer a Fellow Moo2 player discovered a bug with Android workers - A new bug or an old one re-discovered I don't know, but IMO , it's those sort of people that should be doing the Beta testing - proven bug finders with a passion for the game.
|
|
|  |
 |
|
danminster
|
|
I think the only thing required to be a decent beta tester is to be a critical "thinker". So long as you are trying to push the game with different approaches, etc., I think you should be able to catch different bugs that pop up. This is an exercise that is close to being able to proofread a manuscript.
I don't believe that it matters if you are a game player, programmer, or a QA tester, just as long as you know what you're doing.
I also think having too much passion for the game can have an adverse impact on one's ability to search through the game for errors.
|
|
|  |
 |
|
kallisti_dk
|
|
Remember, we don't know how many internal testers Infogrames has, and how long they've been testing the game.
|
|
|  |
 |
|
Ozymandous
|
 |
Atlanta, GA
Aug 2001 time: 00:22
|
|
quote: Originally posted by Xentax
Well, people remember Sid Meier games as such.
It's one thing to be working on an expansion that adds major features (that were originally to be in the initial release...); it's another to keep patching in a timely fashion in the mean time. They *have* patched Civ3 a few times, but I've heard too many complain that they were slow in coming, or insufficient, etc. |
If you've heard too many complain because Civ III wasn't what they wanted then you've probably spent too much time on Apolyton. There were bugs in the initial release to be sure, air superiority as a major one for example, but issues like corruption, etc, were not bugs, IMHO.
quote: My real beef with Civ3 is that it was *too* far off in the first release; it should never have gone gold with corruption that badly broken, for example. That sort of thing deserves an almost immediate patch, and it was ... weeks, maybe even a month or more, before the *first* patch to deal with corruption came out... |
A "bug" is when something is broken in the game outside of the players ability to adapt. With air superiority, no matter what the player did it wouldn't work. With corruption, because you can't build 200 cities half way around the game world, doesn't mean it was "broken" merely that people wanted the game to be as the old versions had been, not have to change their play style.
What do you get when you have people who refuse to change how they do things because 'that's how it's always been done'? The general Civ III board here at Apolyton! lol!
When a game company is faced with the dilemna of a feature that works as it is supposed to but some (annoying and very vocal) people don't like, then you should expect a little delay in the company trying to figure out how to 'tweak' the feature so it still does what they want but also quiet's down some of the biggest 'complainers'.
Look at it this way... You may not have liked Civ III as it was initially shipped, but what shows that a game was shipped too early, having a patch come out 2-4 weeks after it hits the shelves or having a patch available as soon as the game hits the market like Blizzard has done in the past?
Oh, by the way, speaking of Blizzard, I guess none of the people who sing their praises ever played Diablo2 and went through all the see-saw cycles when the company released patch after patch that completely re-worked the game mechanics every time and rendered old characters as useless? You want an example of a company that releases stuff fast and then has to constantly fix their mistakes, look no farther than Diablo2 and Blizzard.
Let's just hope that PtW doesn't completely break and unbalance Civ III as LoD did with Diablo 2.
|
|
|  |
All times are GMT. The time now is 05:22. Apolyton Time is 00:22. |
top of page
|
|
|
Forum Rules:
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is ON
vB code is ON
Smilies are ON
[IMG] code is ON
|
|
|
|
|
|