Free Unity C# Scripts and Game Systems: 55 Copy-Paste Tools for Indie Games

This page is a practical index, not a theory article. If you are building an indie game and need working Unity C# code today, use it to pick the right script by problem: movement, camera, health, save/load, UI, AI, mobile input, inventory, dialogue, audio, and utility infrastructure.

The strongest use case is prototyping. You can copy one script into an existing project, or combine a small set of scripts into a playable slice. Each script page includes source code, Inspector notes, usage steps, and common mistakes, so you can adapt the code instead of treating it as a black box.

Choose by Game Problem

Start a Game in 30 Minutes

The fastest path is to pick a small game target and wire only the scripts needed for that slice. Do not begin by importing every script. Start with the smallest set that proves movement, feedback, saving, and one loop.

• 2D platformer: Use 2D Platformer Starter Kit, or combine 2D Player Controller, Smooth Camera Follow 2D, Health System, Pickup / Collectible, and Screen Fader.
• FPS prototype: Use FPS Foundation Kit, or combine 3D Player Controller, First Person Camera, Weapon System, Projectile System, and Camera Shake.
• RPG slice: Use RPG Essentials Kit, or combine Health System, Simple Inventory, Dialogue Trigger, Quest System, and JSON Save Utility.
• Mobile game: Use Mobile Controls Kit, or combine Touch Joystick, Touch Button, Swipe Input Controller, and Mobile Safe Area Handler.
• RTS prototype: Use RTS Starter Kit, or combine Top-Down Camera, NavMesh Click-to-Move, Minimap System, and Wave Spawner.
• Idle game: Use Idle Game System with Idle Income Generator, Timer / Countdown, and PlayerPrefs Save Helper.

Essential Scripts Every Unity Project Needs

Some scripts are useful regardless of genre. These are the pieces that reduce repeated glue code and make prototypes less fragile.

• Object Pool - reuse bullets, enemies, damage numbers, and effects instead of instantiating every time.
• Audio Manager - centralise one-shot sounds, music crossfades and volume.
• Scene Manager - wrap scene transitions so buttons and triggers call one stable API.
• Health System - give players, enemies, breakables, and bosses a consistent damage contract.
• JSON Save Utility - save structured game state without building a save framework from scratch.

The utility layer

Utility scripts decide how painful a project becomes after the first prototype. If bullets, sounds, scene loads, timers and saving are solved differently in every feature, the game gets harder to change. Add this layer early and your feature scripts stay small.

When to skip a utility

Do not add a manager because one exists. A singleton suits one global audio service, not per-enemy state. A pool suits objects spawned again and again, not a single persistent object. PlayerPrefs is enough for one volume setting; a JSON save suits structured game state.

• Pooling without reset: pooled objects must reset health, velocity, animation state and event subscriptions before reuse.
• Global everything: too many singletons make scenes hard to test and set up.
• Audio spam: limit how often a frequent sound can play so one event does not stack dozens of clips.
• Scene names as magic strings: keep scene names in one place if many buttons load scenes.

When Not to Copy a Script Blindly

Copy-paste scripts save time, but they are not magic. Treat every script as a starting point that needs a quick fit check against your project. The goal is speed with control, not mystery code.

• Unity version: Most of these scripts target Unity 2022.3 LTS and newer; a few use Unity 6 physics APIs and need Unity 6. Each script page states its version.
• Input system assumptions: Some scripts use the built-in Input API. If your project uses the newer Input System package, adapt the input wrapper rather than editing gameplay logic everywhere.
• Inspector setup: Many scripts use [SerializeField]. Missing references are the most common setup bug, so read the usage steps before pressing Play.
• Serialization limits: PlayerPrefs is fine for small preferences. Use JSON or a proper save system for game state, inventory, quest progress, or multiple save slots.
• Dependencies: Individual scripts are designed to stand alone where possible. Complete game systems intentionally include multiple scripts that expect each other.

How to Use These Scripts Safely

1. Create a new C# file with the exact class name shown on the script page.
2. Paste the source code and let Unity compile before adding it to objects.
3. Attach the component to the recommended GameObject type, such as Player, Camera, Manager, or UI Canvas.
4. Assign every required Inspector field and read the common mistakes section.
5. Test the script in an empty scene before mixing it into a large project.
6. Rename variables and tune values only after the baseline behavior works.