t1k:unity:mobile:integration-capture
| Field | Value |
|---|---|
| Module | mobile |
| Version | 3.65.6 |
| Effort | medium |
| Tools | — |
Keywords: adjust token check, applovin integration manager screenshot, check integration sheet, integration capture, integration info, integration setup screenshot, max ad unit check, network adapters screenshot, sdk audit
How to invoke
Section titled “How to invoke”/t1k:unity:mobile:integration-capture<sheet.xlsx> <package-name> [--platform Android|iOS|both] [--post <thread-id> --tag <user-id>]Integration Capture
Section titled “Integration Capture”Proves what a Unity game has wired: a read-only comparison of the ops sheet with the SDK config assets, plus screenshots
a reader can check for themselves. It never changes an ID. To fix what it finds, use t1k-unity-mobile-3rd-integrate.
Decision Tree
Section titled “Decision Tree”| Intent | Path |
|---|---|
| “Does the project match the sheet?” | Step 1 only |
| “Screenshot the integration setup” | Steps 1 to 4 |
| “Also show the network adapters” | Step 3 |
| “Send it to Discord” | Step 5 |
Workflow
Section titled “Workflow”1. Compare the sheet with the project
Section titled “1. Compare the sheet with the project”python3 -I scripts/check_integration.py --xlsx <sheet.xlsx> --package <package> --platform both --project <unity-root>Prints status | platform | field | sheet | project | where, the strikethrough sweep result and a count. Exit 0 means
every field is MATCH, 1 means something else needs reading, 2 means a usage error or no single row for that package.
| Status | Meaning |
|---|---|
MATCH | Same value in the sheet and the asset |
MISMATCH / MISSING / NO_ASSET | Report it. Do not edit from this skill |
STRUCK | Struck through in the sheet, meaning deprecated. Never treated as the expected value |
SHEET_EMPTY | The sheet has no value, so the field is unverified, not good |
NOT_IN_PROJECT | A studio-wide key on the keys tab, such as an Ad Review key, is absent from the checked assets. Check the installed plugin has a field for it before calling it a defect |
Keep -I: the sheet is a downloaded file. Also compare the sheet’s game name with
productName in ProjectSettings.asset by eye, and report a difference rather than resolving it.
2. Capture the Inspector pages
Section titled “2. Capture the Inspector pages”A rendered Inspector needs a real window, so this is the stated rendering need for leaving headless
(rules/unity-headless-by-default.md). First run t1k unity instance current, then confirm with pgrep.
| Editor state | Do |
|---|---|
| CLI reaches an open Editor | Use t1k unity eval with EditorWindow and ScreenCapture per t1k-unity-editor-cli. Do not launch a second Editor |
Open, but the CLI exits 14 (t1k unity doctor reports flatpak-launched-editor) | scripts/capture-pages.sh |
| None open | scripts/capture-pages.sh |
bash scripts/capture-pages.sh <unity-root> <out-dir>It refuses with exit 75 unless available memory is at least 8 GB and swap is at most 60%. Never override that with the open Editor running. One run with 6.4 GB available and swap at 73% filled swap, which is where an OOM daemon such as systemd-oomd kills the largest swap user, usually the open Editor. On a refusal, ask the user to free memory, or report the Step 1 table and adapter list as text.
The script reflink-copies the project, skipping Temp, Logs and .git, and deletes the copy on exit. The harness goes
only into the copy. A window appears on the user’s display for a few minutes and closes itself, so say so first.
Require done pages=N with N of at least 1 in <out-dir>/unity.log; a silent blank run also exits 0.
3. Capture the AppLovin network adapters
Section titled “3. Capture the AppLovin network adapters”The list is the AppLovin Integration Manager window, which needs an open Editor. Have the user open AppLovin > Integration Manager and scroll to the networks, then photograph only that window:
W=$(wmctrl -l | grep -i 'integration manager' | awk '{print $1}' | head -1); [ -n "$W" ] && import -window "$W" <out-dir>/integration_manager.pngDo not drive the user’s Editor with synthetic input. Focusing it runs auto-refresh, which recompiles pending edits and
can reload the domain under another session working in the same project. xdotool key ctrl+shift+i also failed to open
the window in the one run that tried it, and the scene showed unsaved changes afterwards.
Cross-check the installed rows against com.applovin.* in Packages/manifest.json. No X11 window, or wmctrl not
installed: ask the user for a screenshot. Brand-to-package names: t1k-unity-mobile-3rd-integrate/references/max-mediation-adapters.md.
4. Mask, crop and verify
Section titled “4. Mask, crop and verify”Read every page natively, not through the vision router role: unmasked pages hold keys that must not reach a third-party
provider. Then write a spec (references/panel-spec.md) and run python3 scripts/compose_panels.py <spec.json> <out.png>.
| Value | Treatment |
|---|---|
| SDK keys not in the sheet (ByteBrew, Floor Probing API key) | Fully masked |
| MAX SDK key, Meta client token | Keep the first and last few characters, so a reader can compare them with the sheet |
| Adjust tokens, ad unit ids, app ids, package name | Readable: they are what is being checked |
Masks are pixel coordinates from the current run’s pages. Read the composed image afterwards and confirm each mask covers its value; a mask that drifted by one row leaks a key, and a posted image cannot be recalled.
5. Post
Section titled “5. Post”Use the thread and tag the user names. With no thread named, read discord.threads in .claude/t1k-project-links.json.
Confirm a named channel with channels_get before posting: a channel can be named after the game’s title, not its repo.
Upload with attachments_prepare_upload, PUT the bytes, then messages_send, laid out per t1k-discord-message and
worded per t1k-human-writing. Read the message back and confirm every attachment is present. Report the differences from
Step 1 in the post, and do not invent an ask for the person tagged.
6. Clean up
Section titled “6. Clean up”Unmasked pages stay in <out-dir>. Delete them once the post is verified, or tell the user where they are.
Executed by
Section titled “Executed by”| Step | Agent |
|---|---|
Run check_integration.py and report its table | t1k-fact-fetcher |
| Capture, mask decisions and posting | Main session: they need a user-owned window, a judgment on what may be published, and the user’s go-ahead |
Related
Section titled “Related”t1k-unity-mobile-3rd-integrate (fixes the differences found here) · t1k-unity-editor-headless-capture (the launcher
and Inspector harness this drives) · t1k-discord-message · t1k-unity-editor-cli