MagnusIlluminus wrote:
@alsted: How is the sample program in the Astares pdf incomplete? From my view, it is completed by the final criterion being "In any other situation, do this." Could you please explain exactly how you see it as incomplete?
Hi
I read it in the context of that there is one master program that all robots must folllow not that you can create your own.
From here i viewed is case (1-4) as plausible outcomes on a table, where case 1-4 maps to action A - D. Action E is then left dangling and that confused med quite a lot. As i see 4 as the catch all case, action E really seems to be out of place.
Now, from what i gather from you guys expiations there actually exists cases that not covered by 1-4 and then E is put to use.
Does that make any sense?
Any how i think that i agree with primarch, this is really open to interpretation. What I think that I should do is to define a few programs, "Attack", "Defend", "Clear objective" and hold objectice + plus mayhaps a few others. Then let robots choose from these before the game starts. That will still yield flexibility and some well know rules for how the robots play out. If i was creating a scenario i would tailor program to fit the scenario.
Cheers