Groundwater Commons Serious Game for Farmer Groups and Agriculture Students

The problem: a shared resource nobody can see

Groundwater sits under everyone's land, and each farmer's tube-well draws from the same aquifer. In large parts of Punjab and Balochistan, water tables have been falling for years. Each farmer decides alone how much to pump, and the cost of falling water tables is shared by everyone: deeper bores, more energy, wells that fail. This is a textbook commons problem, but to the people living it, the aquifer is invisible, and "pump less" sounds like a sacrifice that only helps neighbours.

Explaining this with a lecture or a poster rarely changes how people think. Playing it often does.

Agriculture students face a similar gap. They learn about groundwater depletion as figures in a textbook, yet many will go on to advise farmers, run farms or work in water departments. A game that lets them feel the pull between private gain and shared loss, and then discuss what rules might change the outcome, prepares them for conversations they will have for the rest of their careers. A digital version also records every choice, so each session produces data for teaching and research.

What already exists and the gap

• Researchers have run collective action games with farmers on paper, with dice and tokens, followed by facilitated discussion.
• Fishbanks, a classic commons simulation by Dennis Meadows, is widely used in business and policy education for a fishery, not groundwater.
• Classroom economics experiments on public goods and common pool resources are common in universities, usually with abstract tokens.

The gap is a digital groundwater game that a facilitator can run in a village meeting room or a university classroom without specialist staff, in local languages, with automatic scoring, consistent rules and data that can be analysed afterwards.

Inspiration

Playing games to save water: Collective action games for groundwater management in Andhra Pradesh, India (Meinzen-Dick, Janssen and colleagues, World Development, 2018) used games that simulate crop choice and its consequences for the aquifer, followed by community debriefing, both to measure cooperation and to change how communities think about shared groundwater. This project builds a digital version that keeps their core design and makes it easier to run, repeat and study.

What you build

• Players each have a farm. Every round (a season) they choose a crop, from water-thirsty to water-light, and see their private earnings.
• The aquifer falls with total pumping and recovers with recharge. A deeper water table makes pumping cost more for everyone.
• The facilitator changes the rules between blocks of rounds: first no talking, then talking allowed, then the group can vote on a rule such as a crop limit. Players see how outcomes change.
• The debrief screen shows each round's choices, the water table and total earnings, so the group can discuss what happened.

The technically interesting part

• A model that is simple and believable. The aquifer model must be simple enough to understand and still behave in a way farmers recognise. Calibrate parameters so that cooperation pays over many rounds but selfish choices pay in a single round.
• Local multiplayer without internet. One device hosts a WebSocket server on a local hotspot; the others connect. Handle dropped connections and rejoins without losing a round.
• Facilitation design. The dashboard must let a non-technical facilitator run a session confidently, including pausing, correcting mistakes and moving to debrief.
• Measurement. Log decisions so you can compare treatments, and design a short before-and-after questionnaire on how players understand the shared aquifer.

How to evaluate it

• Play sessions: at least three groups, such as agriculture students, a farmer group with a partner organisation, and a class of other students. Compare choices and group earnings across treatments.
• Understanding: before and after questions about how one farmer's pumping affects others, analysed with care given small numbers.
• Facilitator usability: can someone who did not build the game run a session after a short briefing?
• Technical robustness: sessions completed without data loss.

Suggested plan

• Weeks 1 to 3: read the Meinzen-Dick paper and its game protocol; design rules and the aquifer model; play a paper prototype with classmates.
• Weeks 4 to 7: Godot client, local server and round logic.
• Weeks 8 to 10: facilitator dashboard, debrief screen and logging.
• Weeks 11 to 13: play sessions.
• Weeks 14 to 15: analysis, report and demo.

Path to a product

Agricultural extension services, water NGOs and universities teaching environmental economics all need engaging tools for discussing shared resources. The game could be offered freely with paid facilitation training, or adapted for other commons such as canal water or fisheries. It is a strong game portfolio piece because it shows design for a real purpose and evidence that it works.

Scope warning

Keep the art simple and focus on rules, model and facilitation. Do not claim the model predicts any real aquifer; it is a teaching model. When playing with farmers, work through a partner organisation, explain the purpose, never use real money without ethical approval and do not collect personal data you do not need.

Learn what you need on Sefism

• Game development roadmap: game loops, state and multiplayer basics.
• Godot Docs: the engine for the player client.
• Game Programming Patterns: structuring rounds, state and events.
• Game development cheat sheet: networking and testing your game.
• Data analytics roadmap: analysing choices across sessions.

Get help with this idea

The hard parts are a model that feels fair and believable and sessions that run smoothly. Tauseef can help you plan the paper prototype, find a partner for sessions and structure the analysis. If you are new here, create a free account first.

• Discuss this idea with a mentor
• Send a query to Tauseef
• Book a 1:1 session