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

Insights checks are done before build checks #124

Closed
crafter23456 opened this issue Aug 6, 2021 · 1 comment · Fixed by #125
Closed

Insights checks are done before build checks #124

crafter23456 opened this issue Aug 6, 2021 · 1 comment · Fixed by #125
Labels
enhancement New feature or request
Milestone

Comments

@crafter23456
Copy link

  1. image
    Is it possible to turn off the message & actionbar that the plot get scanned, should be only for owner
  2. Limit is for example 10k per plot, I have on one side 12k blocks placed per command & on the other plot side of the merge I cant place more so I think the limit should be doubled
  3. The redstone limit message appears even if the user isnt trusted.
@FrankHeijden FrankHeijden added this to the v6.6.0 milestone Aug 12, 2021
@FrankHeijden
Copy link
Member

Point 1 & 3 can be configured with the options provided by #125, which will allow the ability to customize the eventpriority of certain events. Setting the priority higher will result in that other plugins can do their checks before Insights.

Point 2 is actually similar to #100, which is about making limits proportional to the region size.

@FrankHeijden FrankHeijden added the enhancement New feature or request label Aug 12, 2021
@FrankHeijden FrankHeijden changed the title few things Insights checks appear before build checks Aug 12, 2021
@FrankHeijden FrankHeijden changed the title Insights checks appear before build checks Insights checks are done before build checks Aug 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants