|
||||||
|
||||||
|
||||||
At SIGCSE 2007, Greeps invaded for the first time, looking for tomatoes. Two years later, they were back. At SIGCSE'09 and JavaOne'09, this competition ran for conference attendees. Now, the material is available here for those who want to run the competition themselves. The flyer with genereal information: greeps-flyer-2009.pdf The scenario to hand out: greepsreturn.zip A verison of the scenario that includes the "House Greep", for purpose of running the competition, is available on request to instructors (email Michael Kölling). This verison is for the competition organiser only, and should not be handed out to participants. |
|
RulesRule 1: Only change the class 'MyGreep'. No other classes may be modified or created.Rule 2: You cannot extend the Greeps' memory. That is: you are not allowed to add fields (other than final fields) to the class. Some general purpose memory is provided. (The ship can also store data.)Rule 3: You can call any method defined in the "Greep" superclass, except act().Rule 4: Greeps have natural GPS sensitivity. You can call getX()/getY() on any object and get/setRotation() on yourself any time. Friendly greeps can communicate. You can call getMemory() and getFlag() on another greep to ask what they know.Rule 5: No creation of objects. You are not allowed to create any scenario objects (instances of user-defined classes, such as MyGreep). Greeps have no magic powers - they cannot create things out of nothing.Rule 6: You are not allowed to call any methods (other than those listed in Rule 4) of any other class in this scenario (including Actor and World).Please do not publish your solution anywhere. We might want to run this competition again, or it might be used by teachers to run in a class, and that would be ruined if solutions were available. |
|
maintained by Poul Henriksen and Michael Kölling. |
![]() |