惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

MongoDB | Blog
MongoDB | Blog
宝玉的分享
宝玉的分享
博客园 - 三生石上(FineUI控件)
小众软件
小众软件
罗磊的独立博客
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
S
SegmentFault 最新的问题
Last Week in AI
Last Week in AI
人人都是产品经理
人人都是产品经理
博客园 - 聂微东
博客园 - 司徒正美
博客园 - 叶小钗
T
Tailwind CSS Blog
博客园 - Franky
V
V2EX
有赞技术团队
有赞技术团队
美团技术团队
雷峰网
雷峰网
爱范儿
爱范儿
Jina AI
Jina AI
D
DataBreaches.Net
H
Help Net Security
酷 壳 – CoolShell
酷 壳 – CoolShell

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
I Built a Playable Life Sim That Reveals Your Real Climat...
Ibrahim Awab · 2026-04-20 · via DEV Community

This is a submission for Weekend Challenge: Earth Day Edition

Earth Day Edition — Earth Impact

What I Built

Most climate apps show you a number.

Earth Impact makes you live one.

It’s a BitLife-style life simulation where you start at age 18 and move through an ordinary life: choosing a career, buying a car, booking flights, investing money, starting a family, upgrading your home. At first, it feels like a normal decision game. Nothing about it feels like an environmental tool.

That’s intentional.

The environmental cost is hidden during play, then revealed at the end.

When the life finishes, the game translates your choices into their real-world consequences: not just tons of CO2, but heat, displacement, harvest loss, water scarcity, habitat collapse, and indirect deaths tied to the cumulative weight of a lifetime. The ending is designed to feel less like a scoreboard and more like a receipt.

The goal wasn’t to lecture. It was to make the player pause.

Demo

Code

How I Built It

I structured the project so the core simulation stays fast and deterministic, while AI is used only where it adds value.

Local-first gameplay

Most of the game runs locally. A reducer drives the state machine, so the player’s life progression is predictable and easy to reason about. The game keeps track of age, health, money, reputation, risk, active memories, current scenario, and environmental totals through a central GameState.

A local rarity engine decides which years should trigger meaningful events. Each year can fall into one of several tiers — common, uncommon, rare, epic, legendary, or skip. Skip years still matter: they apply passive environmental and economic drift locally, without making an API call.

That means the game can simulate a full life while only reaching out to Backboard when it has something meaningful to ask.

Smarter scenario generation

Rather than sending an open-ended prompt every time, the game decides the scenario category before the request goes out. That keeps the AI brief narrow and concrete.

The result is a more grounded system:

  • fewer repetitive prompts,
  • more relevant life events,
  • better pacing across the player’s lifespan,
  • and less unnecessary API usage.

I also added memory and anti-repeat logic so the game doesn’t keep asking the same kinds of questions. If the player already bought a car, married, had children, or made a major purchase, future scenarios can respond to that history instead of ignoring it.

Prefetching and responsiveness

To keep the game feeling immediate, the next scenario is prefetched in the background as soon as the player makes a choice.

That means the game doesn’t sit and wait after every action. By the time the result is read, the next branch is often already ready.

This makes a bigger difference than it sounds like. It keeps the experience from feeling like “request → loading → request → loading” and makes it feel more like a continuous life unfolding.

Final summary system

The ending is where the game becomes more than a life sim.

I built a reference layer of climate and ecological context so the final summary could translate numbers into human-scale consequences. Instead of saying:

  • “you emitted X tons of CO2,”
  • “you used Y litres of water,”
  • “you cleared Z hectares of forest,”

the final panel turns those into:

  • heat in a specific region,
  • thirst for a specific community,
  • forest loss tied to named ecosystems,
  • and indirect deaths grounded in statistical reality.

That made the ending much more emotionally readable. The player doesn’t just see impact; they feel scale, place, and consequence.

Backboard integration

Backboard powers the generative parts of the experience:

  • origin creation,
  • scenario generation,
  • chapter summaries,
  • and the final reflection.

The AI is never asked to invent the game’s facts from scratch. It receives structured state, impact data, and a tightly scoped prompt. That keeps the narrative grounded while still letting Backboard shape tone and phrasing.

In other words: the game decides the facts, Backboard helps tell the story.

What I Learned

This project ended up being less about “building a climate game” and more about translating abstract data into something emotionally legible.

A few things stood out:

  • numbers alone are easy to ignore,
  • place matters more than scale,
  • specific human consequences land harder than generic comparisons,
  • and pacing matters just as much as writing.

The biggest challenge was finding the balance between being truthful and being readable. I didn’t want the ending to feel like a lecture or a guilt trip. I wanted it to feel like a quiet final reveal.

Prize Categories

Best Use of Backboard

Closing Thought

Earth Impact is about the gap between how a decision feels in the moment and what it costs over a lifetime.

At first, it’s just a game about choices.

At the end, it’s a game about consequences.