[size=150]Update (12th Dec): Thread Closed, Emails Coming Today[/size]
I thank everyone in here for their application, if you either haven’t received a PM with the two questions, or you haven’t answered them yet, it is too
late now. I have sent out a confirmation PM/email to all who “passed” and will make it into the beta. An email with the details on how to proceed
will be sent out today to the address you’ve signed up with to these forums.
The beta testing subproject starts on the 14th, and you will gain access to the beta forum today (12th) to read up on the rules and get set up in our
testing structure that is the POMMS system. Also, if you aren’t already, I’d like you to become expert engine designers in the latest (public) version,
as we will start out with some scenario balancing and need your skills there.
The thread is now locked.
Cheers!
/Robert
[size=150]New Testers Needed[/size]
We have made some great progress on the engine designer and are about to release (on 5th December) the next major update that is the Revamp.
Right thereafter we will start marching towards our next main goal: “Forced Induction & Advanced Test Mode”, which will mark the end of a
long series of Engine Designer updates.
For this next goal/subproject we will need some new blood in the testing team and this is a call for new beta tester candidates. Now if you think we
run the normal “join, fool around, put away” beta like most other studios, you are mistaken…
[size=150]The Testing System[/size]
We are working in a new system nicknamed POMMS (Project-Oriented Modular Motivational System) in which you are given “points” that add to your
“power level” for all the work you do for the team. Tested a scenario? Gives a point. Reported a bug? Gives a point. Completed a quest on the quest
board? Could give many points! While you are required to achieve a certain number of points to stay in the testing team, those that exceed
expectations will be rewarded accordingly (will get their place in the game credits and receive a special forum status).
You are required to do (on average) about 1h of testing per week (4 points per week) during at least a 8-16 week long period (one subproject).
If your power level was one of the best among the testers during that round, your score is reset and your name will make it into the game credits.
Score carries over between subprojects if not reset, so someone who does solid work reaching minimum score over several subprojects WILL make
it into the reward ranks eventually.
[size=150]So Here is the Deal[/size]
[size=120]Requirements:[/size][ul]
]You have preordered Automation./:m]
]You are willing to follow the rather strict testing rule set and work on bug hunting, engine testing as well as new scenarios./:m]
]You are willing to document your findings in a detailed fashion in the tools provided (Pivotal Tracker & Online Balancing Spreadsheets)./:m]
]You know that “testing” does not mean “just playing around” and is not fun all the time./:m]
]You can spend more than on average 1 hour per week on testing./:m][/ul]
[size=120]Application:[/size][ul]
]Write one post in this thread why you are interested in taking part in this./:m]
]If we deem your application both reasonable and sincere, I’ll PM you 2 questions you’ll need to answer./:m]
]If your answers are satisfactory you will be accepted into the beta and welcomed to the team./:m][/ul]
If you like the sound of this, you are most welcome to post down below! Also, be honest. We don’t need people that just play around. Your help
would be greatly appreciated, and will make Automation a better product in the end - and the consequences of that should be to everyone’s
advantage!
This invitation to join the testing team will remain open until the Wednesday the 12th of December. Post before then to be considered. 
Cheers!
/Killrob
).
).