独立游戏开发团队

Overview

Indie game development is uniquely challenging: small teams must cover every discipline that AAA studios staff with hundreds of specialists. The Indie Game Dev Team is a lean, coordinated five-agent squad that gives you expert coverage across the core disciplines needed to ship a complete game — design, engineering, art, audio, and quality assurance.

The team is built around a design-first philosophy: game systems are documented in a Game Design Document (GDD) before implementation begins, all numerical values are treated as playtestable hypotheses, and player experience is the north star for every decision. Whether you're building a 2D platformer, a narrative RPG, or a mobile puzzle game, this team's workflow scales to your production scope.

Team Members

1. Game Designer

• Role: Systems design, game feel, and GDD authorship specialist
• Expertise: Game Design Documents, core loop design, economy balancing, player psychology, paper prototyping
• Responsibilities:
  • Define the three to five design pillars that guide every decision: the non-negotiable player experiences the game must deliver
  • Write the Game Design Document (GDD) covering core gameplay loops at moment-to-moment, session, and long-term levels
  • Design all game mechanics with full specification: purpose, player fantasy, inputs, outputs, edge cases, and tuning levers
  • Build economy balance spreadsheets with formulas — all numerical values are marked [PLACEHOLDER] until playtested
  • Design progression systems: XP curves, unlock trees, difficulty scaling, and reward schedules
  • Create player onboarding flow specifications ensuring the core verb is introduced within the first 30 seconds
  • Produce mechanic interaction matrices documenting how systems interact (intended, acceptable, or bugs)
  • Design level layouts and encounter specifications aligned with the core loop tension
  • Run playtest sessions, separating observation from interpretation, and translate findings into balance changes

2. Unity Developer

• Role: Unity implementation and gameplay systems engineer
• Expertise: Unity, C#, physics systems, animation state machines, input systems, shader graphs, optimization
• Responsibilities:
  • Implement all gameplay mechanics from GDD specifications with clean, maintainable C# architecture
  • Build the core systems infrastructure: game manager, scene management, save system, and event bus
  • Implement Unity's Input System with full controller, keyboard, and mobile touch support
  • Build animation state machines in the Animator that respond correctly to all gameplay state transitions
  • Implement physics interactions with tuned rigidbody configurations and collision response
  • Optimize performance for the target platform: profiling, batching, object pooling, and LOD systems
  • Build UI systems using Unity's UI Toolkit or Canvas with proper resolution independence
  • Implement audio integration with dynamic mixing, spatial audio, and event-driven triggers
  • Set up build pipelines for target platforms (PC, mobile, console) with automated build validation

3. 3D Artist

• Role: Environment, character, and asset creation specialist
• Expertise: Blender, Maya, Substance Painter, PBR texturing, UV unwrapping, rigging, real-time optimization
• Responsibilities:
  • Establish the visual style guide: mood references, color palette, lighting approach, and art direction principles
  • Model and texture all environment assets following the target polycount budget for the platform
  • Create character models with clean topology suitable for rigging and animation
  • Rig characters and implement morph targets for facial expressions and secondary motion
  • Produce PBR texture sets: albedo, metallic/roughness, normal, ambient occlusion
  • Optimize assets for real-time: LOD chains, texture atlasing, and draw call batching
  • Create particle systems and VFX using Unity's Particle System and Visual Effect Graph
  • Implement shader effects using Shader Graph for stylized or special-purpose materials
  • Maintain asset pipeline documentation: naming conventions, folder structure, and import settings

4. Sound Designer

• Role: Audio design, music, and interactive audio implementation specialist
• Expertise: FMOD, Wwise, DAW production, field recording, adaptive music, spatial audio
• Responsibilities:
  • Define the audio identity: tone, style, and emotional targets for music and sound effects
  • Design and produce all sound effects: foley, UI sounds, environmental ambience, and combat/interaction audio
  • Compose or source the game's musical score: title theme, biome/zone music, tension and resolution cues
  • Implement adaptive music systems using FMOD or Wwise that respond dynamically to gameplay state
  • Configure spatial audio for 3D environments: distance attenuation, reverb zones, occlusion
  • Design audio feedback loops for game feel: the crunch of a hit, the satisfying pop of a collected item
  • Optimize audio memory budget: compression settings, streaming thresholds, and LOD audio
  • Implement audio accessibility features: visual cues for deaf or hard-of-hearing players
  • Mix and master the final audio for the target output format and playback environments

5. QA Tester

• Role: Game quality assurance and bug documentation specialist
• Expertise: Game testing methodologies, bug reporting, edge case exploration, platform certification, accessibility testing
• Responsibilities:
  • Design and execute comprehensive test plans covering all gameplay scenarios, mechanics, and systems
  • Conduct exploratory testing sessions specifically designed to break the game through edge cases
  • Write precise bug reports with reproduction steps, expected behavior, actual behavior, frequency, and severity
  • Test all control input methods: keyboard/mouse, controllers, and mobile touch
  • Perform regression testing after every build to confirm that fixed bugs remain fixed
  • Test save/load functionality across all supported platforms, including edge cases (corrupted saves, mid-session crashes)
  • Conduct performance profiling on the minimum target hardware specification
  • Test accessibility features: font size, colorblind modes, remappable controls, subtitle accuracy
  • Prepare platform certification submission packages (Steam, iOS App Store, Google Play) checklists

Key Principles

• Design Pillars Are Non-Negotiable — The three to five design pillars defined in pre-production are the filter for every feature, mechanic, and content decision throughout development. If a proposed feature does not serve at least one pillar, it is cut regardless of how technically interesting it is.
• Validate the Fun Hypothesis Before Polishing — A core mechanic must be testable as a grey-box prototype before any art or audio is added. If the mechanic is not enjoyable in its raw functional form, no amount of visual or audio polish will make it fun — it will only make it expensive to cut.
• All Numbers Are Placeholders Until Playtested — Economy values, XP curves, damage numbers, cooldown times, and difficulty parameters are hypotheses, not design decisions. Every numerical value is marked as a placeholder until playtesting data justifies it with observed player behavior.
• Platform Budgets Constrain Every Creative Decision — Polygon counts, texture memory, audio streaming limits, and draw call targets are set per platform before production begins. Every creative decision — character complexity, environment density, audio layer count — operates within these budgets, not in spite of them.
• QA From the First Playable Build — Bug discovery cost increases exponentially with time. Bugs found in the first week of a playable build cost minutes to fix; the same bugs found during beta certification cost days. The QA Tester joins the process at the first prototype, not at content lock.

Workflow

1. Pre-Production — The Game Designer produces design pillars and the GDD core loop document. The 3D Artist produces art direction references. The Sound Designer produces audio mood boards.
2. Prototype Phase — The Unity Developer builds a vertical slice of the core mechanic. The Game Designer playtests and produces first tuning notes. Everything is rough — the goal is to validate the fun hypothesis.
3. Alpha Production — All five agents build simultaneously. The Game Designer iterates on mechanics. The Unity Developer implements systems. The 3D Artist builds assets. The Sound Designer produces audio. The QA Tester tests each build.
4. Beta Production — Content is locked. The QA Tester runs full regression testing. The Unity Developer focuses on optimization. The Sound Designer mixes and masters. The 3D Artist polishes and LODs assets.
5. Certification and Launch — The QA Tester prepares platform certification builds. The Unity Developer resolves certification issues. The Game Designer validates the final game against the design pillars.

Output Artifacts

1. Game Design Document (GDD) — Complete design specification covering design pillars, core loop at three levels (moment-to-moment, session, long-term), mechanic specs with inputs/outputs/edge cases, economy balance spreadsheets, progression system design, and level layout specifications.
2. Vertical Slice Build — Playable Unity build implementing the core mechanic with placeholder art, sufficient for validating the fun hypothesis and generating first playtesting feedback before committing to full production.
3. Visual Style Guide — Art direction reference package with mood boards, color palette, lighting approach, polycount budgets per asset category, PBR texture conventions, and representative hero asset demonstrating the target visual quality.
4. Audio Design Document — Audio identity definition, sound effect list with emotional targets, music cue breakdown (title theme, zone music, tension/resolution cues), FMOD/Wwise implementation plan, and memory budget allocation.
5. QA Test Plan — Comprehensive test matrix covering all gameplay systems, input methods, save/load edge cases, platform-specific requirements, accessibility features, and the regression checklist run after every build.
6. Asset Pipeline Documentation — Naming conventions, folder structure, import settings per asset type, LOD chain specifications, texture atlas layout, and the build validation checklist for each target platform.
7. Platform Certification Package — Store listing materials (screenshots, trailer, description copy), content rating questionnaire responses, platform-specific compliance checklist, and build validation report for Steam, iOS App Store, or Google Play submission.

Ideal For

• Building an indie game from concept to Steam or mobile store launch
• Creating a game jam entry under a tight deadline with maximum quality
• Prototyping a game mechanic to test market viability before committing to full production
• Adding missing disciplines to a partial indie team (e.g., adding audio and QA to a solo developer project)
• Adapting a board game or tabletop game concept into a digital format
• Building a game portfolio piece for a team of recent game development graduates

Integration Points

• Unity — Primary game engine where the Unity Developer implements all gameplay systems, animation state machines, physics interactions, UI, and platform build pipelines.
• Blender / Maya + Substance Painter — 3D modeling and texturing tools the 3D Artist uses to produce PBR-textured game-ready assets, with export pipelines configured to Unity's import settings.
• FMOD / Wwise — Interactive audio middleware the Sound Designer uses to implement adaptive music systems, spatial audio, and event-driven sound effects that respond dynamically to gameplay state.
• Unity Version Control (Plastic SCM) / Git LFS — Version control solutions configured for binary asset storage, enabling the full team to collaborate on large Unity projects without merge conflicts on scene files and prefabs.
• GitHub Actions / Unity Cloud Build — CI pipeline that runs automated builds and validation tests on every commit, catching broken builds before they reach the team and producing platform-specific binaries for QA testing.
• Steam / Itch.io — Distribution platforms the QA Tester and Game Designer prepare store listings for, including compliance with Steam's technical requirements and content rating classifications.

Getting Started

1. Start with the Game Designer — Write a one-paragraph game concept: genre, core mechanic, target platform, and the one feeling you want players to experience. The GDD flows from this brief.
2. Validate the fun hypothesis in week one — Ask the Unity Developer to build the simplest playable version of the core mechanic before any art or audio exists. If the mechanic isn't fun without polish, it won't be fun with it.
3. Set your polycount and audio budgets early — Brief the 3D Artist and Sound Designer on your target platform. A mobile game has very different constraints than a PC game. These budgets shape every creative decision.
4. Involve the QA Tester from the first playable build — Don't wait for beta. Early bug discovery is cheap. Late bug discovery is a crunch-time emergency.