OpenAI 2026 hackathon

Of Rice and Rent

Of Rice and Rent is a multiplayer historical survival game where families struggle through economic upheaval, scarce work, rising debt, and impossible choices.

Solo project by Florinel Tudor · 0 likes · 0 comments

Archive position — measured, not model output

0 likes on Devpost

2,264 of the 7,856 archived projects have more likes, and 5,592 share exactly 0 — so this project's #5,642 place in the like-ranked listing is a tie-break inside that group, not a ranking.

Projects (log scale)

1
10
100
1k
10k
05,592
11,758
2285
3–4132
5–975
10+14

Likes on Devpost. ▲ marks this project's group.

Show the figures
LikesProjectsShare of archive
05,59271.2%
11,75822.4%
22853.6%
3–41321.7%
5–9751.0%
10+140.2%
Devpost like counts for all 7,856 archived projects, captured when this archive was built.

Executive Summary

Of Rice and Rent is a self-reported multiplayer historical survival game designed for educational workshops and facilitated team-learning sessions. The author states that it simulates economic upheaval from 1919–1942, where players take on family roles and make decisions around scarce resources, debt, and survival. It is built with cloudflare, express.js, javascript, jest, node.js, react, vercel, and uses GPT-5.6 Sol as a development collaborator.

The project is described as a learning experience led by a facilitator, not a standalone product for general consumers. The author claims it sparks discussion about personal choice, policy, and cooperation during financial crises. It includes elements like action cards, resource management, and historical outcome comparisons.

Key commercial due-diligence question: Is this an educational tool or a game with potential for broader adoption? The description does not indicate any revenue model, customer base, or commercial traction beyond a hackathon submission.

Back to contents

What The Product Actually Is

The description states that Of Rice and Rent is a multiplayer historical survival game. It is designed to be played in facilitated sessions, where players take on family roles and make decisions under economic stress. Players receive different household backgrounds, choose action cards, and compete or cooperate for scarce resources.

It includes:

  • A gameplay loop involving resource management
  • Historical context (1919–1942)
  • A final debrief phase that compares outcomes with historical data
  • Facilitator-led structure

The author claims the game is built using cloudflare, express.js, javascript, jest, node.js, react, vercel, and was prototyped with GPT-5.6 Sol.

Inference: The product appears to be a facilitated educational simulation, not a consumer-facing game or SaaS product. It is not described as a standalone experience for individuals.

Back to contents

Positioning & Claim Evolution

The author positions Of Rice and Rent as:

  • A historical learning experience
  • A tool for educational workshops
  • A way to spark discussion about economic crises, personal choices, and public policy
  • An alternative to memorizing history through facts and dates

It is described as inspired by works like Of Mice and Men, focusing on the lives of ordinary people during historical upheaval.

The author also claims:

  • The game can be played in facilitated team-learning sessions
  • It includes historical outcome comparisons to help players understand their choices
  • It was built using AI tools (GPT-5.6 Sol) for prototyping and debugging

Inference: The positioning is educational and experiential, not commercial or consumer-facing.

Back to contents

Target Customer & ICP

The description states that the game is designed for:

  • Educational workshops
  • Facilitated team-learning sessions

It is not described as targeting individual players or general consumers. The author mentions it was presented to a team and used in a weekly meeting, suggesting internal corporate or academic use.

Inference: The target customer appears to be educators, facilitators, or training organizations, not end-users or consumers.

Back to contents

Business Model & Pricing Evidence

The description does not contain any evidence of:

  • Revenue model
  • Pricing structure
  • Monetization strategy
  • Customer acquisition or retention plans

It is described as a hackathon submission and a facilitated educational tool, with no indication of how it would be sold or distributed.

Inference: No business model or pricing evidence is provided. The project appears to be an experiment or prototype, not a commercial offering.

Back to contents

Technical & Delivery Signals

The author states:

  • Built with cloudflare, express.js, javascript, jest, node.js, react, vercel
  • Prototyped using GPT-5.6 Sol for interface design, gameplay loop, server architecture, and debugging
  • Challenges included protecting private family information, distinguishing host from players, and managing large Codex sessions

The author also mentions:

  • Future plans include reconnection support, saved sessions, turn timers
  • Integration of more family backgrounds, scenarios, and regional circumstances

Inference: The technical stack is standard for web-based multiplayer applications. AI tools were used in development, but no evidence of production-grade infrastructure or scalability.

Back to contents

Traction & Maturity Signals

The description states:

  • The game was presented at a team’s weekly meeting
  • It took longer than expected (close to an hour) to complete
  • Players saw how they fared percentage-wise compared to historical data
  • The author is planning more polish and reliability features

There is no evidence of:

  • External users or customers
  • Revenue or monetization
  • Product adoption beyond a single team
  • Any measurable impact or usage metrics

Inference: No traction or maturity signals are evident. It remains an early-stage prototype.

Back to contents

Competitive Context

The description does not mention any competitors or similar products. It is unclear whether there are existing tools for:

  • Historical simulations
  • Educational multiplayer games
  • Facilitated learning experiences

No market positioning or competitive differentiation is stated.

Inference: No competitive context is provided. The project appears to be a standalone concept with no known peers in the space.

Back to contents

Key Risks & Red Flags

Key risks and red flags based on the description:

  • Lack of commercial traction or revenue model
  • No evidence of customer base or adoption beyond a single team
  • Prototype nature, not yet production-ready
  • Heavy reliance on AI tools for development (not scalable or sustainable)
  • Unclear path to monetization or distribution
  • No evidence of scalability or long-term viability

Inference: The project is in an early phase and lacks commercial or product-market fit signals.

Back to contents

Diligence Questions To Ask The Founders

  1. What is the intended audience for this game beyond internal workshops?
  2. Are there any plans to monetize it, and if so, how?
  3. How does the facilitator-led model scale, and what are the barriers to adoption?
  4. Has the game been tested with external users or educators?
  5. What are the long-term goals for the product — is it a prototype or a scalable offering?
  6. How do you plan to manage or reduce reliance on AI tools in development?

Back to contents

Investment/Partnership Verdict

Not evidenced.

The description provides no evidence of:

  • Revenue
  • Customers
  • Product-market fit
  • Commercial traction
  • Scalability
  • Monetization strategy

This is a self-reported hackathon project, not a commercial product or business. It is described as an educational simulation for facilitated sessions, with no indication of market demand or commercial viability.

Confidence: Low. The evidence is limited to the author’s own account and does not support any conclusion about traction, scalability, or investment potential.

Back to contents

Source

Submitted to the OpenAI 2026 hackathon on Devpost. Project home on DevPost.

The analysis above was generated by a language model from the project's own one-line description. It is not independent research and contains no verified traction, revenue or customer data.