SurvivorBots: Tribal Warfare (Submit your Bots!)

[Blackberry]

SURVIVOR BOTS

Please see

POST #60

for SurvivorBots: Tribal Warfare.

Welcome to SURVIVOR BOTS! Create a bot and see if it can survive the Survivor adventure! This first season will be a trial version to test the basic mechanics, so have fun! This thread will be locked until I receive the nine bots to participate in the game.

Once the first nine bots have been received I will unlock the forum and reveal the results of the game! At that time the game and idea of SurvivorBot will be open for public discussion to further discuss the future implementations of SurvivorBot. In the mean time, please do not discuss strategy with others.

[THE BASICS]

The game is quite simple, anyone that wishes to participate may send in a bot to partake in the Survivor game. For the first season, the first nine bots to be sent to me will be accepted. The bots will partake in seven rounds of Immunity Challenges & Tribal Councils, one bot will be eliminated at the end of each round.

Immunity Challenges:

Each bot will participate in the Immunity Challenge. The bot that wins the Immunity Challenge will receive Immunity and may not have any votes cast against it.

Tribal Council:

Each bot will cast a vote for another bot. The bot that receives the most votes at Tribal Council will be eliminated.

Final Two:

When only two bots remain, the first seven bots voted out will form the Jury and each cast a vote for which bot they believe should win the game.

[BUILDING YOUR BOTS]

Submit your completed SurvivorBot to BLACKBERRY via PM. Each bot must have three components to it...

(Component I) Stats:

Each bot has up to 60 stat points to divide among three stats; Strength, Speed, and Smarts. These three stats will be used to determine the winner of Immunity Challenges. Select the stats of your bot wisely, as they may not only be used for determining who will win challenges, other bots may use your stats as a factor when they select who they are voting for. You are not required to use all 60 stat points. You are allowed to give 0 points to one stat field.

(Component II) Strategy:

Each bot must come with a program that dictates what it will do at Tribal Council. You can develop an extremely simple program, or a more complicated program. Although you may make a program as complex as you'd like, it must still be able to be understood and have on clear action. Your bot has access to a lot of data to determine it's vote (the list of

Available Data

is listed below). It is up to you to decide how to program your bot to best ensure it's survival. Your strategy must also instruct how your bot will vote in the event of a tie.

(Component III) Jury:

In the event your bot is eliminated, it will take part in the jury process. Please instruct how your bot will vote in the event it sits on the Jury panel. Jury members may want to consider which bot voted out most of the jury members, or how many times that final two bots voted for your particular bot. Please see the below section on

Available Data

for more information on available criteria.

For the first game, you may choose to name your bot. If you do not name your bot, the moderator will randomly assign a name to your bot.

[IMMUNITY CHALLENGES]

The bots will participate in seven Immunity Challenges throughout the game. The bot's

STATS

will determine who which bot will win the Immunity for that round. The stats you select for your bot will be of vital importance when determining which bot will win the Immunity Challenge. To better assist you in programming your bot's stats, as well as to assist you in formulating your strategy, you will be told of all of the challenges in advance.

Spoiler: IMMUNITY CHALLENGES

Immunity Challenge #1

The bot with the

highest strength stat

will win Immunity. In the event of a tie for highest strength stat, whichever of the tied bots has the highest smarts stat will win. If there is still a tie, a bot will be randomly selected to win Immunity from among the tied bots remaining.

Immunity Challenge #2

The bot with the

highest speed stat

will win Immunity. In the event of a tie for highest speed stat, whichever of the tied bots has the highest strength stat will win. If there is still a tie, a bot will be randomly selected to win Immunity from among the tied bots remaining.

Immunity Challenge #3

The bot with the

highest smarts stat

will win Immunity. In the event of a tie for highest smarts stat, whichever of the tied bots has the highest speed stat will win. If there is still a tie, a bot will be randomly selected to win Immunity from among the tied bots remaining.

Immunity Challenge #4

The bot with the

highest strength stat

will win Immunity. In the event of a tie for highest strength stat, whichever of the tied bots has the highest speed stat will win. If there is still a tie, a bot will be randomly selected to win Immunity from among the tied bots remaining.

Immunity Challenge #5

The bot with the

highest speed stat

will win Immunity. In the event of a tie for highest speed stat, whichever of the tied bots has the highest smarts stat will win. If there is still a tie, a bot will be randomly selected to win Immunity from among the tied bots remaining.

Immunity Challenge #6

The bot with the

highest smarts stat

will win Immunity. In the event of a tie for highest smarts stat, whichever of the tied bots has the highest strength stat will win. If there is still a tie, a bot will be randomly selected to win Immunity from among the tied bots remaining.

Immunity Challenge #7

The bot with the

highest strength stat

will win Immunity. In the event of a tie for highest strength stat, whichever of the tied bots has the highest smarts stat will win. If there is still a tie, a bot will be randomly selected to win Immunity from among the tied bots remaining.

[TRIBAL COUNCIL]

At each Tribal Council, each bot must cast a vote for another bot. Bots are not permitted to cast a vote for the bot that won Immunity that round. The bot with the most votes will be eliminated.

MEDICAL EVACUATIONS:

A bot may be medically evacuated during Tribal Council if its Strategy programming is insufficient and does not specify who to vote during a tribal council.

TIES:

In the event of a tie, all bots (including the tied bots) will revote and must revote for one of the bots that received the most votes.

REVOTES:

If a revote results in another tie one of two things will occur. If the tie has narrowed a multi-player tie down to less players (for example, the original TC was a 3-way tie, and now there is a 2-way tie) then another revote will occur. If the tie is between the same exact players it was before then a challenge will be performed to determine which bot will be eliminated.

TIE CHALLENGE:

The bots that are still tied for most votes will be eligible for elimination. Of the eligible bots, the bot that performed the worst at the most recent challenge will be eliminated. If there is still a tie, the decision will be made at random.

[AVAILABLE DATA]

The bots have access to a lot of basic information, including:

• The exact STRENGTH, SPEED, and SMARTS stat of each bot


• Which bot has WON each Immunity Challenge


• HOW MANY votes each bot receives at each Tribal Council


• The NAME of each bot


• WHO VOTED for who each Tribal Council

Yes, your bots have access to who voted for who each Tribal Council. Although in a typical Survivor game each TC votes are anonymous, in order to imitate the social game to the best of our ability, our bots are assumed to be highly intelligent and can deduce who voted for who each tribal council. Bots, however, do not have access to other bot's strategies. If you have any question whether a criteria you've come up with is valid or not, please ask.

[FUTURE SEASONS]

You are not required to read this section. If you are interested in the future of SURVIVOR BOT you may read the below sections.

Spoiler: FUTURE MECHANICS

Originally, I was not going to allow each bot to view who voted for who each Tribal Council. However, I believe allowing this improves the strategical ability the players can implement into the programming of each bot. This may change in the future. In the future seasons, other data may be added or removed from the game.

One idea I believe I will implement in future seasons is the ability to "FOLLOW" another bot. Following another bot would allow the bot to have access to who another BOT will be voting for at that current Tribal Council (and allows the bots to imitate alliances).

Please offer suggestions and opinions of which data/criteria or mechanics you believe should be removed or added to the game in future seasons.

Spoiler: FUTURE SEASONS

In future seasons, the starting number of bots will closely imitate the show and I will attempt to match the format of two tribes of eight with a merge at ten. This new format will result in an added strategical dimension of programming when each bot must take into consideration pre-merge and post-merge strategy. My ultimate goal is to set this up as a tourney style game in which there are four players per game, each of which submit four bots which will randomly be placed onto the two starting tribes.

If you have any suggestions or opinions of what the future of SURVIVOR BOT should look like, please let me know.

[EXAMPLE BOTS]

Below are a few example bots. You are not required to read them, but look at them to get a look of acceptable bots.

Spoiler: GEEK BOT

NAME: Geek Bot

STRENGTH: 12
SPEED: 17
SMARTS: 31
[Strategy]
1. Of the players eligible to vote for, vote the player with the least smarts. If more than one player has the lowest smarts, see 2.
2. Of the players with the least smarts, vote the player with the most strength. If more than one player meets both of these standards and it is still tied, see step 3.
3. Of the players still tied, vote for the player with the longest bot name (counting all characters, excluding spaces). If more than one player meets this criteria, vote for one of these tied players randomly.

[Ties]
4. If it is possible to keep my vote the same, keep my vote the same. If not, see 1.

[Jury]
5. Of the final 2, vote for the player with the most smarts. If they are tied, see 6.
6. Vote for the player who voted alongside Geek Bot during the most number of Tribal Councils. If they are tied, see 7.
7. Vote for the player who has the most speed. If they are tied, see 8.
8. Vote for the player who won the last Immunity Challenge.

Spoiler: DICE BOT

NAME: Dice Bot

STRENGTH: 18
SPEED: 24
SMARTS: 18
STRATEGY: Vote randomly.
TIES: If the personal Dice Bot originally voted for is still eligible to be voted for, vote for that person again. If not, randomly vote for one of the eligible bots that is not Dice Bot.
JURY: Vote randomly.

Spoiler: BITCH BOT

NAME: Bitch Bot

STRENGTH: 19
SPEED: 21
SMARTS: 18

STRATEGY

During the first Tribal Council, vote for whoever has the highest Strength of those eligible to be voted for. If there is a tie for players with most strength, vote randomly among the eligible bots.

During the other Tribal Councils, vote for the bot that won the Immunity Challenge in the previous round. If the bot that won Immunity last round is Immune again this round, vote randomly.

TIES

If Bitch Bot is not tied for most votes, switch Bitch Bot's vote to one of the other bots eligible to be voted for (at random).
If Bitch Bot is tied for most votes, keep Bitch Bot's vote the same if possible. If it is not possible to keep her original vote the same, vote randomly for one of the other bots.

JURY

1. Vote for the player who voted Bitch Bot least number of times during the game (do not include revotes). If there is a tie, see 2.
2. Vote for the player who won the least number of Immunity Challenge. If there is a tie, see 3.
3. Vote for the player who has the most smarts. If there is a tie, see 4.
4. Vote for the player who did not win the last immunity challenge.

For this game you may only submit one bot. The first nine players to submit a bot (to Blackberry via PM) will have their bots participate in

SurvivorBots - Season 1

!

In addition, if you'd like to submit a bot, but would like time to develop your bot, shoot me a PM and I'll reserve your spot for Season 1, and you will have *up to* 48 hours from that PM to submit your completed bot.

[Blackberry]

SURVIVOR BOTS: UPDATE!

I currently have received a total of 16 bots. Wow! I'm glad there is so much interest in this!

Since I received 16 bots, the first 9 bots will participate in the first game. The second set of 9 bots will be participating in the second game. Since these are

trial

games, if there is anything unclear or points of confusion with any of the bots I will send out questions to those bots. As soon as I have everything clarified for the first 9 bots, their results will be posted. In the mean time, there is room for 2 more bots!

[Blackberry]

SURVIVOR BOTS: Season 1!

Welcome to the first season of Survivor Bots! Nine brave bots will venture into a game unlike any other. Let's see what happens!

[MEET THE BOTS]

• Bad Robot
  submitted by TheBadOne


• Empbot
  submitted by Empking


• Zeus Bot
  submitted by Ten_Heavens


• Middlebot
  submitted by AcRv


• Mongo Bot
  submitted by JDGA


• Immunity Bot
  submitted by inspiratieloos


• The Bot That is a Dragon
  (nickname: Dragon Bot) submitted by 2birds1stone


• Brotocol Five
  submitted by Cybele


• Sheep Bot
  submitted by Cheery Dog

Spoiler: NOTES

* I apologize for the extreme delay, some of the bots were still unfinished.
* If any bots were not fully complete, I made the proper adjustments so they could compete properly.
* Recap will be posted as soon as all Episodes are released.
* Flavor has been added for entertainment purposes and does not reflect Bot strategies.
* I do appreciate the effort most of you put into your bots, in order to fix some of the bots that did not have proper programming, I've made some rule adjustments.
* (Rule Adjustment) It is assumed all bots can not vote themselves, nor the Immune.
* (Rule Adjustment) At the FINAL 3 TC only the individual that is Immune will vote.

Spoiler: EPISODE 1

The bots meet each other for the first time. The Bot That is a Dragon is quickly nicknamed

Dragon Bot

by his competitors. Mongo Bot & Bad Robot are the first to form an alliance.

• Dragon Bot shows off his strength and wins Immunity!

Middlebot pronounces to others his dislike for Brotocol Five. Meanwhile... Zeus Bot, Dragon Bot & Immunity Bot come to the conclusion that they are the top dogs and decide to team up. Which bot will fall at their mercy?

[Tribal Council #1]

BROTOCOL FIVE (Middlebot's vote)
EMPBOT (Brotocol Five's vote)
BAD ROBOT (Sheep Bot's vote)
SHEEP BOT (Mongo Bot's vote)
SHEEP BOT (Bad Robot's vote)

MONGO BOT (Zeus Bot's vote)
MONGO BOT (Immunity Bot's vote)
MONGO BOT (Empbot's vote)
MONGO BOT (Dragon Bot's vote)

• Mongo Bot is eliminated with 4 votes!

Spoiler: EPISODE 2

After the events of the first TC, Middlebot manages to align himself with Empbot, and convinces him that Brotocol Five will need to be exterminated!

• Immunity Bot uses his speed and wins Immunity!

Sheep Bot fumbles around and bahhhhs. Bad Robot manages to join the alliance of Zeus Bot, Immunity Bot, and Dragon Bot and they select their next target. Unknown to anyone else, both Zeus Bot and Immunity Bot have their own agendas...

[Tribal Council #2]

DRAGON BOT (Zeus Bot's vote)
ZEUS BOT (Immunity Bot's vote)
EMPBOT (Sheep Bot's vote)
BROTOCOL FIVE (Middlebot's vote)
BROTOCOL FIVE (Empbot's vote)

SHEEP BOT (Brotocol Five's vote)
SHEEP BOT (Bad Robot's vote)
SHEEP BOT (Dragon Bot's vote)

• Sheep Bot is eliminated with 3 votes!

Spoiler: EPISODE 3

Dragon Bot is not happy with his former allies, Zeus Bot & Immunity Bot, turning their back on the plan! Brotocol Five quickly catches on to Middlebot & Empbot's alliance and plots to survive.

• Zeus Bot showcases his wits and wins Immunity!

Immunity Bot and Dragon Bot have a public dispute. Zeus convinces Immunity Bot it's time to give Dragon Bot the boot. Empbot and Middlebot stick to their plan to gun for Brotocol Five. Bad Robot plots a betrayal...

[Tribal Council #3]

EMPBOT (Brotocol Five's vote)
IMMUNITY BOT (Dragon Bot's vote)
BROTOCOL FIVE (Middlebot's vote)
BROTOCOL FIVE (Empbot's vote)

DRAGON BOT (Immunity Bot's vote)
DRAGON BOT (Zeus Bot's vote)
DRAGON BOT (Bad Robot's vote)

• Dragon Bot is eliminated with 3 votes!

Spoiler: EPISODE 4

Despite their successful blindside of Dragon Bot, Immunity Bot and Zeus Bot begin to turn on one another. Both want to emerge the leader. Meanwhile, Empbot and Middlebot continue their scheming to rid their sights of Brotocol Five. Unfortunately for them, they're about to hit a speed bump...

• Brotocol Five fights to stay in the game and wins Immunity!

Empbot and Middlebot scramble to find another target. Bad Robot and Middlebot begin to squabble. Zeus Bot and Immunity Bot are still at one another's throats. This is going to be a close one...

[Tribal Council #4]

EMPBOT (Brotocol Five's vote)
BAD ROBOT (Middlebot's vote)
MIDDLE BOT (Bad Robot's vote)
ZEUS BOT (Immunity Bot's vote)

IMMUNITY BOT (Zeus Bot's vote)
IMMUNITY BOT (Empbot's vote)

• Immunity Bot is eliminated with 2 votes!

Spoiler: EPISODE 5

Zeus Bot is approached by Brotocol Five. Can they work together and take down the Empbot & Middlebot duo?

• Middlebot races to safety and wins Immunity!

Empbot & Middlebot also approach Zeus Bot and attempt to persuade him to their side. Will they gun for Brotocol Five again, or do they have something different up their sleeve?

[Tribal Council #5]

EMPBOT (Brotocol Five's vote)

BROTOCOL FIVE (Middlebot's vote)
BROTOCOL FIVE (Empbot's vote)
BROTOCOL FIVE (Bad Robot's vote)
BROTOCOL FIVE (Zeus Bot's vote)

• Brotocol Five is eliminated with 4 votes!

Spoiler: EPISODE 6

Bad Robot & Middlebot continue to bicker with one another. Zeus begins to worry about his position in the game.

• Zeus impresses everyone with his wits and wins Immunity!

Bad Robot and Middlebot are determined to take one another down. Will Empbot stay loyal to Middlebot? And what will Zeus do?

[Tribal Council #6]

MIDDLEBOT (Bad Robot's vote)

BAD ROBOT (Middlebot's vote)
BAD ROBOT (Empbot's vote)
BAD ROBOT (Zeus Bot's vote)

• Bad Robot is eliminated with 3 votes!

Spoiler: EPISODE 7

Zeus Bot plots a way to break Empbot and Middlebot up.

• Middlebot shows he's stronger than he seems and wins the final Immunity!

Middlebot must decide whether he'll take out his loyal ally Empbot, or the thunderous Zeus Bot.

[Tribal Council #7]

ZEUS BOT (Middlebot's vote)

• Zeus Bot is eliminated with 1 vote!

Spoiler: FINALE

Will Empbot take home the crown? Or will Middlebot prove he's really the TOPBOT?

[Jury Votes]

Mongo Bot votes for MIDDLEBOT
Sheep Bot votes for EMPBOT
Dragon Bot votes for EMPBOT
Immunity Bot votes for MIDDLEBOT
Brotocol Five votes for EMPBOT
XT0PH-D votes for EMPBOT
Zeus Bot votes for EMPBOT

• Empbot wins in a vote of 5-2!

	TC 1	TC 2	TC 3	TC 4	TC 5	TC 6	TC 7	JURY
EMPBOT	Mongo Bot	Brotocol Bot	Brotocol Five	Immunity Bot	Brotocol Five	Bad Robot	-----	WINNER
MIDDLEBOT	Brotocol Five	Brotocol Bot	Brotocol Five	Bad Robot	Brotocol Five	Bad Robot	Zeus Bot	RUNNER-UP
ZEUS BOT	Mongo Bot	Dragon Bot	Dragon Bot	Immunity Bot	Brotocol Five	Bad Robot	-----	EMPBOT
BAD ROBOT	Sheep Bot	Sheep Bot	Dragon Bot	Middlebot	Brotocol Five	Middlebot		EMPBOT
BROTOCOL FIVE	Empbot	Sheep Bot	Empbot	Empbot	Empbot			EMPBOT
IMMUNTIY BOT	Mongo Bot	Zeus Bot	Dragon Bot	Zeus Bot				MIDDLEBOT
DRAGON BOT	Mongo Bot	Sheep Bot	Immunity Bot					EMPBOT
SHEEP BOT	Bad Root	Empbot						EMPBOT
MONGO BOT	Sheep Bot							MIDDLEBOT

[Blackberry]

SURVIVOR BOTS: Season 2!

Welcome to the second season of Survivor Bots! Nine new bots will try their all to survive. Who can come out on top?

[MEET THE BOTS]

• Strategy Bot
  submitted by Nicholas1024


• Steve
  submitted by Snakes


• BOTicus
  submitted by D3f3nd3r


• Sexy Bot
  submitted by Blastoide


• Jenna
  submitted by Mist7676


• Spitfly Bot
  submitted by ProsecutorGodot


• DashBot
  submitted by RainbowDash


• XT0PH-D
  submitted by xtopherusD


• Deana
  submitted by Chevre

Spoiler: EPISODE 1

After meeting each other for the first time, DashBot, Spitfly Bot and Deana decide to team up.

• Deana proves a girlbot can pack a punch and wins Immunity!

BOTicus forms his own alliance with Jenna and XT0PH-D. Meanwhile, Sexy Bot seduces Strategy Bot and they plot their way to victory. With so many alliances, who will come out on top?

[Tribal Council #1]

BOTicus (Steve's vote)
JENNA (Sexy Bot's vote)
JENNA (Strategy Bot's vote)

STRATEGY BOT (Splitfly Bot's vote)
DASHBOT (Jenna's vote)
STRATEGY BOT (DashBot's vote)
DASHBOT (BOTicus's vote)
STRATEGY BOT (Deana's vote)
DASHBOT (XT0PH-D's vote)

• DashBot and Strategy Bot tie with 3 votes a piece!

[Tribal Council #1 Revote]

DASHBOT (Splitfly Bot's vote)
DASHBOT (Jenna's vote)
DASHBOT (BOTicus's vote)
DASHBOT (Strategy Bot's vote)

STRATEGY BOT (Steve's vote)
STRATEGY BOT (DashBot's vote)
STRATEGY BOT (Sexy Bot's vote)
STRATEGY BOT (Deana's vote)
STRATEGY BOT (XT0PH-D's vote)

• Strategy Bot is eliminated with 5 votes!

Spoiler: EPISODE 2

DashBot begins to doubt her alliance. She quickly forms a new bond with Sexy Bot.

• DashBot earns her speedy name and wins Immunity!

BOTicus is not happy with Steve for voting against him last Tribal Council. DashBot's out allies, Spitfly Bot & Deana, target Jenna. But DashBot & Sexy Bot have their own plan.

[Tribal Council #2]

STEVE (BOTicus's vote)
SPITFLY BOT (Jenna's vote)
DEANA (Sexy Bot's vote)
DEANA (DashBot's vote)

JENNA (Spitfly Bot's vote)
JENNA (Steve's vote)
JENNA (XT0PH-D's vote)
JENNA (Deana's vote)

• Jenna is eliminated with 4 votes!

Spoiler: EPISODE 3

DashBot continues to campaign against Deana. Spitfly Bot develops a crush on Sexy Bot.

• Spitfly Bot lets us know he has the brains and wins Immunity!

Despite Spitfly's attempt to impress Sexy Bot by winning Immunity, Sexy Bot attempts to seduce Steve. Spitfly, nor Steve, like Sexy Bot's promiscuous ways.

[Tribal Council #3]

STEVE (Deana's vote)
SEXY BOT (Steve's vote)
SEXY BOT (Spitfly Bot's vote)

DEANA (DashBot's vote)
DEANA (Steve's vote)
DEANA (Sexy Bot's vote)
DEANA (BOTicus's vote)

• Deana is eliminated with 4 votes!

Spoiler: EPISODE 4

DashBot and Spitfly Bot decide to rekindle their alliance. It appears Spitfly Bot has finally got Sexy Bot's attention, and she isn't happy that he voted her last Tribal Council.

• XT0PH-D flexes his muscles and wins Immunity!

Despite the fact that they've both voted one another, Steve & BOTicus decide they should team up if they want to survive.

[Tribal Council #4]

SPITFLY BOT (Sexy Bot's vote)
STEVE (DashBot's vote)
STEVE (Spitfly Bot's vote)

DASHBOT (XT0PH-D's vote)
DASHBOT (Steve's vote)
DASHBOT (BOTicus's vote)

• DashBot is eliminated with 3 votes!

Spoiler: EPISODE 5

Steve and BOTicus decide to target Spitfly Bot next.

• BOTicus is the first to reach the finish line and wins Immunity!

Spitfly Bot tries to rally the others against Steve. Will it work?

[Tribal Council #5]

STEVE (Spitfly Bot's vote)

SPITFLY BOT (XT0PH-D's vote)
SPITFLY BOT (Sexy Bot's vote)
SPITFLY BOT (Steve's vote)
SPITFLY BOT (BOTicus's vote)

• Spitfly Bot is eliminated with 4 votes!

Spoiler: EPISODE 6

Sexy Bot tries to target the studly BOTicus. Meanwhile, XT0PH-D makes a case to knock out Steve.

• Sexy Bot shows she has smarts too and wins Immunity!

Will BOTicus and Steve stick together?

[Tribal Council #6]

STEVE (XT0PH-D's vote)
BOTICUS (Sexy Bot's vote)

XT0PH-D (Steve's vote)
XT0PH-D (BOTicus's vote)

• XT0PH-D is eliminated with 2 votes!

Spoiler: EPISODE 7

Sexy Bot tries to work her magic on the two remaining bots in an attempt to stir up controversy.

• Steve earns his spot in the finale and wins the Final Immunity!

Will Sexy Bot's tactics work? Or will Steve stay loyal to the brace BOTicus?

[Tribal Council #7]

SEXY BOT (Steve's vote)

• Sexy Bot is eliminated with 1 vote!

Spoiler: FINALE

Steve or BOTicus? Let's find out!

[Jury Votes]

Strategy Bot votes for BOTICUS
Jenna votes for STEVE
Deana votes for STEVE
DashBot votes for BOTICUS
Spitfly Bot votes for BOTICUS
XT0PH-D votes for STEVE
Sexy Bot votes for BOTICUS

• BOTicus wins in a vote of 4-3!

[Blackberry]

IT'S UNLOCKED!

Woohoo! It's time to unlock the thread! I'll be revealing the rest of the results throughout the night! Below I have some discussion points as well . I do apologize for the wait, as I mentioned, some bots were still incomplete but I went ahead and fixed them in terms with what I assumed the creator intended. You do not have to read all of the below, they're just starting points for those who are interested!

Also - I have decided not to reveal the stats or programs of the bots to safeguard some of those masterpieces. Feel free to share your own strategy if you'd like though.

[RULE CHANGES]

I have decided to make the following rule changes to make it easier on everyone.

• No Bot may vote for themselves nor may they vote for the Bot with Immunity.
• At the FINAL 3 Tribal Council, only the Bot that is immune will cast a vote.
• To avoid ties in Immunity Challenges I would like to bump up the stat allocation to 600 points.

[QUESTIONS/IMPROVEMENTS]

The following are a list of questions and talking points that I'd like to get your feedback on. Feel free to provide other questions/suggestions as well so we can improve the game!

• FOLLOW COMMAND:
  Should we include a "FOLLOW" command (your Bot may ask one Bot who they are voting during that TC)?
- If we do, we'd have to account for if (a) the Bot is voting for the own bot is also following another Bot [in which case the Bot asking will get a 'No Response' and (b) if we allow a Follow command you must instruct what you do if you get a 'No Response'.
• STAT CHANGES:
  Should we increase the stat points to allow for more diversity? Should we add an additional stat (Endurance)?
- Some bots had the exact same stats and I prefer an Immunity winner not be determined at random. I think we should increase the stats to 600 points. I also like the idea of adding an Endurance stat. The Endurance Stat would only be used for the FINAL 3 TC.
• RANDOM:
  Should the idea of allowing a choice to be made randomly be forbidden?
- Or should this just be a special setup for a 'Season' to not allow randomization. On a different note - should we forbid Jury Votes from being determined randomly?

[BOT WORKSHOP]

Need help creating a bot? Or not sure what to keep in mind? Below are a couple of general tips to create a completed Bot. When selecting criteria to determine your vote, keep the following in mind.

• Describe what your Bot does if no one meets, or multiple bots meet the criteria selected.
- Example: If your Bot is designed to vote whoever has the highest Smarts and that individual has won Immunity, what does your bot do?
• Describe who your Bot votes for in the event of a tie.
- Example: What if the Bot you originally voted for is in the tie? What if the tie is between two bots and you did not vote either of them?
• Describe what your Bot does if the Bot that meets your criteria is YOUR Bot.
- Example: If you Bot is designed to vote whoever won the last Immunity Challenge, what if your Bot won the last Immunity Challenge?
• A good idea is to use an 'eligible' system.
- Example: If Bots meet X criteria, they are eligible for voting. If at only time there is only one bot eligible for voting, vote them. If not, move on to the next criteria and see which eligible bots meet the next criteria.

[NEXT SEASON]

I would like the next test run to be the following scenario.

• The game will consist of 2 tribes of 6 bots each. There will be 3 tribal immunity challenges, followed by a merge at 9.
• Each contestant will submit 2 bots, which will be randomly placed on opposite tribes (this will permit more intricate strategy).
• Jury will start once the tribes merge at 9.

Feel free to post with your thoughts and comments! The rest of the results are coming shortly! I'll also be giving awards for notable bots!

[Empking]

I think randomness is needed, and if it was banned you'd simply be replacing it with the just as bad arbitrariness. A "Randombot" would be cheap though.

I don't think boosting the number of points would help ties, whether you have 6 or 600 points you'll still get people putting 2,2,2 or 200,200,200.

The workshop is good though.

[Cheery Dog]

I think having random needs to stay, because my bot needed that if all else fails argument to actually function round one. (because I couldn't actually sheep people yet because of the no follow people)

I think the extra stat would be possibly be useful, make the total amount of stat points something that can't be divided equally into each of the stat categories to lessen the chances of a immunity being randomly determined.

I meant to send in the second set of edits to my bots, I opened the pm to preform the edits, but then ended up not thinking of what I actually wanted.
I have a different idea for submitting a new bot now, although I'm not sure how well it will go with the first tribal council either.

[Chevre]

I realized my faults with Deana about 10 minutes after submitting it.

If we add the follow thing, won't we need to know the names of the bots beforehand?

The more stats, the better. I think we should even have some challenges which are combinations of stats (Strength + Speed) or even more complex and combinations of fractions of stats (1/2 Strength + 1/4 Endurance + 1/4 Speed)

I don't think random bots should be allowed; it doesn't seem to be "realistic." However, randomness should obviously apply when all criteria are tied/ineligble.

[Blackberry]

I realized my faults with Deana about 10 minutes after submitting it.

If we add the follow thing, won't we need to know the names of the bots beforehand?

The more stats, the better.

I think we should even have some challenges which are combinations of stats (Strength + Speed)

or even more complex and combinations of fractions of stats (1/2 Strength + 1/4 Endurance + 1/4 Speed)

I don't think random bots should be allowed; it doesn't seem to be "realistic." However, randomness should obviously apply when all criteria are tied/ineligble.

The comment I bolded is something I was wanting to do once everything was set and the full-blown (16 player) version was ready to go.

...

Concerning the Follow command, you would have the same criteria as you use with voting to determine who you'd like to follow. For example "Follow the Bot that won Immunity this round", or "Follow the Bot that received the most votes last TC (if there is a tie, choose the one that, etc., etc.)", or "If anyone voted the same as my Bot last TC, Follow one of those bots (if more than one, choose to Follow the one with the highest Speed, etc.)" ... or whatever creative/effective method you could come up with to determine who you'll follow .

However, with the Followcommand, you would always need a back-up such as "If bot responses with No Response, do X instead." (No Response would be given to your bot if (a) the Bot is voting your own Bot, or (b) if the Bot is trying to follow someone else). If we think it's too complicated, we don't have to implement it .

[Empking]

Woo!

[Blastoide]

Would the follow command be part of the Strategy section, or an entirely new section itself. I think it would be fine if it was part of the strategy, but I'm not sure how it would work if it was an entirely new section. It would definitely help for flavor purposes though.
I think adding Endurance stat as Challenge #7 would be great, because that way the strength path wouldn't be the way most people would go after. It would add more thinking in the allocation process in my hot opinion.
As for the actual game, I love reading the flavor! It is very entertaining.. And Sexy Bot isn't getting rusty(ha) just so you all know. Steve probably just has a man crush on BOTicus. Otherwise Sexy Bot would have made it to the end! I've noticed though, winning Challenge #6 is a curse, because whoever does win, gets voted off next..

[Blackberry]

Would the follow command be part of the Strategy section, or an entirely new section itself. I think it would be fine if it was part of the strategy, but I'm not sure how it would work if it was an entirely new section. It would definitely help for flavor purposes though.
I think adding Endurance stat as Challenge #7 would be great, because that way the strength path wouldn't be the way most people would go after. It would add more thinking in the allocation process in my hot opinion.
As for the actual game, I love reading the flavor! It is very entertaining.. And Sexy Bot isn't getting rusty(ha) just so you all know. Steve probably just has a man crush on BOTicus. Otherwise Sexy Bot would have made it to the end! I've noticed though, winning Challenge #6 is a curse, because whoever does win, gets voted off next..

It would be part of the Strategy section, as an OPTION (not a requirement at all).

Also - I ran a lot of other simulations with the same bots today (just so I could post a ranking/see how they all do against eachother) and I can tell you the IC 6 winner does not always get voted off next (I'll probably post those voting histories and rankings just so people can see how their bots did in other scenarios).

[Blastoide]

Hehe.. Sexy Bot had the deciding vote.

Also - I ran a lot of other simulations with the same bots today (just so I could post a ranking/see how they all do against eachother) and I can tell you the IC 6 winner does not always get voted off next (I'll probably post those voting histories and rankings just so people can see how their bots did in other scenarios).

I don't knoooww.. I'll believe you.. For now.. And please, post the rankings. I always like to see those kinds of things!

[Nicholas1024]

I'd like to reserve a spot for the next season, please. Bot info coming shortly.

[Chevre]

Yes. /pre-in for next season.

[Blastoide]

What?! Pre-Ins?! Yay!

/Pre-in for next season.

And I promise this time I'll make my bot before deadline.

[inspiratieloos]

I think randomness is needed, and if it was banned you'd simply be replacing it with the just as bad arbitrariness. A "Randombot" would be cheap though.

You could just add a rule that a bot needs to have at least 1 (or more) voting criteria before voting randomly.

Also what Empking said on points, most people will go for round numbers.

/pre-in

[2birds1stone]

[QUESTIONS/IMPROVEMENTS]

The following are a list of questions and talking points that I'd like to get your feedback on. Feel free to provide other questions/suggestions as well so we can improve the game!

• FOLLOW COMMAND:
  Should we include a "FOLLOW" command (your Bot may ask one Bot who they are voting during that TC)?
- If we do, we'd have to account for if (a) the Bot is voting for the own bot is also following another Bot [in which case the Bot asking will get a 'No Response' and (b) if we allow a Follow command you must instruct what you do if you get a 'No Response'.
• STAT CHANGES:
  Should we increase the stat points to allow for more diversity? Should we add an additional stat (Endurance)?
- Some bots had the exact same stats and I prefer an Immunity winner not be determined at random. I think we should increase the stats to 600 points. I also like the idea of adding an Endurance stat. The Endurance Stat would only be used for the FINAL 3 TC.
• RANDOM:
  Should the idea of allowing a choice to be made randomly be forbidden?
- Or should this just be a special setup for a 'Season' to not allow randomization. On a different note - should we forbid Jury Votes from being determined randomly?

Random should be forbidden except for error handling. 'Vote random' is cheap and brings nothing to the game, but it's definitely a valid contingency plan. Strongly agree with adding an extra stat and including a 'follow' command, but 600 points seems like overkill.

Also, I wouldn't mind seeing stricter rules regarding bot syntax. I'm not sure about everyone else, but I spent a long time trying to find the least ambiguous wording for my bot, and it would've shortened my design time a lot if there was a 'programming language' to adhere to.

Also what Empking said on points, most people will go for round numbers.

Disagree.

Pre-in, if we're pre-inning.

[inspiratieloos]

I had something like 8 criteria and then a catch all 'vote randomly between all eligible bots'. You could also forbid random voting and have random voting as standard behaviour for each bot if it runs out of criteria.

What if you put in an 'intent to vote' stage, in which every bot states who they intent to vote (answer 'no comment' or completely different from voting criteria may be given), then in the voting stage that information can be used by bots. If that works you could later start thinking about allowing programming to say different things to different bots and stuff... Until at the end you have a complete survivor simulation with dozens of pages of programming for each bot.

Whether the follow command or this is a good idea is mostly dependant on whether you think simplicity or realism is more important.

[Cybele]

Oh, I find myself liking inspir's suggestion.

[Xalxe]

Can we see the bots' programming?

EDIT: I can reading.

Also, /pre-in.

[TheBadOne]

/Pre-in

[D3f3nd3r]

/pre-in

I didn't think I had much of a chance. I made one relatively strong move in my strategy, but otherwise everything was pretty much simple.

[xtopherusD]

Looks like Godot and I had the same idea for tiebreakers!

My Ties section was essentially "If it is possible to vote for the same bot, don't."
And had it not been that way it would've been a very different game...

'Twas fun to read the flavour. Glad it was there. Stops it from being an unreadable list of happenings.
I reckon I'll /pre-in for the next go if that is actually what's happening! This was pretty cool!

[ProsecutorGodot]

I'll /pre-in for the next season.