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

Mantle thinks all badges cost 100 Robux but Roblox just announced that the first 5 badges within 24 hours are free #136

Closed
1 of 3 tasks
blake-mealey opened this issue Feb 25, 2022 · 1 comment · Fixed by #138
Labels
bug Something isn't working enhancement New feature or request

Comments

@blake-mealey
Copy link
Owner

blake-mealey commented Feb 25, 2022

What type of feature request is this?

  • Mantle doesn't support a Roblox feature I would like to use
  • Mantle CLI improvement
  • Other

Describe your problem

Mantle tells the user that they will be/were charged 100 Robux to create a badge no matter what. Roblox recently announced that every 24 hours allows 5 free badge creations per experience. See details here: https://devforum.roblox.com/t/announcing-free-badge-creations/1680515

Describe the solution you'd like

We'll need to look into what APIs they use to check if the price is currently free to estimate the price before telling the user what the cost will be. We might also be able to tell the user when the badge creation will become free in the warning logs. We may want to add a setting to never pay for badge creation (e.g. --dont-allow-badge-purchases). Maybe this is a sign that we should extend the basic --allow-purchases to actually be per purchase type. For example, --allow-badge-purchases and --allow-audio-asset-purchases or --allow-all-purchases to let all purchases go through.

@blake-mealey blake-mealey added bug Something isn't working enhancement New feature or request labels Feb 25, 2022
@blake-mealey
Copy link
Owner Author

Since audio can now be free (see #137), I don't think separating out --allow-purchases would be as useful. Some users might want to be cautious about using up their free quotas though. To handle this we could either make quotas opt-in (--allow-badge-uploads) or opt-out (--dont-allow-badge-uploads).

For now though I think the current implementation is sufficient - by default Mantle will only allow free creations, but if the user goes over their quota they can opt-in to further creations with --allow-purchases.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant