The Dink Network

Sorry guys, looks like i broke the beta testers roster. (i need a roster to test the roster

Actually, i think some smart cookie (co-worker) has set mysql to run in batch mode by default, without telling me, which could mean that all roster operations are delayed untill up to 23:59:50 after you submit them (in a worst case scenario). it still seems to work, as in it sends emails, but i may have to re-code a whole heap of that stuff...

Don't worry, in my opinion, it sucks. I think you should submit you file discription to the database, and everyone could view it. If someone wanted ot beta the file, then they could 'submit' themselves to the author to author so see if they are eligable to beta test the file. Also make it so people can be selected by the author to test.

--WC

: Don't worry, in my opinion, it sucks. I think you should submit you file discription to the database, and everyone could view it. If someone wanted ot beta the file, then they could 'submit' themselves to the author to author so see if they are eligable to beta test the file. Also make it so people can be selected by the author to test.

: --WC

thank you!!

seriously, do you know how many times I have tried to get some feedback about this from you people? I'm not trying to be defensive of my program or anything, because i agreee, it does suck teh motherload. for that very reason, today i am completely recoding it, from scratch. Anyway, the coding sucked, and i can now make a much better job of it.

BTW, before i broke it, the projects WERE added to a database, and so were the users. and yes, i will include your additions.

thanks!

Whoa, I'm glad you took that well. If someone told me WDE or another program of mine sucked , they would be eating the source code print outs

--WC

: Whoa, I'm glad you took that well. If someone told me WDE or another program of mine sucked , they would be eating the source code print outs

: --WC

hmmm... so why did you say it?? not that i care, I'm half way through coding another version, from scratch, however, i have a problem:

i under stand that choosing your beta testers is important to at least you, but, if i sign up to test something, i would like my choosing to be at random.... i dunno, maybe it's just me, what do you guys thing?

err, the random thing is kinda...odd, dunno why I think that. Oh well, that why I suggested the part about being able to 'request' to beta things.

--WC

: err, the random thing is kinda...odd, dunno why I think that. Oh well, that why I suggested the part about being able to 'request' to beta things.

: --WC

ok, will do.

I just got myself warcraft 3, and I'm up to chapter 6 (humans) allready, in only half a day!! this may slow my development of teh BETA testing roster a bit

I prefer to choose my Beta Testers. Beta testing is not just playing the game and reporting a few bugs, it's a skill in itself - one I know I'm not good at doing. You have to be able to replay and replay the game - being objective as you can each time - well that's what I want in a beta tester. Plus I want their feedback - specifics about what they hated, what they liked. Pilgrim's Quest was shaped by the Beta testers in many, many ways.

There that's enough of my rant.

: I prefer to choose my Beta Testers. Beta testing is not just playing the game and reporting a few bugs, it's a skill in itself - one I know I'm not good at doing. You have to be able to replay and replay the game - being objective as you can each time - well that's what I want in a beta tester. Plus I want their feedback - specifics about what they hated, what they liked. Pilgrim's Quest was shaped by the Beta testers in many, many ways.

: There that's enough of my rant.

i agree, but:

thats all fine and dandy, but does this mean that you (pl) will not select testers who haven't tested before?? surely someone testing your file is better than no one testing your file. I agree that BETA testing is a skill, but how can new people learn, if you don't give them any experience??

I suggest a combination of teh two ideas:

the developer can select a set number of testers he/she wants, and then the project descriptions are sent out to another set of testers, so new tester scan get some experience.

what do you think?

I think a good betatesters also looks for bugs in d-mods he's not supposed to test. In my case, it's a (bad?) habit to try the hardness around houses and try all possible answers to a question, etc...

If you think you're good and you want to get a chance at betatesting, you should send the bugs you find in d-mods to the author. Then, if he thinks you're good, you may get the opportunity to test his or her's next d-mod.

: I just got myself warcraft 3, and I'm up to chapter 6 (humans) allready, in only half a day!! this may slow my development of teh BETA testing roster a bit

Excellent game, that. It's rather easy, though, so you'll be finished with that and back working with the beta testing roster in no time. Maybe.

Kyle, how many d-mod author make more than one d-mod? Yeah..

--WC

: Kyle, how many d-mod author make more than one d-mod? Yeah..

: --WC

Okay... If you think every man who subscribed himself for the betatester roster is actually a good betatester, forget it. I was just pointing out a good way for authors to distinguish between the good and the... less good.

: I think a good betatesters also looks for bugs in d-mods he's not supposed to test. In my case, it's a (bad?) habit to try the hardness around houses and try all possible answers to a question, etc...

: If you think you're good and you want to get a chance at betatesting, you should send the bugs you find in d-mods to the author. Then, if he thinks you're good, you may get the opportunity to test his or her's next d-mod.

hmm... good point.