Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] configureItem() Broken | An unknown error occurred: [37] AssetIsLimited #836

Closed
OfficialSteam opened this issue Oct 5, 2024 · 4 comments · Fixed by #839
Closed

Comments

@OfficialSteam
Copy link

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:

  1. 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);
  1. Try to run it.
  2. 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

image
image

Additional context

Add any other context about the problem here.

@alanbixby
Copy link
Member

alanbixby commented Oct 5, 2024

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
Copy link
Author

OfficialSteam commented Oct 14, 2024 via email

@forkinghell0
Copy link

Is this being worked on?

@Neztore
Copy link
Member

Neztore commented Oct 26, 2024

Feel free to open a PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants