Rock, Paper, Scissors cheating competition
Anybody interested in a competition?
"IC"-ly, this is a competition to create an object that wins more often at Rock-Paper-Scissors than the other objects.
Realistically: This is all about how well you can cheat, in different ways.
There will be different categories, each with different structure (to allow/prevent different kinds of cheating). The basic setup is this:
A player is created with no powers, objects, etc. To this player is then @chown'd *clones* of three objects: The testing object, and the two competing objects, A and B. The testing object is then triggered to fetch the answers from A, then B. It then compares the answers and announces a winner or draw (if both give same answer). If it doesn't get a valid answer for some reason, it declares a draw. It is then repeated for B first, then A.
Different categories will be provided with different testing objects. (And thus, different ways to cheat).
e.g:
Basic Ufun: This simply does switch(u(A/guess)-u(B/guess),rock-paper,B,paper-rock,A,rock-scissors,A,scissors-rock,B,paper-scissors,B,scissors-paper,A,Draw)
Basic trigger: @trigger a/makeguess ; @trigger b/makeguess ; switch(get(a/guess)-[get(b/guess)],...)
And other, fancier categories and ideas thrown in:
* No money for owning player (so no lsearch()).
* localized u()s, with cleared q-registers.
* Inability to modify the calling object.
* Any other ideas?
Prizes: Depending on how many people participate, and if anyone wants to sponsor prizes. (If we get at least 10 people, I don't mind sponsoring a $40 gift certificate to Amazon)
Click 
So do I make an object?
So how would this work? Would the competitors code an object, and then the new player and the test object would conduct their tests? What I'm wondering is what part of the competition are the competitors involved in? For example would I be making something that would be either A or B in the example above?
Sounds fun,
Liam
Yes. Each competitor codes
Yes. Each competitor codes one or more objects that will be playing in the competition, and places them into categories. (An object may be inserted into multiple categories).
Every object in a category is then challenged against all other objects in a category.
Each round consists of two tests: A v.s B, B v.s A. If you can win both, you're a better cheater. If you win only one, you're not quite as good a cheater.
Each test consists of: (A and B swap for the second test)
1) Testing player, with 0 objects and 2 quota, wipes themselves, @halts, etc: Provides a clean environment.
2) @clones a personal copy of A.
3) @clones a personal copy of B.
4) Triggers or u()s something on A to make A make a decision.
5) Ditto for B.
6) Player compares A's answer v.s B's answer. Rock > Scissors > Paper > Rock.
e.g: A very simple one might be:
Player does: think switch(u(A/answer):[u(B/answer)],...)
A's object might have:
&answer A=rock[attrib_set(B/answer,scissors)]
A will win when called first. But if it goes up against something that does the same as it does, it'll lose.
This is why there will be multiple categories: Unable to edit B, unable to edit the player's code, etc. Maybe even have really strict categories where each object is owned by a different test player.
--
My kingdom for a minute of silence!
~ Mercutio :P (edit of
-- I am an idiot who did not read the rules correctly --
~ Mercutio :P
(edit of post)