-
-
Notifications
You must be signed in to change notification settings - Fork 42
Panel integrity check and warning to prevent standalone-mod-caused issues #209
Copy link
Copy link
Open
Labels
scope:backendIssues or pull requests related to Blueprint's backend.Issues or pull requests related to Blueprint's backend.scope:cliIssues or pull requests related to the Blueprint CLI.Issues or pull requests related to the Blueprint CLI.
Description
Scope
Admin
Explanation
Many summer hosters and inexperienced users attempt to install Blueprint alongside non-Blueprint extensions. Instead of reviewing the documentation when issues arise, they often go straight to the issues tab and claim that Blueprint has broken their instance.
To address this, a feature could be added that checks whether the Pterodactyl Panel files have been modified. If such modifications are detected, Blueprint could immediately notify the user that it is not compatible with non-Blueprint addons and bail out.
Good idea(?), Stupid execution, please find another way to do this,
i'm very stupid in these kinds of things
Is there an existing issue for this?
- I have searched the existing issues before opening this issue.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
scope:backendIssues or pull requests related to Blueprint's backend.Issues or pull requests related to Blueprint's backend.scope:cliIssues or pull requests related to the Blueprint CLI.Issues or pull requests related to the Blueprint CLI.