[BUG] configureItem() Broken | An unknown error occurred: [37] AssetIsLimited
Closed this issue · 4 comments
OfficialSteam commented
Before posting a bug, be sure that someone else has not posted it already and it is an actual bug with noblox.js and not other frameworks like discord.js
Describe the bug
When you attempt to use configureItem()
it will error and say "An unknown error occurred: [37] AssetIsLimited"
To Reproduce
Steps to reproduce the behavior:
- Create a basic function to config a price, for example
const noblox = require("noblox.js")
const newPrice = 100
const assetId = "ASSET_ID"
const assetName = "ASSET_NAME";
const description = "ASSET DESCRIPTION";
await noblox.configureItem(assetId, assetName, description, price);
- Try to run it.
- It will then error and say "An unknown error occurred: [37] AssetIsLimited" or something of the sorts.
Expected behavior
I expected it to change the asset's price and not error.
Screenshots
Additional context
Add any other context about the problem here.
alanbixby commented
Clarification for maintainers, it is not broken, it is incompatible with post June 2024 t-shirt that go through the publishing fee workflow.
We likely should create a new endpoint that uses itemconfiguration.
, and update this endpoint to redirect use that if they get an assetIsLimited error
Example API calls in the #reverse-engineerinh channels
OfficialSteam commented
What do you think the ETA on that is?
…On Sat, Oct 5, 2024 at 5:58 PM Alan Bixby ***@***.***> wrote:
Clarification for maintainers, it is not broken, it is incompatible with
post June 2024 t-shirt that go through the publishing fee workflow.
We likely should create a new endpoint that uses itemconfiguration., and
update this endpoint to redirect use that if they get an assetIsLimited
error
—
Reply to this email directly, view it on GitHub
<#836 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A5P34SYOBG56G2644W2E3BLZ2BVILAVCNFSM6AAAAABPNVZAUSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJVGIYTSNZRGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
forkinghell0 commented
Is this being worked on?
Neztore commented
Feel free to open a PR