Document community products
Co-Authored-By: Claude Opus 5.5 <[email protected]>
This commit is contained in:
1 parent
887e8a2364
commit
0e5ecf54ae
2 files changed
+31
No files matched your search
@@ -24,3 +24,11 @@ in the `t5de` repository (git.t5de.dev/t5de/t5de, usually checked out beside thi
|
||||
- t5de's `tools/drive.py` starts the built client, takes screenshots, clicks, and sends `imvu:` commands
|
||||
(`showMode?mode=shop`, ...), so the proxy can be tested in the real client without a person; the test
|
||||
account's saved login signs in by itself. The log is `%TEMP%\t5de-proxy.log`.
|
||||
- Community products (README): `internal/products`. What the client needs was worked out from captures
|
||||
(t5de-hub's `docs/imq-rooms.md` and this repo's README): a product's CFL holds `index.xml` (deriving from a
|
||||
parent with `__DATAIMPORT product://<id>/index.xml`), materials and textures; `_contents.json` would make the
|
||||
client fetch files separately, so packs don't use it. Outfit saves happen only from some modes (Dress Up, not
|
||||
rooms). Test packs (never committed: they're built on IMVU products' templates) live outside the repo; tests use
|
||||
synthetic files.
|
||||
- Debugging: `-trace` (or `T5DE_PROXY_TRACE=1`) logs full URLs and IMQ frame types; changes to community products
|
||||
are logged as `products: ...`.
|
||||
Reference in new issue
Block a user