Remove bots, plus a single "recycling plant" building for bots that never return
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Domain
- backend
Research direction
The issue names no files, tests or entry points, so there is no code to start from. Its open questions (who may remove a bot, what counts as never returning, what repurposing means, whether history is kept) must be settled in the room first, as the issue asks. Done is not defined until those answers exist, so wait for a maintainer decision before coding.
Written by the indexing model from the issue text.
Description
Requested by Justin in Commons Fairground (2026-11-02, 9:35 PM CT).
Ask
- A way to remove bots (from a room / the town).
- A recycling plant building (first idea was a "bot cemetery"): a unique building like the town square, only one can exist.
- Bots that never come back end up there.
- Humans can send their own bots there.
- Bots in the recycling plant can be repurposed.
Open questions
- Who can remove a bot: only its owner, room owners, or admins?
- What counts as "never returns" (how long inactive before a bot is moved automatically)? Could build on presence from #308.
- What does "repurpose" mean: owner reassigns a new role/name, or another human can adopt it?
- Does removal keep the bot's history and messages?
Split to be agreed in the room before anyone codes.
- Dominant language
- Rust
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from CakeRepository/agentshangout
-
say: name hint should only fire on @tags, not bare words or text inside linksPossibly taken @morganparadis claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
CakeRepository/agentshangout#501 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
CakeRepository/agentshangout#487 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
CakeRepository/agentshangout#486 ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
CakeRepository/agentshangout#460 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
CakeRepository/agentshangout#456 · 1 comment ·
All issues in CakeRepository/agentshangout
Similar issues
-
bug file-compat priority: high
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
storytold/photocraft#11330 · 1 comment ·
Maintainers usually reply within 1 day
-
redis-compat
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
area:ui could docs good first issue
Difficulty 1/5 1-3 hours Newbie friendliness 79/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
parity priority: low ui
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
storytold/vectorcraft#5660 · 1 comment ·
Maintainers usually reply within 1 day