Scratch

How exactly are we going to win if we can't even alter the movement scripts (which don't work for the Playerbot)?

@Mayhem

IMHO I think it would be a lot easier on the coding if the bots did not have a black edge to them - would you consider removing the black except for where strictly necessary e.g to join the outlying extremities to the main body

regards

Simon

I want to play!

eyra

1) S65 - see simplescratch's response.  Playerbot has no movement script, it is up to you to create one.  That's pretty much the essence of the competition, in fact.

2) If practicebot has two identical scripts, that is indeed a bug.

3) Vis the black outlines, I was planning to add black edging to the arena and make it a rule that all bots must be scripted to not allow black to pass through black, so they can't go off screen and can't pass through each others bodies.

I'll keep the colour-coding on the walls as well as a black border as it will give a bot some idea of where it is, possibly.

4) good idea about the costume, but to keep it even simpler I'll just hide the loser 

Oops! I misread the rules. Time to return to working 

eyra

Re 2)
"if 2 identical scripts - indeed a bug"  ???

I think something has been lost in translation. :-)

In the version I've downloaded, there are 2 health reduction scripts - one of which has a broadcast endbattle at end of loop - other doesn't.

Are you saying this is deliberate - if so - could you explain the need for the 2 scripts please :-)

3) Black outlines
I'll try to make a better case :-)

With the different coloured sectors and parts - you've made it possible to detect the relative angles of the bots to each other but the black boundary around all the parts of the bots just gets in the way of this detection and increase the coding complexity .

New suggestions
Start bots off further apart - preferably in mirror image positions and directions (with slight random element to prevent automatic knowledge of others position) so as to prevent any advantage in a tournament due to initial start position.

I also feel that movements/direction changes should be limited otherwise bots will be able to do completely unrealistic movements which would not make for good viewing :-)

I think that what you might need is a system of people being able to get their bots to you privately so you can decide whether you need to modify your rules - if people post their bots publicly long before closing date/time then I think others might "borrow" them :-)

regards

Simon

You could create a hotmail account and just use that for the tournament - (I'll set one up for you if you'd like to save you effort :-) )

Rule clarification is a lot better (I'd used point in direction myself - hadn't thought of not knowing opposition name :-( )

I still feel that being not restricting max movement will cause issues :-(

regards

Simon

Last edited by SimpleScratch (2007-08-05 11:15:19)

Bot coding proceeding but I'm having a bit of trouble understanding the "colour xxx over yyy" block :-(

I've come to the conclusion that it means if any of the sprite's pixel of colour x is on top of (or underneath!) any pixel colour y of another sprite then result is true otherwise its false.

But am I right????

regards

Simon

Last edited by SimpleScratch (2007-08-06 14:42:45)

Aw man, why can't we make our bots play any sounds??

_Dragon_MC_ wrote:

By the way Mayhem, can we use "change x by " and "change y by " blocks? And if not, why?

No, because I want robots limited to moving forwards and backwards, and rotating, only.

I looked a bit closer at the rules a I saw you don't allow distance to or point to target. I realize that it would take a bit longer for you to switch all  the targets but really without being able to gather any data on your opponent the best most people can do would be to make a bot that wonderers around aimlessly until it hits it's target. If you allowed distance to and point to blocks people could make their bots look like they are trying to hunt the other bot down instead of just wandering. So please loosen up the rules just a little bit 

PS: There might be other ways to judge robots. You could put the user in control of a little player who tries to shoot down the diffrent kinds of robots and the robot project with the most love it's wins.

Last edited by archmage (2007-08-08 02:33:55)

Archmage - at short range there are ways for your bot to sense the enemy.  The intellignece of its patrol route when not sensing an enemy and its behavior when it does, are the programming challenges of the game.

Checking the code of a specific enemy and programming to exploit it may not be such a good tactic, as in the heats you may not battle that bot.

Last edited by Mayhem (2007-08-08 04:13:51)