@xsolla/backpack-js 1.9.0 → 1.9.2

package/README.md

@@ -36,11 +36,11 @@ Send (web3 transfer) is off by default, but an embed may turn it on with `enable
 
 Transfuse (minting an off-chain catalogue item onto the chain) is off by default too, and turns on with `enableTransfuse` / `enable-transfuse`. It needs no credentials at all — the backend performs the mint — but it is irreversible and costs gas, and the action only appears on items the items API marks `is_mintable`, so turning it on where no project is wired for minting simply shows nothing.
 
-Salvage (destroying an item) is the other way round: it is **on** by default, and an embed turns it off with `enableSalvage` / `enable-salvage`. It signs nothing and costs nothing, the backend refuses the item types it will not destroy, and the drag onto the target is the confirmation, so there is no button a user can hit by accident. The merchant configuration can withhold the seat as well, and wins over the attribute.
+Salvage (destroying an item, labelled "Remove" on the wheel) is the other way round: it is **on** by default, and an embed turns it off with `enableSalvage` / `enable-salvage`. It signs nothing and costs nothing, the backend refuses the item types it will not destroy, XLA and XLA-NT (the tokens gas is paid in) never get the seat, and the drag onto the target is the confirmation, so there is no button a user can hit by accident. The merchant configuration can withhold the seat as well, and wins over the attribute.
 
 Set `openItem` / `open-item` to open that inventory item as the element loads, with its action wheel already up. Backpack fetches the item on its own, so it does not have to be on the first page of the grid. A missing row, a failed fetch, or a hidden SKU leaves the grid as it is. Clearing the attribute, or the player closing the wheel, returns to the catalog. Reloading the embed does not open the same id again.
 
-The action wheel shows the item's 2D artwork in the middle. An embed can put the 3D model there instead with `enableWheel3dModel` / `enable-wheel-3d-model`, which is off by default: the viewer is a WebGL canvas that keeps rendering for as long as the wheel is open, and it takes frames the wheel's own spin and drag need. Item details is unaffected either way and always shows the model.
+The action wheel shows the item's 2D artwork in the middle. An embed can put the 3D model there instead with `enableWheel3dModel` / `enable-wheel-3d-model`, which is off by default: the viewer is a WebGL canvas that keeps rendering for as long as the wheel is open, and it takes frames the wheel's own spin and drag need. Item details is unaffected either way and always shows the model; when the model cannot be shown it falls back to the 2D still with a "Failed to load 3D item" toast.
 
 Xsolla Metrika analytics is on by default. Pass your project ID as `externalId` / `external-id` so every Backpack event carries it as `eid`. Metrika builds a device fingerprint, so collecting that is your call as the owner of the user's consent: without it, turn analytics off with `enableAnalytics = false` / `enable-analytics="false"`. Removing the attribute turns it back on. If your page already runs Metrika, Backpack reuses that instance, so initialise it before the element mounts. Otherwise Backpack starts its own, with automatic page tracking off. `external-id` does nothing while analytics is off.