Introduction
If you’re drawn to hand-crafted worlds, cozy ecosystems, and the satisfying loop of tending, exploring, and discovering, becoming an UndergrowthGames contributor might be your next favorite creative adventure. I’m opening the canopy to collaborators who care about indie craft and nature-first design—people who want to ship memorable games, learn fast, and leave a gentle footprint on players and the planet.
This guide explains how I approach collaboration, the roles I’m looking for, our creative pillars, and the practical workflows that keep production smooth. Whether you love code, art, audio, narrative, or community-building, there’s space to grow here.
What “UndergrowthGames Contributor” Means
An UndergrowthGames contributor is a creator who joins development on a project-by-project basis, aligned with our values and production cadence. I use a contributor model to keep teams nimble, compensate fairly, and allow people to bring their best skills without the overhead of traditional studio structures.
Contributor Principles
- Respect the biome: we build worlds that honor ecology—mechanically, aesthetically, and ethically.
- Player-first iteration: prototypes early, usability tests often, and balance for clarity over complexity.
- Small team, strong signals: short feedback loops, transparent decisions, and visible milestones.
- Sustainability by design: scope discipline, modular tools, and technical choices that minimize waste.
Focus Areas: Indie and Nature-Themed Games
Nature is the north star. I gravitate toward cozy survival, gentle farming, exploration puzzlers, and creature care sims—the kinds of games where systems interlock like roots underground. Expect mechanics that reward curiosity and stewardship: soil health, water cycles, pollination networks, and seasonal rhythms that affect crafting and strategy.
Tonal Range
- Wholesome, low-conflict experiences with ambient challenge
- Mood-forward adventures with environmental storytelling
- Lightly systemic sandboxes that invite emergent play
Roles I’m Seeking
Game Design and Systems
- Economy, crafting, and progression design balancing long-term arcs with short-session goals
- Combat-light interaction models: harvesting, caretaking, observation, and puzzle loops
- UX flows for tutorials, journals, and diegetic guidance that reduce cognitive load
Programming
- Gameplay feature implementation in Unity or Godot (C#, GDScript)
- Tools and pipeline scripts for exporters, map editors, and data-driven content
- Performance profiling, memory budgets, and platform builds (PC/Switch/mobile)
Art and Animation
- Stylized foliage, terrain shaders, and hand-painted props that age gracefully
- Creature concepting with readable silhouettes and expressive behaviors
- Lightweight rigging and animation blending tuned for cozy interactions
Audio and Music
- Field-recorded Foley, subtle UI chimes, and reactive soundscapes
- Themes that evolve with biome states: weather, time-of-day, and player actions
- Middleware integration (FMOD/Wwise) with parameter-driven layering
Narrative and Community
- Environmental lore, item descriptions, and journal entries that hint rather than tell
- Community management, devlogs, and compassionate moderation
- Accessibility reviews and playtest facilitation
Production Workflow
I keep production humane and predictable with a few core practices that scale from solo to small teams.
Planning and Scoping
- Break work into 1–2 week sprints with visible, testable outcomes
- Define “golden paths” for prototypes; lock stretch goals behind validation
- Budget by effort and dependency, not by hope
Collaboration Stack
- Version control in Git with trunk-based development and protected main
- Task tracking in Linear/Jira with lightweight spec docs in Notion
- Art source in shared libraries; auto-export pipelines into the engine
Testing and QA
- Graybox-to-gold process: verify feel before polish
- Automated checks where feasible: build verifiers, unit tests for core systems
- Regular playtest circles: accessibility, UX friction, and session length tuning
Creative Pillars
Ecology as Mechanic
Systems model mutualism and trade-offs. If you overharvest, soil quality drops; nurture pollinators and yields rise. The best strategies look like good gardening.
Clarity Over Complexity
Every mechanic should read at a glance. I prefer fewer verbs with deeper synergy, supported by strong iconography and tactile feedback.
Player Care
We design for calm: forgiving fail states, generous autosaves, and UI that respects left-handed, color-blind, and low-vision players. Difficulty is an adjustable climate, not a wall.
Tools and Tech
- Engines: Unity (URP) and Godot 4 for fast iteration and robust 2.5D/low-poly looks
- Source: GitHub/GitLab with CI for automated builds and linting
- Data: JSON/ScriptableObjects with localization-ready strings
- Art: Blender, Substance, Aseprite; shaders tailored for wind, water, and seasonal tinting
Contribution Models and Compensation
I support a few paths to participate; we’ll pick the right one per project.
Paid Contracts
Clear deliverables with hourly or milestone-based pay, invoices net-15.
Revenue Share
Documented split tied to recoup and platform fees, with transparent dashboards.
Hybrid
Smaller upfront paired with revenue share for risk-balanced collaboration.
Submission Guidelines
- Portfolio or Git repo demonstrating relevant, shippable work
- One-page pitch: what you want to contribute, timelines, and tools you prefer
- Availability window and time zone; typical weekly capacity
- Any access needs for communication or tooling
Collaboration Etiquette
- Write things down: decisions, assumptions, and risks live in the spec
- Default to kindness and curiosity; critique the work, not the person
- Communicate blockers early; quiet surprises sink schedules
Example Project Tracks
Biome Caretaker (Cozy Strategy)
Tend a micro-reserve across seasons. Balance species needs, craft simple structures, and research upgrades that make ecosystems resilient.
Moss & Memory (Exploration Narrative)
A quiet hike through ruins reclaimed by green. Puzzles emerge from natural patterns—lichen, rivulets, wind.
Ripple Forge (Systems Sandbox)
Chain small ecological reactions—like water flow and seed dispersal—into delightful loops that power settlement growth.
Onboarding Path
- Start with a scoped, low-risk task to align style and expectations
- Pair once weekly for code/art review and roadmap sync
- After two sprints, expand scope or pivot based on mutual fit
Sustainability and Impact
I try to minimize digital waste—smaller builds, shared textures, and efficient shaders. We offset a share of revenue toward conservation partners and encourage volunteering, mentorship, and knowledge-sharing within the community.
How to Reach Out
If you see yourself in this undergrowth—patient, curious, and eager to cultivate—reach out with your portfolio and a note on the role you’re excited about. I review submissions weekly and reply with next steps if there’s a fit. Let’s build something small, sincere, and alive.
