Welcome to FactoryCorp! Despite how the company name suggests we are specialists in production, we have a lot of trouble manufacturing goods to specification This has lost us so many customers that we are on the verge of shutting down. We have hired you to be our first and only quality control personnel. This company's future rests in your hands, though it will only last for so long. In the mean time, good luck! Regards, The C.E.O.
Controls: All controls are used when the target product is in the red box. Left click - reject product Right click - approve product
The concept is nice, but this game needs a better tutorial. I had to lose a few times before I understood why I was losing.
First of all, it's not clear if the requirements are combined by an OR or an AND. At first I thought that if the requirements where "color: blue; shape: diamond" I needed to accept all blue diamonds, while I actually needed to accept all blue objects and all diamond shaped objects.
The other problem I've had was with some of the classes. For example, when someone starts playing, they have no idea what a "normal" sized object is. It would be nice to have an example of each size class on the tutorial for this.
Finally, I feel that the "feedback sound" (the one that tells you if you made a mistake or not) comes too late, so its hard to find out what was the cause of your mistake.
Nice idea - I think the execution could be made a bit friendlier.
A tutorial level would help a lot - where there was no winning or losing, but if you made a mistake it explained how your decision violated the checklist.
First of all, it's not clear if the requirements are combined by an OR or an AND.
At first I thought that if the requirements where "color: blue; shape: diamond" I needed to accept all blue diamonds, while I actually needed to accept all blue objects and all diamond shaped objects.
The other problem I've had was with some of the classes. For example, when someone starts playing, they have no idea what a "normal" sized object is. It would be nice to have an example of each size class on the tutorial for this.
Finally, I feel that the "feedback sound" (the one that tells you if you made a mistake or not) comes too late, so its hard to find out what was the cause of your mistake.