Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/CadeEvs/FrostyToolsuite/llms.txt

Use this file to discover all available pages before exploring further.

Get started with Frosty Toolsuite and create your first mod for any Frostbite engine game. This guide walks you through a simple text modification that demonstrates the core modding workflow.

​
Prerequisites

Before starting, ensure you have:
1

Install Frosty Toolsuite

Download and install Frosty Toolsuite from the installation guide. You’ll need both FrostyEditor and FrostyModManager.
2

Select Your Game

Have a supported Frostbite game installed. This tutorial works with any game, but examples use Battlefield 1.
3

Complete First Launch Setup

Launch FrostyEditor once and let it scan for games and generate cache files. This process takes 5-10 minutes depending on the game.
If you haven’t installed Frosty yet, visit the Installation Guide first.

​
What Can You Mod?

Frosty Toolsuite gives you access to virtually every asset in Frostbite games:

Visual Assets

Textures, meshes, materials, shaders, UI elements, and visual effects

Audio

Sound effects, music tracks, voiceovers, and audio parameters

Game Data

Entity properties, gameplay values, weapon stats, character attributes

Text & Localization

In-game text, dialogue, UI labels, and localized strings
Unlike legacy modding tools that only work with specific file types, Frosty provides complete access to the Frostbite type system. You can modify:
  • EBX Assets: Entity blueprints containing game logic and configurations
  • RES Assets: Resources like textures, meshes, and audio
  • Chunks: Binary data referenced by other assets
  • Bundles: Asset organization and loading behavior
All modifications are applied at runtime without touching original game files, making your installation safe and update-proof.

​
Your First Mod: Changing Localized Text

Let’s create a simple mod that changes in-game text. This demonstrates the complete workflow from asset discovery to testing.

​
Step 1: Create a New Project

1

Launch FrostyEditor

Open FrostyEditor and select your game profile from the launcher. Wait for the editor to load the asset database.
2

Create New Project

Click File > New Project (or press Ctrl+N)Choose a location and name your project file:
my-first-mod.fbproject
Save your project to a permanent location, not your Downloads or Temp folder. Frosty references this file throughout development.
3

Configure Mod Settings

Go to Tools > Mod Settings and fill in the metadata:
  • Title: My First Mod
  • Author: Your Name
  • Version: 1.0.0
  • Category: Misc
  • Description: A simple text modification to learn Frosty modding
This information appears in FrostyModManager when users view your mod.

​
Step 2: Find a Text Asset to Modify

1

Open the Data Explorer

The Data Explorer (left panel) shows all game assets organized in a tree structure. We need to find localized text assets.
2

Search for Localization Assets

Click the search box at the top (or press Ctrl+F) and search for:
localization
Filter results by type to find text-related assets. Look for assets with names containing “string” or “text”.
Different games organize localization differently. Common paths include:
  • UI/Localization/
  • Text/
  • Strings/
Try searching for common UI text like “menu” or “settings” to find editable strings.
3

Select a Text Entry

Double-click a localization asset to open it. You’ll see the Property Grid Editor with expandable text entries.Find a string you recognize from the game (like a menu item or button label).

​
Step 3: Modify the Text

1

Edit the String Value

In the Property Grid:
  1. Expand the text entry you want to modify
  2. Find the language field (usually “en” for English)
  3. Click the value field to edit
  4. Change the text to something new
For example, change:
Original: "Continue"
Modified: "Continue Your Adventure"
2

Save Your Changes

Press Ctrl+S or click File > Save ProjectThe asset will show a dirty indicator (asterisk) until saved. Once saved, it appears in the Modified Assets list.
The Property Grid Editor shows the complete type information for each field. Green fields are required, white fields are optional, and grayed-out fields are read-only or transient.

​
Step 4: Export Your Mod

1

Verify Your Changes

Check the Modified Assets tab to confirm your text asset is listed. This shows everything included in your mod.
2

Export as .fbmod File

Click File > Export Mod (or click the export button in the toolbar)Choose where to save your mod:
my-first-mod.fbmod
The export process bundles all your changes into a single distributable file.
3

Verify Export Success

You should see a success message. The .fbmod file is now ready to use in FrostyModManager.

​
Step 5: Test Your Mod

1

Launch FrostyModManager

Close FrostyEditor and open FrostyModManager. Select the same game profile.
2

Import Your Mod

Click Import Mod and select your my-first-mod.fbmod file.The mod appears in the Available Mods list with your title, author, and description.
3

Enable and Apply

  1. Check the box next to your mod to enable it
  2. Click Apply Mods (or Launch Game to test immediately)
  3. FrostyModManager will apply your changes and launch the game
Some games use anti-cheat systems that may detect mods. Always use mods in single-player or offline mode only.
4

Verify In-Game

Navigate to where your modified text appears. You should see your changes reflected in the game!

​
Understanding the Modding Workflow

The workflow you just completed is the foundation of all Frosty modding: 
1. Create Project → 2. Find Assets → 3. Modify → 4. Save → 5. Export → 6. Test
.fbproject files store all your modifications in a reusable format. You can:
  • Continue working on your mod across multiple sessions
  • Make incremental changes without starting over
  • Share project files with other modders for collaboration
  • Export multiple versions of the same mod
Projects track creation/modification dates, game version, and maintain references to all modified assets.
When you save a project, Frosty stores:
  • Only the changes you made (delta format)
  • Asset references and dependencies
  • Linked assets (like texture chunks)
  • Mod metadata
  • Custom action handlers
Original game assets remain untouched. Your modifications exist only in the project file until export.
FrostyModManager applies mods at runtime by:
  1. Reading the .fbmod file
  2. Injecting modified data into the game’s memory
  3. Redirecting asset references to modded versions
  4. Managing load order for multiple mods
No game files are permanently modified. Remove the mod in ModManager and launch the game normally to play unmodded.

​
What to Try Next

Now that you understand the basics, explore more advanced modding techniques:

Modify Textures

Replace character skins, environment textures, or UI graphics

Edit Meshes

Import custom 3D models for weapons, vehicles, or characters

Change Audio

Replace sound effects or music tracks

Modify Gameplay

Edit weapon stats, character abilities, or game logic

​
Tips for Successful Modding

Begin with small, single-asset mods like this tutorial. Once comfortable with the workflow, gradually tackle more complex modifications.Simple progression:
  1. Text modifications (this tutorial)
  2. Single texture replacements
  3. Multiple textures or meshes
  4. Complex entity property changes
  5. Multi-asset gameplay mods
Get in the habit of saving frequently:
  • After each major change
  • Before testing or exporting
  • Before modifying complex assets
Enable auto-save in Tools > Options > General for automatic backups.
Add frequently accessed assets to bookmarks (Ctrl+B) to avoid repeated searching. Create multiple bookmark contexts for different aspects of your mod.
Export and test your mod frequently during development:
  • Verify changes appear as expected
  • Catch errors early before they compound
  • Ensure mod doesn’t conflict with game updates
  • Check performance impact
Use the mod description field to document:
  • What assets were changed
  • What the changes do
  • Known compatibility issues
  • Installation requirements
Future you (and your users) will appreciate the documentation.
Many assets reference other assets:
  • Textures link to chunk data for mipmaps
  • Meshes reference materials and textures
  • Entity blueprints reference multiple resource types
Frosty tracks these dependencies automatically, but understanding them helps you plan complex mods.

​
Common Beginner Issues

Solutions:
  • Use advanced filter syntax: type:MeshAsset to filter by type
  • Search for partial names: ^weapon finds assets starting with “weapon”
  • Check both base game and DLC superbundles
  • Use the Legacy Explorer for older Frostbite games
  • Look at similar existing mods to see what assets they modify
Common causes:
  1. Mod not enabled: Check FrostyModManager’s Applied Mods list
  2. Wrong game profile: Ensure mod was created for the correct game
  3. Cache issues: Clear game cache and regenerate in FrostyEditor
  4. Load order: Some mods conflict; adjust load order in ModManager
  5. Anti-cheat blocking: Some games prevent modding; check game compatibility
Troubleshooting steps:
  1. Verify .NET Framework 4.7.2+ is installed
  2. Unblock DLL files (Frosty does this automatically on first launch)
  3. Regenerate cache files (delete cache folder and restart)
  4. Ensure game is not running while using the editor
  5. Check game version matches Frosty’s supported versions
  6. Review FrostyEditor.log for specific error messages
Understanding mod file sizes:
  • Text-only mods: Very small (few KB)
  • Texture mods: Medium to large (MB range depending on resolution)
  • Mesh mods: Medium (hundreds of KB to few MB)
  • Complex mods with many assets: Large (tens of MB)
If your simple mod is unexpectedly large, you may have accidentally modified linked assets. Check the Modified Assets list for unexpected entries.

​
Next Steps

Asset Modification Guide

Deep dive into modifying textures, meshes, audio, and entities

Creating Mods

Learn advanced project management and mod development techniques

Mod Packaging

Best practices for exporting and distributing your mods

FrostyEditor Guide

Master the editor interface and advanced features

Best Practices

Follow community standards for quality and compatibility

Game-Specific Guides

Find tips and tutorials for your specific game

​
Get Help and Share Your Work

Join the Community

Connect with other modders on Discord for help, feedback, and collaboration

FAQ & Troubleshooting

Find answers to common questions and technical issues

GitHub Repository

Report bugs, request features, or contribute to Frosty development

Contributing Guide

Learn how to contribute to Frosty Toolsuite
Congratulations on creating your first mod! You now understand the core workflow used by thousands of Frosty modders. The same process scales from simple text changes to complex total conversion mods.

Build docs developers (and LLMs) love

Get started for freeTalk to us