Skip to content

t1k:unity:mobile:floor-probing-config

FieldValue
Modulemobile
Version3.65.6
Effortmedium
Tools—

Keywords: applicationIdentifier, applovin-floor-worker, batch key mapping, floor probing, floor-probing, FloorProbingSettings, gridBaseUrl, mFloorProbing, revealed price, ThirdPartiesConfig

/t1k:unity:mobile:floor-probing-config
[--project <path>]

Edit the mFloorProbing: block of ThirdPartiesConfig.asset — the ONLY thing this skill touches.

ItemPath
Config asset<UnityProject>/Assets/Resources/GameConfigs/ThirdPartiesConfig.asset — <UnityProject> is a subfolder of the repo, resolve it generically (do not assume a fixed name)
Field schema + defaultsPackages/com.gdk.3rd/Configs/Ads/FloorProbingSettings.cs
Parent settings (declaration order)Packages/com.gdk.3rd/Configs/Ads/AdSettings.cs — mFloorProbing is declared directly after mCloudX
Runtime gate (dead without it)#if X_FLOOR_PROBING in Packages/com.gdk.3rd/Ads/Applovin/AppLovinAdsWrapper.cs; FloorProbing/CachedGridFloorLookup.cs is gated APPLOVIN && X_FLOOR_PROBING
  1. Resolve the Unity project directory generically — the repo root is not the Unity project root; find the folder containing Assets/ and ProjectSettings/ (there may be more than one in a fleet-style repo — confirm which one the user means before editing).
  2. Pre-flight: check <UnityProject>/Temp/UnityLockfile. If it exists, the Editor owns this .asset in memory and can overwrite your edit on its next domain reload / asset save — warn the user before editing (same gotcha t1k-unity-mobile-3rd-integrate documents).
  3. Read the file as bytes first to detect its line-ending style (CRLF vs LF) — preserve it verbatim on write. Unity .asset YAML is sensitive to whole-file reformatting.
  4. Locate the mFloorProbing: key.
    • Present → edit only its child lines in place.
    • Absent → the field may simply not have been serialized yet (Unity only writes a new schema field to a .asset the next time the object is saved, not retroactively) — this is NOT an error. Insert a full block at the same indent as its siblings (enableCloudX: / mCloudX: / enableByteBrew:), spliced in directly after the mCloudX: block ends (anchor on indent depth, not on a specific sibling name — the schema’s sibling ordering can differ by project vintage).
  5. Resolve gridBaseUrl and apiKey — the method depends on how the caller was invoked:
    • No key list supplied (single project) — ask BOTH, batched in one AskUserQuestion call, every time, regardless of whether the block already had values: gridBaseUrl (you may offer https://applovin-floor-worker.the1studio.org/ as ONE selectable option, never a silent default), apiKey (no default offered — never guess, reuse a value from another project’s asset, or reuse a value seen elsewhere this session).
    • A key list was supplied (<store name> - <fk_key> - <package id> lines, one per project — the fleet/batch case) — resolve apiKey by MATCHING, never by asking:
      • Read this project’s Android/iPhone applicationIdentifier from <UnityProject>/ProjectSettings/ProjectSettings.asset (may be an LFS pointer — see Hard rules).
      • Match against the list’s <package id> field — never <store name>, which differs from the project’s productName and is not a reliable key.
      • No match → skip this project, record “no matching key for <applicationIdentifier>” in the report; never guess or borrow a key from another project.
      • gridBaseUrl is still confirmed once per BATCH via AskUserQuestion (same studio-worker option as above) — it does not vary per project.
  6. Set (or insert with) enabled: 1. Leave refreshIntervalMinutes: 60, fetchTimeoutSeconds: 10, probeInterstitial: 1, probeRewarded: 1 at the schema defaults unless the user states otherwise — those are not part of what this skill asks about.
  7. Write back preserving indentation and the detected line-ending style. Field order inside the block, when inserting fresh, must match the schema declaration order: enabled, gridBaseUrl, apiKey, refreshIntervalMinutes, fetchTimeoutSeconds, probeInterstitial, probeRewarded.
  8. Verify: git diff touches ONLY ThirdPartiesConfig.asset, and the hunk is scoped to the mFloorProbing block (plus, for a fresh insert, the single preceding line where it was spliced in). Any wider diff means a YAML re-serialize touched unrelated content — discard and redo by hand-editing lines, not by round-tripping through a generic YAML library.
  9. Report the exact block written (values included — see Hard rules on why the API key is not redacted) and hand off to t1k-unity-mobile-floor-probing-pr / -jenkins if the caller asked for those steps.

Example block (reference shape, not literal values to copy)

Section titled “Example block (reference shape, not literal values to copy)”
mFloorProbing:
enabled: 1
gridBaseUrl: https://applovin-floor-worker.the1studio.org/
apiKey: fk_...
refreshIntervalMinutes: 60
fetchTimeoutSeconds: 10
probeInterstitial: 1
probeRewarded: 1
  • The apiKey is a client-shipped key and is expected to be committed in plain text — FloorProbingSettings.cs’s own doc comment states it plainly: it is “not a secret in the sense a server-side credential is one… it ships inside the app binary and is extractable by anyone who wants it.” It buys ad-unit-ID obscurity, key revocability on leak, and scanner-vs-real-client telemetry — nothing more. Do NOT treat it as a .env-class secret, do not refuse to write it into a committed .asset, and do not route it through rules/security.md’s env-var handling. This is a deliberate, user-accepted design choice of the underlying package, not an oversight.
  • Absence of mFloorProbing: in an older asset is normal, not corruption — insert with schema defaults rather than erroring or asking the user to “fix their asset first.”
  • The Editor may hold the asset open in memory (Temp/UnityLockfile) — an edit made while it is open can be silently clobbered by the Editor’s own next save. Check first.
  • Preserve exact indentation and line endings; a generic YAML parse/re-serialize reformats the WHOLE file and turns a 7-line diff into a file-wide one.
  • Only ever edit the mFloorProbing block. Never touch sibling ad-network blocks even if you notice something odd in them while scanning — that is t1k-unity-mobile-3rd-integrate’s scope.
  • ProjectSettings.asset and ThirdPartiesConfig.asset may both be Git LFS pointers on disk, not the real YAML — a pointer file starts with version https://git-lfs.github.com/spec/v1. Detect this before parsing either file; read the SMUDGED content instead (the working-tree file after git lfs pull/smudge, or git show <ref>:<path> | git lfs smudge) — editing the raw pointer text is not editing the asset.
  • Insert-when-absent must not leave a blank line before the new block, and must not drop the file’s trailing newline when mCloudX: is the LAST block in the file — both were observed defects in a prior run. Splice directly after the last line of the mCloudX: block with no blank line, and preserve whichever trailing-newline convention the file already had at that point.
  • A migrated GDK may already serialize mFloorProbing: with enabled: 0 — “present” does not mean “already configured”; still run step 5 above and set enabled: 1.

Main session (inline). The edit is a small, scoped, single-file YAML-block patch gated by one AskUserQuestion call — well under the ~20-line patch exception in delegate-to-preserve-context.md, and no sub-agent fan-out is warranted for a single asset edit.

  • t1k-unity-mobile-floor-probing — entry/router that chains this skill with the PR and Jenkins steps
  • t1k-unity-mobile-floor-probing-pr — commits and opens a PR for the diff this skill produces
  • t1k-unity-mobile-floor-probing-jenkins — wires X_FLOOR_PROBING so the config is not dead on the build that runs it
  • t1k-unity-mobile-3rd-integrate — sibling com.gdk.3rd config skill (same ThirdPartiesConfig.asset, different blocks); consult its Temp/UnityLockfile handling