Skip to main content

Getting Started with Schedule 1 Modding

Welcome to the unofficial Schedule 1 Modding Wiki! This comprehensive guide will help you take your first steps into modding Schedule 1, a Unity-based game with a passionate and growing modding community.

Community Project

This wiki is not affiliated with the game studio or developers. The "Schedule 1" trademark is owned by the game's developers. This is a community-driven resource created by modders, for modders.

Introduction to Schedule 1 Modding​

Schedule 1 is a Unity-based game available on Steam that offers excellent modding potential through the MelonLoader framework. The game's architecture allows modders to create everything from simple quality-of-life improvements to complex gameplay overhauls.

Why Mod Schedule 1?​

  • Active Community: Join a thriving community of modders who actively share knowledge and collaborate on projects
  • Modder-Friendly Codebase: The game's architecture is highly modular and seemingly designed with modding in mind
  • Frequent Updates: Regular game updates provide fresh opportunities and challenges for modders
  • Extensive Modding Potential: From simple tweaks to complete overhauls, the game offers endless possibilities for customization

Understanding the Default and Alternate Branches​

Schedule 1 offers two distinct Steam beta branches that use different Unity scripting backends. Understanding these branches is crucial for effective modding:

Common Misconception

Many new modders mistakenly believe they must only work with the il2cpp branch and that the Mono branch is "different code" that won't help them. This is incorrect! Both branches contain the exact same source code before compilation - the only difference is how Unity compiles the assemblies using different scripting backends.

Default Branch (il2cpp)​

  • What it is: Uses Unity's il2cpp (Intermediate Language to C++) compilation system
  • Compilation: Source code is compiled to optimized native C++ code
  • Modding challenge: The compiled assemblies are harder to analyze and reverse engineer
  • User base: The majority of Schedule 1 players use this branch
  • For modding: Your final mods should target this branch for maximum compatibility

Alternate Branch (Mono)​

  • What it is: Uses traditional Mono .NET runtime compilation
  • Compilation: Source code is compiled to standard .NET assemblies
  • Modding advantage: C# assemblies remain highly readable and easy to analyze
  • Primary use: Code exploration and understanding - this is your window into the game's source code!
  • Key insight: Most things you learn here applies to il2cpp modding too

The Critical Relationship Between Branches​

🔑 Key Understanding: Both branches start with identical C# source code. The differences only appear after Unity compiles them:

  • Mono Branch: Source Code → IL (Intermediate Language in .NET assemblies) → Executed by Mono runtime (easy to read with tools like dnSpy)
  • il2cpp Branch: Source Code → IL (Intermediate Language) → Converted to C++ → Compiled to native code (harder to analyze)

📋 Recommended Workflow:

  1. Start with Mono - Use it to understand classes, methods, and game systems
  2. Learn the game's architecture - Identify what you want to modify
  3. Develop your mod logic - Write and test your modding approach
  4. Adapt for il2cpp - Follow the il2cpp differences guide to handle compilation differences
  5. Test on both branches - Ensure your mod works for all users
Branch Strategy

Don't choose one or the other - use both strategically! The Mono branch is your research tool, while il2cpp is your deployment target. Most experienced modders spend significant time in the Mono branch understanding the game, then apply that knowledge to create mods that work on both il2cpp and mono.

Prerequisites​

Before diving into Schedule 1 modding, ensure you have the necessary foundation:

Basic Programming Knowledge​

Essential Skills:

  • C# Fundamentals: Variables, methods, classes, and basic syntax
  • Object-Oriented Programming: Understanding of classes, inheritance, and polymorphism
  • Basic Unity Concepts: GameObjects, Components, MonoBehaviours, and scene hierarchy
  • Debugging Skills: Ability to read error messages and troubleshoot issues

Helpful (But Not Required):

  • Previous modding experience with other games
  • Familiarity with version control systems like Git
  • Understanding of .NET framework and IL (Intermediate Language)
Critical Legal Requirements

Before you begin modding, you must understand and comply with these legal requirements:

✅ What You Can Do​

  • Analyze and modify your own copy of Schedule 1 that you legally own
  • Create and share your mod code (C# scripts, configuration files, etc.)
  • Document your discoveries and share knowledge with the community
  • Collaborate with other modders on open-source projects

❌ What You Cannot Do​

  • Never distribute copyrighted game assets (textures, models, audio files, etc.)
  • Do not share extracted game content even for "educational purposes"
  • Don't claim ownership of the original game's intellectual property

📋 Best Practices​

  • Share only your mod code not extracted game content
  • Credit the original developers of used assets and respect their intellectual property
  • Document your modifications clearly so users understand what your mod does

System Requirements​

Minimum Setup:

  • Windows 10/11 (other platforms may work but aren't officially supported)
  • Visual Studio Community (free) or another C# IDE
  • At least 8GB RAM for comfortable development
  • A legally owned copy of Schedule 1 on Steam

Learning Path​

This wiki is structured to take you from complete beginner to advanced modder. Follow this recommended progression:

🏗️ Foundation (Required for Everyone)​

  1. Getting Started - Understand the basics of Schedule 1 modding (where you are now)
  2. Core Concepts - Master fundamental modding concepts and patterns
  3. Essential Tools - Install and configure your modding toolkit
  4. Development Environment - Set up Visual Studio and your workspace

🔧 Practical Application​

  1. Creating Your First Mod Template - Build reusable project templates
  2. Creating Your First Mod - Complete walkthrough of mod creation process

🚀 Advanced Topics (Coming Soon)​

  1. Steamworks.NET Networking - Multiplayer mod synchronization
  2. Advanced Harmony Techniques - Complex patching scenarios
  3. Performance Optimization - Making your mods efficient and stable

📚 Reference Materials​

  • Troubleshooting Guide - Solutions to common problems
  • Community Resources - Links to Discord, forums, and additional learning materials

Community & Support​

The Schedule 1 modding community is incredibly welcoming to newcomers and always ready to help:

Getting Help and Support​

  • Ask questions freely - The community loves helping newcomers learn
  • Share your progress - Even small achievements are celebrated
  • Collaborate on projects - Many successful mods are team efforts
  • Document your discoveries - Help expand the knowledge base for future modders

Community Guidelines​

  • Be respectful and patient with newcomers asking questions
  • Share knowledge freely - The community thrives on open collaboration
  • Give credit where it's due - Acknowledge others' contributions
  • Follow legal guidelines - Don't share copyrighted assets

Where to Find the Community​

  • Discord Servers - Real-time chat and voice collaboration
  • Reddit Communities - Discussion and showcase platforms
  • GitHub Repositories - Open-source mod projects and collaboration
  • Steam Community - Game-specific discussions and mod sharing

Setting Realistic First Mod Goals​

For your first modding project, start with something achievable that teaches core concepts:

🎯 Beginner-Friendly Project Ideas​

Simple Console Commands:

  • Add a command to spawn items
  • Create a teleport command
  • Implement a time manipulation command

Basic UI Overlays:

  • Display additional player information
  • Create a simple mod configuration menu
  • Add visual indicators for game states

Quality of Life Improvements:

  • Automatically organize inventory
  • Add keyboard shortcuts for common actions
  • Improve accessibility features

🏆 Success Tips​

  • Start small - Complex projects can overwhelm beginners
  • Test frequently - Small, working increments build confidence
  • Stay Organized - Use a project management tool like Trello or Notion
  • Follow OOP Principles - Use classes, inheritance, and polymorphism to create modular and maintainable code
  • Document everything - You'll thank yourself later, especially if you use in-line XML documentation for IDE support
  • Ask for feedback - The community can spot issues you might miss
  • Use version control - Git saves you from losing progress

Next Steps​

Ready to begin your Schedule 1 modding journey? Let's get your tools set up:

👉 Continue to Essential Tools →

The Essential Tools guide will walk you through installing MelonLoader, dnSpy, Visual Studio, and other software you'll need for successful modding.

Need Help?

Having trouble getting started? Don't hesitate to reach out to the community! Check our troubleshooting section or join the community Discord for real-time help from experienced modders.