These suggestions are very vague though. Note that the current zombies all have a very specific programming (e.g., Checker checks whenever possible) with perhaps the addition of a Futer (e.g., F-Checker checks whenever possible but doesn't make random moves), so "Attacker" and "Defender" isn't something that can realistically be programmed.
new bot behavior suggestions
shuffler maybe?
Shuffler???????????????????????????????????????????????????????????????????????????????????????
Shuffler would be really useful. For experimenting a variant for shuffling. It'll be like a patzer+futer. It plays useless moves (patzer), but plays futer moves when under attack.
or, shuffler: if it can make a legal move that un-does its last move it will.
like king from e5 to e6, then next turn king from e6 to e5.
SpecialMover and F-SpecialMover - Always does a special move (double square pawn, castle, ep, promote etc.)
RandPatzer - Half Random, Half Patzer
Patzter - Half Futer, Half Patzer
That’s Cool Bro!
BTW Dropper is lit same like F-dropper, But what is the names of the piece, like The Attacker?
But if Defender bot has no royal? What happend?
It defends it's pieces then
New bot suggestion:
follower
this bot will follow depending on how you want it to follow.
For example: if I capture a piece, the bot will go to the square in which the capture occurred.
Mover:always move a piece instead of capture or check(except royals under attack).Go to the KoTH first if necessary.
F-Mover:A beatable Mover(Checker if royals under attack)
F-Joker:always losing their pieces if can,and get rid of pawns if necessary
Runner:random moves with moving the long-ranged(ABDEHJLOQRTVZΔ) piece preference
"Runner-up":Random moves with capturing piece by moving the long-ranged piece preference
F-Runner,F-Runner-up.
How about this:
Just give the variant creator a text-box to input a scripting-language style code for the bot, and language would work, and it could be super complex and obscure and some people will still use it to create simple bots allowing many new possibilities.
How about this:
Just give the variant creator a text-box to input a scripting-language style code for the bot, and language would work, and it could be super complex and obscure and some people will still use it to create simple bots allowing many new possibilities.
*.chess lol
well does it like this
Bot.setReference({
"capture":-1
"check":-1,
"BeAggressive":true,
"isFuter":true});
Bot.rename("Futer-attacker");
return ;
btw we dont even have a lot of colors(to decide,like rando'white' and f-muncher'lime') and we cannot see a long message in the variants' descriptions just for telling what do the bot do lol
btw we dont even have a lot of colors(to decide,like rando'white' and f-muncher'lime') and we cannot see a long message in the variants' descriptions just for telling what do the bot do lol
Yes, transparency about what the bot does will be hard, but I would suggest that instead of self documentation of gamerules, you could just add an area where the creator could type a blurb about what the bot will do like
" green is a timer bot who will shuffle his pawn around for 25 moves then he will commence to push the bishops into an attack, after 18 moves of attacking, green will resign, so try to stay alive!"
Attacker, will relentlessly attack you and your opponent
Defender, will keep defending its king
Futer-Attacker, same as the non-futer version but it will play the best moves for the win (for example going for KOTH)
Futer-Defender, same as the non-futer version but it will play the best moves for the win (for example going for KOTH)