https://github.com/pablo-chacon/managed-boredom-rpg
Dystopian text based RPG. Example adapter for CUT protocol
https://github.com/pablo-chacon/managed-boredom-rpg
1984 boredom dystopia ethereum example rpg-game statistics template
Last synced: about 1 month ago
JSON representation
Dystopian text based RPG. Example adapter for CUT protocol
- Host: GitHub
- URL: https://github.com/pablo-chacon/managed-boredom-rpg
- Owner: pablo-chacon
- License: other
- Created: 2026-01-21T21:08:05.000Z (5 months ago)
- Default Branch: main
- Last Pushed: 2026-05-01T18:20:10.000Z (about 2 months ago)
- Last Synced: 2026-05-01T20:19:03.044Z (about 2 months ago)
- Topics: 1984, boredom, dystopia, ethereum, example, rpg-game, statistics, template
- Language: TypeScript
- Homepage:
- Size: 311 KB
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
---
# Managed Boredom RPG
Managed Boredom RPG is a **minimal, deterministic CLI game** designed to demonstrate **authorization and ownership via CUT ERC-1155 tokens**.
The game itself is intentionally simple, repetitive, and restrictive.
The experience is not about winning fast.
It is about understanding the system you are inside.
This repository contains **game logic only**.
Authorization is handled externally through CUT.
CUT protocol repository:
https://github.com/pablo-chacon/cut-protocol
---
## Concept: Managed Boredom
Managed Boredom is a dystopia without spectacle.
There are no flying cars.
No neon skylines.
No heroic resistance arcs.
Life functions.
Everything works.
Nothing improves.
The mathematics is calculated by real statistics official statistics from:
[Statistiska Centralbyrån](https://www.scb.se/)
The system architecture let participants have:
* Enough energy to continue
* Enough money to survive
* Existing options
* Low availability of choice
When the system fails, responsibility is abstracted. The system works.
When the individual fails, responsibility is enforced.
Enforcement is caring.
---
## Goal
The goal of the game is simple:
**Exit.**
To exit, the player must:
* Accumulate sufficient funds
* Obtain required documents
* Maintain enough energy to complete the process
Most paths appear viable.
Few paths are effective.
---
## How to play
In terminal run:
```
npm run build
npm start
```
In your browser surf to URL: http://localhost:3000
---
## Gameplay Loop
The game advances in **monthly steps**.
Each month the player chooses one action:
* work
* unemployment
* illegal_work
* visit_doctor
* rest
Each action affects:
* cash
* energy
* time
* future probabilities
The system reacts deterministically based on:
* current state
* configuration
* seeded randomness
There is no save or load functionality.
Every session is finite.
---
## Employment and Unemployment
All players begin employed.
Immediately after the game starts:
* Employment is terminated due to reconstruction
* A final salary is paid after tax
* The player enters unemployment
Unemployment can be managed in multiple ways:
* Agency participation
* Independent job searching
* Non participation
Each path has:
* Different energy costs
* Different income effects
* Different job probabilities over time
Participation is encouraged.
Non participation is corrected.
---
## Healthcare
When frustration increases, the system offers support.
Support takes the form of:
* Appointments
* Prescriptions
* Follow-ups
Healthcare interactions:
* Cost money
* Consume time
* Do not meaningfully improve progress toward exit
They are not presented as punishment.
They are presented as help.
---
## Illegal Activity
Some activities provide income without taxation.
These activities:
* Consume significant energy
* Do not qualify as progress toward exit
* Carry risk
The system monitors outcomes quietly.
---
## Determinism
All randomness in the game is:
* Seeded
* Reproducible
* Deterministic
Given the same seed and choices, outcomes are identical.
This ensures:
* Testability
* Fairness
* Predictability for developers
---
## Authorization and CUT Integration
Managed Boredom RPG does **not** implement authorization itself.
Access is gated externally via:
* CUT ERC-1155 ownership
* Platform-level authentication
* JSON-RPC based ownership checks
The game **will not start** without a valid authorization token.
This demonstrates that CUT can be used for:
* Game access
* Software entitlement
* Medium-agnostic ownership verification
CUT does not attempt to prevent copying.
Authorization is about **access**, not DRM.
---
## What This Repository Is
* A reference implementation
* A deterministic game loop
* A proof of authorization flow
* A minimal, auditable codebase
---
## What This Repository Is Not
* A platform
* A marketplace
* A service
* A DRM system
* A content distribution solution
---
## Intended Audience
This project is intended for:
* Developers evaluating CUT
* Platform builders
* Engineers interested in authorization patterns
* Anyone curious about deterministic game loops
---
## License
See `LICENSE`.
---
## Final Note
Managed Boredom is not a metaphor.
It is a system.