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

[Feature]: Identify cause of invalid configuration #390

Open
PikaMug opened this issue Dec 9, 2021 · 0 comments
Open

[Feature]: Identify cause of invalid configuration #390

PikaMug opened this issue Dec 9, 2021 · 0 comments
Labels
0.3.x Targeted for a 0.3.x version feature request New feature or request

Comments

@PikaMug
Copy link

PikaMug commented Dec 9, 2021

Describe the solution you'd like

Attempting to purchase an upgrade on 0.2.21 results in this warning:

Debug.warn("[BedWars]> Upgrade configuration is invalid.");

Please output a more descriptive warning so I can tell what's wrong.

Is your feature request related to a problem? Please describe

Here's the upgradeShop.yml I'm testing with (based on the snippet from https://docs.screamingsandals.org/BedWars/0.2.21/upgrades/):

data:
- stack: "APPLE;1;Upgrades;Upgrade your stuff."
  row: 2
  column: 3
  items:
   - price: 1
     price-type: iron
     upgrade:
      entities:
       - type: spawner
      spawner-type: iron
      add-levels: 0.2
      shop-name: "iron upgrade of the team %team%"
      notify-team: true
     stack:
      type: DIAMOND_BLOCK
      amount: 1
      display-name: "iron upgrade of the team %team%"
@PikaMug PikaMug added the feature request New feature or request label Dec 9, 2021
@zlataovce zlataovce added the 0.3.x Targeted for a 0.3.x version label Dec 9, 2021
@Misat11 Misat11 changed the title Identify cause of invalid configuration [Feature]: Identify cause of invalid configuration Dec 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0.3.x Targeted for a 0.3.x version feature request New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants