Tester

[Nitro]

I do not have what it takes to do any modelling etc so if i can i atleast want to contribute with betatesting.
Playd PT/CT so think i should be able to se how the game should work.

You know where to find me...

[MacBryce]

Happy to see some known faces around here! For the Sheep! ;D

Here's the standard message that I post below every sollicitation. :D

Thanks for the offer. Check the site to stay up to date. When enough people have signed up, we're going to assemble the actual team. In the meantime you can chat in the public discussion about the game. Don't forget to spread the word. We still need more developers.

[LiVe.To.Di3]

yes same with me so i would just like to actually help with the game itself when you guys think you are ready to let the testers see all the glitchtes etc.

[Cyntrox]

Here's the standard message that I post below every sollicitation. :D

You didn't post it in mine >:(

[Overstatement]

By the time UT3 comes out, you guys could have already learnt C++. Are you guys dedicated enough to do that?

[frvge]

Even if you have a talent for abstracting, a few months will only teach you the basics and not the subtle things. And we need some more experienced people than that.

[Overstatement]

I think the majority of programming is debugging the damn thing and a lot of those mistakes (after lots of compile-time errors) are simple "almost correct" things like adding stuff when you're suppose to be adding two things which can be debugged by someone (or an army of someones) who really only know half the language and the programming structure of video games like entities and bounding boxes.

RUN-ON SENTENCE!

[frvge]

Which is why I am additional programmer. Definately not good enough to be lead. Or at least in that area yet.

[Overstatement]

We still do need people to actually code stuff which you could do. The folks that don't know C++ as well can debug until they get a greater understanding of it. There is no known limit to how many people can debug as there hasn't been a game created that didn't have a single bug (is that a double negative?)

[frvge]

I just read a paper/study which says that a small team performs better than a large team. While the large team costs more, takes relatively more time because of more bugs and the decrease in actual time is neglectable.

[Overstatement]

I'm not saying they should be part of the team, they're like beta testers for code. I'm suggesting more of a peer review of code to make sure it's bug free.