evennia
Python MUD/MUX/MUSH/MU* development system
Not yet verifiedsource: GitHubhomepagePythonBSD-3-Clausecommit a89a9b94e4d7
Python, BSD-3-Clause licensed. The project labels itself: based, django, engine, game development, game engine, gamedev, hacktoberfest and moo.
evennia has not been verified yet.
Measured by Argusic on a fresh machine every time. Every number links to its evidence.
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the most recent recorded attempt, which did not reach a verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Migration 0017 uses get_operations() pattern never called by Django 5.1+
- EvenniaLogFile accesses settings at class definition time
- Twisted reactor conflicts when running multiple test modules in one process
- Install time
- 2 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- evennia test passed: test_server (9), test_launcher (15), test_gametime (13), test_dbserialize (17), all OK
- Model tokens used
- 317,893
- Exact commit tested
- a89a9b94e4d7
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Cold machine to finish
- the attempt was stopped at the time limit after 95 minutes, so it never finished
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
exec
/bin/sh -lc 'cd /work/repo/.isocheck && timeout 120 /home/runner/.local/bin/uv run evennia test eve…
exec
/bin/sh -lc 'cd /work/repo/.isocheck && timeout 120 /home/runner/.local/bin/uv run evennia test eve…
succeeded in 51362ms:
Ran 1 test in 10.243s
OK
Destroying test database for alias 'default'...
TESTING: Using Evennia's default settings file (evennia.settings_default).
(use 'evennia test --settings settings.py .' to run only your custom game tests)
Found 1 test(s).
System check identified no issues (0 silenced).Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Ran out of time | 0.00 | 0.65 |
Topics (from GitHub)
baseddjangoenginegame-developmentgame-enginegamedevhacktoberfestmoomudmultiplayermushmuxpythontexttext-basedtext-based-adventuretwistedwebclientwebserver
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/evennia)Questions
- Does evennia run?
- evennia has not been fully verified yet. No recorded run has produced a verdict yet.
- How did Argusic test evennia?
- On a fresh, disposable machine, with every command recorded. One attempt is recorded, and the full method is on the methodology page.
- Where is the evidence for evennia?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.