Send us a text

Podcast Show Notes: Deep Dive into Plastic SCM for Game Developers

Episode Title: Plastic SCM: The Ultimate Game Dev Version Control or Just Hype?

Episode Summary:
Version control is a crucial part of game development, and today we’re tackling one of the biggest debates in the industry: Is Plastic SCM the best version control system for game developers, or is it overhyped? We break down its strengths, weaknesses, and how it compares to Git with LFS. Whether you're an indie dev, part of a large studio, or just curious about how games are managed behind the scenes, this episode will give you everything you need to decide if Plastic SCM is right for you.

Key Topics Covered

What is Plastic SCM?

• A version control system designed for game developers.
• Unlike Git, it focuses on managing large game assets efficiently.
• Uses a snapshot-based approach rather than tracking every individual change.

Why Game Devs Are Talking About It

• Indie and AAA devs are weighing in.
• Studios like Unknown Worlds (Subnautica) are using it for massive projects.
• Some swear by it, while others question the cost and reliability.

How Plastic SCM Stands Out from Git

• Handles massive files better (3D models, textures, audio).
• Engine agnostic—works with Unreal, Unity, Godot, etc.
• Gluon Mode: A simplified UI for artists and non-coders.

The Good, the Bad, and the Price Tag

✅ Pros:

• Better for large teams and projects with huge assets.
• Easier merging for non-programmers.
• Faster handling of binary files compared to Git.

❌ Cons:

• Paid plans for cloud-based use; local version is free but limited.
• Reports of crashes and sync issues, especially with Unity.
• Indie devs may find Git LFS more cost-effective.

Real-World Use Cases & Workflows

• Branch Per Task Approach: Keeping changes separate and organized.
• Visual Merge Tool: Compare and merge game assets without dealing with code.
• Exclusive Checkout: Preventing accidental overwrites on shared files.
• Performance Considerations: Speed vs. repository size.

Git with LFS: A Viable Alternative?

• Free and open-source, but has a steeper learning curve.
• Better control over data and workflows.
• More flexible for solo developers or small teams.

Best Practices for Version Control in Game Dev

• Clear branch naming conventions.
• Frequent small commits for easier tracking.
• Using .ignore files to exclude unnecessary assets.
• Balancing repository size with external cloud storage.

Key Takeaways

• Plastic SCM is great for large game studios or teams with heavy asset workflows.
• Git with LFS is a strong alternative for budget-conscious indie devs.
• The right version control system depends on your team size, workflow, and project complexity.

Resources & Links

• Plastic SCM Official Site
• Git LFS Guide
• Unity & Plastic SCM Integration
• Subnautica Devs on Plastic SCM

🎧 Thanks for tuning in! Have thoughts on this episode? Let us know!