This game allows you to place a creature into a virtual environment with other creatures and observe its activity.
I created this application in 2017 as I was getting into python for the first time. It was one of the first programs that I was proud of.
You're able to create a creature and release it into an environment where it can interact with other creatures.
- World already has creatures
- Every time creature comes into contact with another it has a chance to eat, become friends or have a baby
- The more you do one thing the less you do the others
- It has 4 different areas so that they're not all interacting with the same things
- Every day there's a chance they'll move areas
- Show creatures alive at all times
- Make inputted names possible baby names using a txt file
Usage reporting is on by default: Kreatures sends one startup event per launch to trace at https://trace.danielstephenson.dev, carrying only the program name, the version from version.txt and a random installation ID (the tag install, so installations can be counted rather than launches). Nothing about you or your machine is sent — no username, hostname, IP address, creature name or anything typed into the game. The report is made off the main thread and can never stop or slow the game.
The first launch prints a one-line notice and writes src/config/settings.json (git-ignored).
The installation ID is a random UUID kept in a file named trace-install-id in the user data directory: ~/.local/share/kreatures/ on Linux (or $XDG_DATA_HOME/kreatures/), ~/Library/Application Support/kreatures/ on macOS and %APPDATA%\kreatures\ on Windows. It identifies no person, account or address; delete the file to get a new one. Setting the environment variable TRACE_INSTALL_ID sends that value instead and leaves the file alone. The file is only created while reporting is on, so every opt-out below also stops it. The browser version makes no ID file.
To turn reporting off, any one of these will do:
src/config/settings.json→"usage_reporting": {"enabled": false}— Kreatures' own switchTRACE_USAGE_REPORTING=off(alsofalse,0,no) in the environment — turns off every program that reports to traceDO_NOT_TRACK=1(alsotrue,yes) in the environment — the console DNT convention, honoured the same way
Every switch fails closed, so an opt-out is never read as "on": enabled keeps reporting on only for true (or the strings "true", "on", "yes", "1"), and false, "false", "off", 0, null, a typo or a missing enabled turn it off; "usage_reporting": false works too and is never replaced by the defaults. An opt-out written under another spelling also counts as off: a block named usage-reporting, usageReporting or UsageReporting, an enable/Enabled switch that is not clearly on, or "disabled": true; the first launch then writes "usage_reporting": {"enabled": false} next to it. TRACE_USAGE_REPORTING set to anything but blank, true, on, yes or 1 turns it off, and so does DO_NOT_TRACK set to anything but blank, 0, false, off or no.
{
"usage_reporting": {
"enabled": false
}
}The same block also holds endpoint and key, which are only there to be pointed at another trace server. The reporting client is src/trace_client.py, vendored unmodified from trace-client-python (0.5.0).
Details: https://danielstephenson.dev/usage-reporting
The ideas in this project are generalized and expanded upon in the Interakt and Apex projects.
The same game, unmodified, runs in a browser tab under tak's console runtime (Python via Pyodide): https://kreatures.play.danielstephenson.dev, listed with the rest at danielstephenson.dev/play. To build and serve it locally (needs tak installed):
python3 web/build_zip.py
python3 -c "from tak.web.serve import main; main(root='.', title='Kreatures')"
Pushes to master deploy it to arcade (.github/workflows/browser.yml).