DarwinBotsManual
Open the app EspañolES

Home

The screen the app opens with: the last run, the scenarios to get started, opening a .txt or a .dbsim, your saved runs and recent bots.

Home is the app's first screen and the place you come back to when you want to switch runs. From here you start a new world from a scenario, carry on with the one you left running, resume a saved one or open a file. You get there with Home in the top bar or by clicking the DarwinBots name.

The screen has two columns. On the left, the last run's card and the scenario gallery; on the right, your Saved runs and Recent bots.

The last run

The card at the top changes depending on what there is:

What there isWhat it showsButtons
A world in memory (what you left in Observe)Last run: a thumbnail of the world, the name, the cycle, how many bots and species it has, and whether it's saved (“saved … ago”) or “not saved”Continue and View analysis
Nothing in memory, but saved runsLast saved run: the most recent one, with its thumbnail and its dataResume
Nothing at allNo runs yetPick a scenario, which scrolls down to the gallery

Continue takes you to Observe with the world just as it was, without reloading anything. View analysis opens Analyze on that same run. Resume loads the saved run and takes you to Observe paused: click Start to have it go on.

With a tournament in progress, the simulation is its fight: Resume, the scenarios' Start, Choose file and Import .dbsim are off, and a notice at the top explains it and takes you to the tournament strip (see Compete).

The world in memory lives as long as the tab is open. If you reload the page, whatever you didn't save is lost; what you saved stays in the list on the right.

Scenarios

A scenario is a setup ready to start: which bots get seeded, how many, what color, and with what world settings. The gallery shows a preview of each one, its name, a short description and some tags (the theme and how many species it brings). The app comes with these:

ScenarioWhat it's about
Primordial soupAlgae and a minimal animal in the default world, with mutations: the starting point to watch a species evolve.
Predator and preyA hunter over a field of algae: does the food run out or do the populations balance?
F1 matchTwo F1 league bots face to face with the league settings.
F2 matchTwo F2 league bots face to face, with their solar energy and their disqualification.
F3 matchTwo F3 league bots face to face, with their solar energy and their disqualification.
MB matchTwo multi-bots in the F2 world, with no disqualification.
SB matchTwo short bots, on a bigger field.
SS matchTwo single-store bots, with the F1 league settings.
F4 matchTwo league bots face to face, on a field with twice the side and the old-age upkeep at 1.
Day and nightThe sun sets every 1000 cycles and the population oscillates.
MazeA spiral maze the bots can see.
OceanWater physics in a world that closes in on itself; the algae float adrift.
ArchipelagoTen random rock islands and two teleporters.

Each card has two buttons:

The league matches are different: instead of Start they say Pick bots and take you to Compete, because a match is set up by choosing the rivals.

The scenarios you save from Experiment show up in the same gallery after the built-in ones, with the Custom tag. The Custom setup link, at the top right of the gallery, also takes you to Experiment. How a scenario is built and shared is in Scenarios.

From a file

The last card in the gallery, From a file, opens two kinds of file with the Choose file button:

With a .txt, the new world is the default-values one, with the algae from Primordial soup and ten copies of your bot. The bot takes the file's name (without the .txt) and a color of its own; the run is called “bot with algae”. If your bot has the same name as the alga, only your bot is seeded.

It's the quickest way to see whether a bot you wrote does anything. The file format is in the .txt format; if the DNA has words the engine doesn't recognize, Observe tells you how many (they're worth 0). A .txt that's empty or has only comments isn't seeded: the app warns you there's nothing to seed.

For something more elaborate (other species, more copies, another world), seed the bot from Observe or build a scenario in Experiment.

Saved runs

The right-hand column lists the runs you saved from Observe, the most recent one on top: name, cycle, how many bots it had and when you saved it. The one that's loaded now carries the current mark.

  1. Click a row to resume it. If it's the one already in memory, it takes you to Observe without reloading it.
  2. If you have more than four, See all expands the whole list and See less shortens it again.
  3. Import .dbsim opens a simulation file, just like the From a file card.

To delete a saved run, use Runs in Observe (Observe).

Recent bots

Below, up to four bots from your current run and the saved ones show up, with their color and their category in the library (F1, F2, Vegetable, Custom…). Each name opens its profile in the library. The Full library link takes you to the entire library, with the count of bots it holds.

Where everything is kept

Runs, custom bots, custom scenarios and tournaments are saved in this browser, not on a server. If you switch computers or browsers they won't be there: export them first. How to do that, and what happens if the browser clears its data, is in Your data.

If it's your first time, Your first simulation walks you step by step from Primordial soup to your first saved run.