t1k:unity:mobile:floor-probing
| Field | Value |
|---|---|
| Module | mobile |
| Version | 3.65.6 |
| Effort | medium |
| Tools | — |
Keywords: applovin floor probing, floor probing, floor-probing, FloorProbingSettings, gdk gate, mFloorProbing, release branch, revealed price, revealed-price
How to invoke
Section titled “How to invoke”/t1k:unity:mobile:floor-probing[--config-only] [--with-jenkins] [--full] [--no-jenkins]T1K — AppLovin Floor Probing (entry)
Section titled “T1K — AppLovin Floor Probing (entry)”Router AND pipeline owner for enabling AppLovin revealed-price floor probing
(com.gdk.3rd’s FloorProbingSettings / mFloorProbing) in a Unity project. It edits
nothing in ThirdPartiesConfig.asset or Jenkins itself — those stay the focused
skills’ jobs — but it DOES own the GDK gate, mode routing, and (mode 3 only) the
release-branch resolve/push steps that glue the others together.
| Mode | Flag | Steps |
|---|---|---|
| Config only | --config-only | GDK gate → config edit → commit (no push, no PR) |
| With Jenkins | --with-jenkins | Mode 1 + Jenkins symbol-only wiring (Develop+Release) |
| Full pipeline | --full | GDK gate → config → Jenkins (symbol-only) → PR+merge → release-branch resolve → Jenkins (branch) → push → report |
Invocation
Section titled “Invocation”No flag given → open an AskUserQuestion menu offering the three modes above
(rules/always-ask-on-unresolved.md) — never silently default to one. The three
flags stay available for scripted/direct invocation. --no-jenkins remains a
documented modifier on mode 3 only (steps 1–2, then 4–5, then 7–8 — both
Jenkins invocations, steps 3 and 6, are skipped: release branch still
pushed, but the symbol is NOT wired — warn this leaves the config dead on that
build). It has no meaning on modes 1–2.
More than one project targeted → smoke ONE project through the chosen mode
first, AskUserQuestion before scaling to the rest
(rules/preview-first-batch.md).
Step 1 — GDK gate (always, every mode)
Section titled “Step 1 — GDK gate (always, every mode)”mFloorProbing only exists in a migrated com.gdk.3rd. Enabling it against an
un-migrated project’s com.gdk.3rd produces config with nothing behind it — worse
than refusing, because it looks configured.
- On
origin/develop, read thePackages/com.gdk.3rdgitlink SHA (git ls-tree origin/develop <UnityProject>/Packages/com.gdk.3rd), then confirmConfigs/Ads/FloorProbingSettings.csexists at that SHA inside the submodule checkout:git -C <path-to-com.gdk.3rd> cat-file -e <sha>:Configs/Ads/FloorProbingSettings.cs(fetch the submodule remote first if the SHA isn’t local). - Present → continue to the config step for the chosen mode.
- Absent → check
origin/ai/gdk-migrate. If it exists and is0commits behindorigin/develop(git rev-list --count origin/ai/gdk-migrate..origin/develop), delegate tot1k-git-manager: open a PRai/gdk-migrate→developand merge it (merge commit — never squash, never deleteai/gdk-migrate; the project’s GDK fleet worker, if any, owns that branch across runs). Re-fetchdevelop, re-check the gitlink. Otherwise STOP and report the project as blocked — config would be dead on this GDK version.
Mode 1 — --config-only
Section titled “Mode 1 — --config-only”After the GDK gate: run t1k-unity-mobile-floor-probing-config, then commit
only — delegate to t1k-git-manager with the pathspec form
(rules/parallel-teammate-git-index-race.md), naming only the files this task
changed (the ThirdPartiesConfig.asset, nothing else), onto the branch already
checked out. No push. No PR. Then report: config diff path + values, commit
SHA, branch.
Mode 2 — --with-jenkins
Section titled “Mode 2 — --with-jenkins”Everything in Mode 1, then t1k-unity-mobile-floor-probing-jenkins invoked in its
--symbol-only mode (idempotently appends X_FLOOR_PROBING to the
Develop and Release jobs — Creative jobs are deliberately out of scope for now,
a decision, not an oversight). No release-branch resolve, no Branches-to-build
change, no PR, no push. Then report: config diff path + values, commit SHA, and
per-job Jenkins result (symbol already-present/appended, verified).
Mode 3 — --full (default full pipeline)
Section titled “Mode 3 — --full (default full pipeline)”- GDK gate → 2.
t1k-unity-mobile-floor-probing-config→ 3.t1k-unity-mobile-floor-probing-jenkinsin--symbol-onlymode (wiresX_FLOOR_PROBINGon the Develop and Release jobs, before any branch is pushed anywhere — no branch-spec change here) → 4.t1k-unity-mobile-floor-probing-pr(opens AND merges the PR) → 5. resolve the release branch (this skill) → 6.t1k-unity-mobile-floor-probing-jenkinsagain, without--symbol-only, to set the Release job(s)’ Branches-to-build to the resolved release branch (its symbol check is an exact-token idempotent append, so this second run is a no-op on the symbol — it does not double-append) → 7. push the release branch (this skill, delegated) → 8. report.
Step 5 — Resolve the release branch (after the PR merges, before the Jenkins branch wiring)
Section titled “Step 5 — Resolve the release branch (after the PR merges, before the Jenkins branch wiring)”Read-only in the main session. Branch naming varies per repo — check both
release-x.y.z and */release-* patterns against git ls-remote --heads origin.
- No release branch found at all →
AskUserQuestion— never invent a starting version. - Newest one (by version, tie-broken by committer date) last changed > 7 days
ago → plan a NEW branch from
origin/develop; next version = patch +1, with the fleet’s observed rollover (1.1.9→1.2.0,1.0.9→1.1.0). - Changed ≤ 7 days ago → plan merging
developinto that EXISTING release branch, no new branch. - Hand the resolved plan to
t1k-git-managerto PREPARE (create the branch, or merge locally) but not push yet — the push is step 7, after the second Jenkins call.
Step 7 — Push the release branch last
Section titled “Step 7 — Push the release branch last”Only after step 6 confirms the Release job(s)’ branch spec already points at the
resolved release branch. Delegate to t1k-git-manager: push the step-5
branch/merge to origin/<release-branch>. This push is what starts the Jenkins
Release build via GitHub’s push webhook — do not trigger the Release job through
the Jenkins API instead; that intentionally differs from t1k-jenkins-build’s
never-auto-trigger-Release default, because here the build is started by the branch
push the user asked for, not by this skill calling Jenkins.
Step 8 — Report
Section titled “Step 8 — Report”One consolidated summary per project: config diff path + values, PR URL (merged),
release branch + SHA, Jenkins before/after per job (repo, branch, symbols
added/removed, push-trigger presence), and whether a build actually got queued
after the push (re-read the job’s last-build/queue state — safe to use
t1k-jenkins-build’s fact-collection for this, since it never auto-triggers a
Release job).
Hard rules
Section titled “Hard rules”- The
apiKeyis a client-shipped key, committed in plain text — accepted by the user, not a leak to flag. Seet1k-unity-mobile-floor-probing-config§ Hard rules for the full rationale; do not applyrules/security.md’s secret-handling steps to it. - Config with
enabled: 1compiles to nothing unlessX_FLOOR_PROBINGis wired — and it must be wired before ANY push in the pipeline, including the develop merge, not just before the release push: a project whose Develop job has a GitHub push trigger would otherwise start a symbol-less develop build the moment step 4’s PR merges. That is why mode 3 wires the symbol first, in its own--symbol-onlystep (3), before the PR/merge (4) — confirmed necessary byUnityAndroid/DumplingMakeOver-Releasebuild #17, whosePARAM_UNITY_SCRIPTING_DEFINE_SYMBOLSwas read back lackingX_FLOOR_PROBINGbecause the symbol had been wired after that build’s triggering push. Mode 3’s second Jenkins call (6) only adds the release-branch spec; its symbol check is idempotent and a no-op by then. This is also why mode 2 exists at all for projects that want the symbol wired without a release. - Any git mutation (GDK-gate PR/merge, mode 1/2 commit, mode 3’s release-branch
prepare/push) is delegated to
t1k-git-manager(rules/orchestration-rules.md), never rungit/ghdirectly in the main session. - Never re-implement the config edit, the PR mechanics, or the Jenkins mutation here — this skill owns only the GDK gate, mode routing, and (mode 3 only) the release-branch glue; the three sub-skills own their own domains.
Routing + the GDK gate + (mode 3 only) release-branch resolve/push glue. Not
itself: asset edits (t1k-unity-mobile-floor-probing-config), PR mechanics
(t1k-unity-mobile-floor-probing-pr), or Jenkins define-symbol/branch mutation
(t1k-unity-mobile-floor-probing-jenkins).
Executed by
Section titled “Executed by”Main session (inline) for the GDK-gate check and release-branch resolution
(read-only judgment); t1k-git-manager for every git/PR/commit mutation across all
three modes.
Related
Section titled “Related”t1k-unity-mobile-floor-probing-configt1k-unity-mobile-floor-probing-prt1k-unity-mobile-floor-probing-jenkinst1k-unity-base-gdk-migrate— ownsai/gdk-migrate; the project’s GDK fleet worker, if any, owns the fleet schedule this gate’s merge feeds intot1k-jenkins-build— read-only build-state facts used in mode 3’s reportt1k-unity-mobile-3rd-integrate— the siblingcom.gdk.3rdconfig skill this domain sits next to