-
-
Notifications
You must be signed in to change notification settings - Fork 300
fix: don't bypass history with //ores #3258
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
base: main
Are you sure you want to change the base?
Conversation
dordsor21
commented
Aug 1, 2025
- also add copper and update limits
- also restrict ores spawning to region
- also fix caves out of region error
- fixes //caves Permission Issue //Ores Does Not //undo Consistently #3108
|
Given you updated the list of ores: is / was there any plan to add the deepslate variants as well? |
Mm yeah the ore generation settings aren't too obfuscated in the code so wouldn't be impossible |
- also add copper and update limits - also restrict ores spawning to region - also fix caves out of region error - fixes #3108
|
|
||
| public abstract class FaweRegionExtent extends ResettableExtent implements IBatchProcessor { | ||
|
|
||
| private final FaweLimit limit; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we mark this and the ctor param as nullable?
worldedit-core/src/main/java/com/fastasyncworldedit/core/function/generator/OreGen.java
Outdated
Show resolved
Hide resolved
worldedit-core/src/main/java/com/sk89q/worldedit/extent/Extent.java
Outdated
Show resolved
Hide resolved
| public void generate(Region region, GenBase gen) throws WorldEditException { | ||
| for (BlockVector2 chunkPos : region.getChunks()) { | ||
| gen.generate(chunkPos, new SingleRegionExtent(this, getLimit(), region)); | ||
| gen.generate(chunkPos, new SingleRegionExtent(this, null, region)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any specific reason for removing the limit, given it can be set on the EditSession and should be respected by all child extents?