Freaking out YML parser is unhandled

[prplwtf]

Current Behavior

When messing up quotes in a extension configuration file, Blueprint will not handle it as an error but will also incorrectly install an extension.

Expected Behavior

Blueprint or the YML parser it uses to throw a user-readable error and stop the extension transaction.

Steps to Reproduce

Mess up quotes in any Blueprint extension configuration file. This includes conf.yml, Components.yml and Console.yml.

option: item""

Blueprint Version

beta-2025-01

Panel Version

1.11.10

Is there an existing issue for this?

• I have searched the existing issues before opening this issue.
• I have provided all relevant details and tested my reproduction steps.
• I have checked to my best capabilities and believe this is a bug with the software, and not a configuration issue with my specific system.
• I have made sure to check that this bug is the fault of Blueprint and is not caused by stock Pterodactyl.

[oiahoon]

Could you clarify the intended validation boundary here? option: item"" is a valid YAML plain scalar and parses as the literal string item"", while truly unclosed quoted scalars such as option: "item and option: 'item are currently accepted by parse_yaml with exit status 0 and reduced to item. Should this issue cover unclosed quoted scalars only, or does Blueprint intentionally enforce a stricter YAML subset that rejects quotes inside plain scalars? This distinction affects whether the fix should add syntax validation or a project-specific style rule.