GTracker: Create Unity game integrations without writing code
Project: GTracker on GitHub
Example integration: CelSector 1.1.1 EDI Integration
TL;DR
Using GTracker, I was able to fully integrate CelSector with more than 180 scripts in a single afternoon, without touching a single line of code.
GTracker handles the repetitive parts of creating an integration: capturing scenes, using Unity telemetry to isolate animation cycles, generating the Unity/BepInEx mod, mapping animations to scripts, and exporting the EDI Gallery.
It is currently in a very early alpha state, and I cannot promise that I will be able to provide support. However, its Unity Animator workflow already works extremely well for compatible games and allowed me to integrate an entire game surprisingly quickly.
If people actually like this project and it’s helpful I can make a little tutorial/scripting example video.
Why I Made This
I’ve lurked on EroScripts for a while and have amassed a collection of more than 65 integrated games.
Properly integrated games are a mindblowing experience. Having a toy react directly to what is happening in the game adds an incredible extra layer of immersion. Unfortunately, making a complete integration has traditionally required a lot of time and technical knowledge.
Depending on the game and workflow, you might have to:
- Record or collect footage for every scene.
- Stitch everything into one giant reference video.
- Precisely trim every animation loop by hand.
- Keep scene names, timings, and scripts organized manually.
- Investigate which Unity animation systems the game uses.
- Write or update BepInEx plugins for different Unity frameworks.
- Manually connect runtime animation names to scripts.
- Rebuild everything whenever mappings change.
That amount of work makes full integrations difficult to produce, especially for people who are not experienced programmers or mod developers.
GTracker is my attempt to make that process much more approachable.
What Is GTracker?
GTracker, currently branded as EDI Integration Studio, is a Windows authoring tool for creating game integrations for Easy Device Integration.
For a well-supported Unity game, the basic workflow is:
- Select the game’s executable.
- Let GTracker analyze its Unity runtime.
- Generate and install the BepInEx integration plugin.
- Start the game and enable runtime discovery.
- Play an animation for a couple of loops.
- Select the detected Unity Animator event and click Capture cycle.
- Draw the corresponding funscript curve.
- Click Save + lock and continue to the next scene.
- Export the finished EDI Gallery.
The generated plugin reports animation names, object paths, loop timing, and other runtime information back to GTracker. For timed animations, GTracker can calculate and capture the exact animation cycle from its rolling screen buffer.
This means you generally do not need to:
- Create one enormous video containing every scene.
- Search through that video later.
- manually trim every animation to exact loop boundaries.
- Write a custom plugin from scratch.
- Write code to map every detected animation.
- Manually maintain framework-specific Unity observer code.
You can capture, script, name, map, and save each scene while you are already looking at it in the game.
Current Unity Support
The generated integration can currently observe several common Unity runtime systems, including:
- Animator/Mecanim
- Legacy Animation
- PlayableDirector/Timeline
- Mono Spine
- PlayMaker state changes
- Unity scene changes
The timed Capture cycle workflow currently works best with Animator/Mecanim and other supported systems that expose reliable playback timing.
Not every Unity game will work automatically. Games can use custom state machines, procedural animation, obfuscated code, native animation systems, or unusual frameworks. Some games may still require manual mappings or a game-specific patch.
How Well Does It Work?
My first major test was CelSector.
With GTracker, I created a full integration containing more than 180 scripts in one afternoon. I did not have to write or edit a single line of code.
The workflow was essentially:
- Open a scene in the game.
- Let the animation loop.
- Select the newest detected Animator event.
- Capture the exact cycle.
- Draw the motion.
- Save and move to the next scene.
The generated plugin then used the saved mappings to trigger the correct EDI scripts during gameplay.
My scripting may not be amazing since I am still new to it, but simply having the toy triggered automatically by the game adds an incredible amount of immersion.
You can find that integration here:
Alpha Warning
GTracker is in a super alpha state.
Please expect rough edges, incomplete workflows, and compatibility problems. It has primarily been tested through my own integration work, not across every Unity version or game configuration.
Important limitations:
- Windows x64 only.
- Primarily intended for Unity games.
- Compatible games still need to expose detectable runtime events.
- Screen capture requires a visible windowed or borderless game.
- Some games will require manual mapping or custom code.
- Project and captured clip files may contain local paths or captured screen pixels.
- There is currently no polished installer or stable release process.
- I am not sure how much user support I will be able to provide.
Please back up your projects and treat the current version as an experimental authoring tool rather than finished software.
Why Share It Now?
Even in its current state, GTracker made a previously intimidating full-game integration achievable in an afternoon.
I am hoping it can eventually make integration authoring accessible to people who are comfortable drawing scripts but are not comfortable reverse-engineering Unity games or writing BepInEx plugins.
Properly integrated games are incredible, and we need more of them. I think we can all agree that the more people who can create and share full integrations, the better.
Links
- GTracker source and documentation
- Installation and prerequisites
- Authoring scenes
- Unity mod workflow
- CelSector integration
Feedback and testing reports are welcome, but please keep the alpha status and limited support availability in mind.
