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

HybridPlotWorld does not respect configured schematic path #4408

Open
2 tasks done
PseudoResonance opened this issue Apr 21, 2024 · 0 comments
Open
2 tasks done

HybridPlotWorld does not respect configured schematic path #4408

PseudoResonance opened this issue Apr 21, 2024 · 0 comments
Labels
Requires Testing This is a new issue which needs to be approved before labeled with "bug"

Comments

@PseudoResonance
Copy link

Server Implementation

Paper

Server Version

1.20.4

Describe the bug

The HybridPlotWorld implementation loads schematics from the plugin folder and does not respect the configurable schematic path, as seen here.

To Reproduce

  1. Configure a different path to store schematics in under paths.schematics
  2. Generate new road schematics with /plot createroadschematic
  3. Attempt to regenerate roads with /plot createroadschematic

Expected behaviour

HybridPlotWorld should load schematics from the same location they are saved in, not exclusively the plugin root folder

Screenshots / Videos

No response

Error log (if applicable)

No response

Plot Debugpaste

https://athion.net/ISPaster/paste/view/442d7ad6af294da294858a052ccfd9bf

PlotSquared Version

PlotSquared-7.3.8-Premium

Checklist

Anything else?

If you don't want to change the HybridPlotWorld behavior, the documentation should reflect this.

@PseudoResonance PseudoResonance added the Requires Testing This is a new issue which needs to be approved before labeled with "bug" label Apr 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Requires Testing This is a new issue which needs to be approved before labeled with "bug"
Projects
None yet
Development

No branches or pull requests

1 participant