Tool [Tool] LibTool iOS v1.1.10 – IL2CPP Explorer, Runtime Editor, Lua, AI, ESP & Dumper

HaoDam · August 19

LibTool iOS
Version: 1.1.10
Developer: HaoDam

Hello everyone, I am HaoDam.

Some time ago, I shared a Unity game modding utility called LibTool. The project was originally developed on Android. I have now rebuilt and expanded it for iOS, and today I would like to introduce the new version and show you how its main features work.

LibTool is not a mod menu made for one game. It is a runtime toolkit for exploring and testing Unity IL2CPP games directly inside the app.

Video demo

Spoiler

Soul Knight Prequel FREE MOD – LibTool iOS (+4 Tools)
https://www.youtube.com/watch?v=UgaQXhLrv1g

LibTool iOS – Demo Tool AI Easy MOD
https://www.youtube.com/watch?v=PMwOCjOJv_A

Requirements

- iOS 13 or newer
- arm64 device/app
- Unity game using the IL2CPP backend
- Jailbroken device or a compatible decrypted-IPA tweak injection method
- For a jailed setup, inject the LibTool package into the IPA instead of using a normal jailbreak installation
- Internet connection is required only for the AI tab

What does it do?

Tools

- Browse all loaded IL2CPP images and classes
- Assembly-CSharp.dll is selected by default
- Open multiple class tabs with the + button
- Search by class, method or field
- View class metadata, parent classes, interfaces and generic information
- View static fields and methods
- Find live objects and inspect their values
- Read and write supported fields/properties
- Invoke methods with custom parameters
- Patch, redirect and trace methods at runtime

Filter examples

Quote

Wallet
Search for classes containing Wallet.

:GetCoins
Search for any class containing a GetCoins method.

Wallet:GetCoins
Search for a Wallet class that also contains GetCoins.

Wallet#coins
Search for a Wallet class containing a coins field.

^WalletModel$
Match the exact class name WalletModel.

Example: finding the real currency class

Quote

If the game displays 10,000 coins:

1. Search Wallet, Currency, Coin or Balance.
2. Open WalletModel and use Find Objects.
3. Inspect the live fields/properties.
4. Call GetCoins() if the method exists.
5. Compare the result with the 10,000 shown by the game.

If WalletModel.GetCoins() returns 10,000 while CurrencyView only contains text formatting, WalletModel is probably the real data owner. If the values do not match, continue searching instead of patching the first result.

Inspector

- Displays Field/Property, Value and Type columns
- Shows inherited fields
- Supports static and live instance objects
- Boolean values use a True/False selector
- Enums display their named constants
- Numeric and string values can be edited directly
- Object references can be opened and inspected deeper
- Back and Root buttons navigate the object graph
- Breadcrumb shows the current path
- Properties option enables managed property getters/setters
- Always Update refreshes values that change while the game runs
- Arrays can be opened by index
- List and Dictionary backing data can also be inspected
- Field metadata displays type, offset, reflection state and attributes
- ACTk/Obscured values receive safer handling instead of blindly editing hidden integrity fields

Example: inspecting inventory

1. Find a live PlayerInventory object.
2. Open the items/List field.
3. Open its _items array.
4. Select an element such as [0].
5. Inspect ItemData fields such as id, amount or rarity.

Caller

- Calls static or instance methods directly
- Instance methods require a valid this object
- Supports Boolean, enum, integer, float, double and string inputs
- Supports object and supported value-type parameters
- Supports ref/out parameters and displays their returned values
- Can run a method normally or on the main thread
- Call Count repeats a verified method several times
- Call Results displays return values, managed objects and exceptions

Example: calling a setter

If metadata confirms:

int GetCoins()
void SetCoins(int value)

1. Select the same live WalletModel object for both methods.
2. Call GetCoins() and record the BEFORE value.
3. Call SetCoins(999999).
4. Call GetCoins() again.
5. Verify the game UI.

A successful call is not enough. The AFTER value and the real UI should also change.

Patcher

- Automatically reads the method return type
- Supports Boolean and integer return patches
- Supports float, string, enum and BigInteger where compatible
- Supports Vector2, Vector3, Vector4 and Quaternion returns
- Void methods can use Patch NOP
- Manual Input accepts raw arm64 patch bytes for advanced users
- Redirect sends one compatible method to another method
- Active patches can be enabled, disabled or restored
- Generated patch bytes can be copied when available

Example: Boolean patch

bool CanAfford(ItemData item)

After confirming this is the real local purchase check, open Patcher, select True and press Patch. Test the real purchase or call the method again. Press Restore when the test is complete.

Do not apply a Boolean patch to an int or void method. The patch type must match the real return type.

Example: NOP patch

void ConsumeEnergy()

Because this method returns void, it cannot return true or 999. Patch NOP prevents its body from running. Be careful: a void method may also perform cleanup or callbacks, so NOP can break other game logic.

Tracer

- Trace shows when a method executes
- Trace + Return also captures supported return information
- Displays hit count and calls per second
- Can display arguments and return values
- Pause freezes the current trace display
- Clear removes trace history
- Auto-Stop can stop extremely hot methods at a CPS limit

Example: finding the spending method

1. Search for Spend, Purchase, Buy or Consume methods.
2. Trace one candidate.
3. Spend 500 coins in the game.
4. Check which method fired and whether 500 appeared as an argument.
5. Stop tracing after you have enough evidence.

Avoid Trace All unless necessary. Tracing too many hot methods can reduce performance or crash the game.

Scripting

- Create, open, edit and save Lua files
- Files are stored in Documents/libTool-files/script
- Multiple scripts can be opened in separate tabs
- Paste from clipboard and Clear are available
- Check Syntax reports the exact script line
- Run executes a one-shot script
- Scripts defining OnDraw() automatically use Run UI
- Restart UI reloads the current menu code
- Stop UI closes the persistent menu
- Runtime errors, stack traces and print logs are shown below the editor

Simple Lua example ( Subways Surfers )

local cls = Class.fromName("Game.WalletModel")
if not cls then
  print("WalletModel not found")
  return
end

local wallet = cls:findObjects()[1]
if not wallet then
  print("No live WalletModel")
  return
end

local ok, value = pcall(function()
  return wallet:GetCoins()
end)

print("GetCoins ok=", ok, "value=", value)

Lua rules

- Static method: cls.StaticMethod()
- Instance method: obj:Method()
- Property: obj.Property, not obj:Property()
- Use collectionItems(...) before iterating a managed List/Dictionary/Array
- Always check class and object values for nil
- Use pcall for experimental actions
- Print BEFORE, AFTER and DELTA when modifying a value

Simple UI menu example

local state = { amount = 1000, status = "Ready" }

function OnDraw()
  ImGui.SetNextWindowSize(380, 260)
  local visible = ImGui.Begin("Wallet Menu")

  if visible then
    local changed, amount = ImGui.InputInt("Amount", state.amount, 100, 1000)
    if changed then state.amount = amount end

    if ImGui.Button("Apply") then
      state.status = "Requested: " .. tostring(state.amount)
    end

    ImGui.SeparatorText("Status")
    ImGui.TextWrapped(state.status)
  end

  ImGui.End()
end

The Apply button above is only a UI example. Replace it with a class/method that you already verified in Tools.

AI

- AI can inspect the actual runtime instead of only giving generic answers
- Supports OpenCode Zen Free dynamic models
- Supports OpenAI account login
- Supports GitHub Copilot
- Supports custom OpenAI-compatible providers
- Keeps separate chat sessions for different games
- Shows plan and analysis progress
- Tracks context/token usage and supports conversation compaction
- Can inspect classes, methods, fields, objects and collections
- Can compare candidate classes
- Can inspect nested objects
- Can call verified methods or write fields
- Can patch and restore methods
- Can create, validate and save Lua scripts
- Saved scripts automatically open in Scripting

AI prompt example

Quote

The game currently displays 10,000 coins. Find the live class that owns this exact value. Search Wallet/Currency classes and related getters. Compare live objects and the UI value. Do not modify anything until the source of truth and method signature are confirmed.

After the class is confirmed:

WalletModel.GetCoins() matches the UI and SetCoins(int) is confirmed on the same object. Create a compact Lua menu with one InputInt, one Apply button, nil checks, pcall and a status message. Save it and open it in Scripting.

AI can make mistakes. Always verify the result with Tools, Caller, Inspector or the game UI.

ESP

- GameObjects tab lists live Unity GameObjects
- Filter by object ID or name
- hasComponent:Type filters objects by Component
- Components tab groups Component types and shows their object count
- A Component can be selected as Main Component
- Additional Sub Components reduce false targets
- Camera selector supports the default or another live camera
- Name filter supports Equal or Contain
- Overlay options include Ray line, Box, Distance and Object name
- Draw starts the overlay and Stop ends it

Example: Enemy ESP

1. Open Components and search EnemyController.
2. Set EnemyController as Main Component.
3. If friendly NPCs also match, add EnemyHealth as a Sub Component.
4. Open Draw and start with Default Main Camera.
5. Enable Box, Distance and Object name.
6. Press Draw.

Use a specific Component with a small object count. Transform may have thousands of objects, while EnemyController may have only 20 targets.

Dumper

- Dumps IL2CPP metadata from the running game
- Shows current progress/class while dumping
- Creates a C#-style .cs file
- Output name contains the package and game version where available
- Copy path copies the final location

Example

1. Wait until the game is fully loaded.
2. Open Dumper.
3. Press DUMP once.
4. Wait for Done.
5. Copy the output path.
6. Search the file for WalletModel, GetCoins or another class discovered in Tools.

The dump is not the original game source and does not show which object is currently alive. Use Dumper for offline reference and Tools for runtime verification.

Settings

- Text/UI size from 25% to 200%
- Maximum Content, Compact and Comfortable density
- Dark, Light and Classic styles
- Menu FPS selection up to the device refresh rate
- Scroll speed adjustment
- Show or hide Scripting, AI and ESP tabs
- Device, iOS, screen, bundle, game version and Unity information
- Reset display/performance or optional tabs

Download

Spoiler

CLICK DOWNLOAD LIBTOOL 1.1.10

Important

- Use LibTool only on software and devices you own or are authorized to test
- Back up important local game data
- A wrong field, object, method signature or patch can crash the app
- Online games may validate values on the server or detect modifications
- Runtime patches normally disappear after restarting the app
- Do not resell or redistribute modified LibTool builds without permission

Credits

Developer: HaoDam / F4CK CHEAT
Thanks to the developers and communities behind Dear ImGui, Lua, Dobby, IL2CPP research resources and the other open-source components used in this project.
Official link
YouTube: https://www.youtube.com/@F4CKCHEAT
Telegram: https://t.me/F4CKCHEATING

HaoDam · August 19

Additional note for anyone who wants to explore more LibTool examples

You can also learn from Android LibTool videos because the main Unity IL2CPP workflow is almost the same: browse images and classes, search for fields or methods, inspect live objects, test a function, and verify the result inside the game. The installation and injection process is different on Android, so please do not copy those setup steps directly to iOS.

If you use the AI feature inside LibTool, I recommend Provider: OpenCode Zen.

My personal favorite is DeepSeek with Thinking set to Max. It can analyze a wider class structure, compare related Wallet, Currency, Inventory or Manager classes, and help you reach a useful mod or Lua script much faster. The exact DeepSeek model name may change as the OpenCode Zen catalog is updated, so choose the currently available DeepSeek model and select Max, or the highest Thinking level offered.

Please try it and share your experience. Tell me which game and version you tested, which model you used, what the AI found correctly or incorrectly, and whether the generated patch or script worked. Your feedback will help me improve LibTool in future updates.

VaaR · Tuesday at 12:07 PM

Absolute goat I love this tool. Never tried deepseek inside the tool, but from my own tests I find it that it just goes around the subject in modding instead of actually doing it, it has the right info and direction but couldn’t actually pull it off, the other models I used actually did things all the way.
Regarding the tool, I always prefer the ai to directly patch things because the menu it creates always lags the game when something is enabled

Updated Tuesday at 12:19 PM by VaaR