Jump to content

Recommended Posts

Posted (edited)

Hey! Can anyone explain what the tries, xSpread and ySpread actually do?

 

public static final BlockClusterFeatureConfig FLOWER = (new BlockClusterFeatureConfig.Builder(
            new SimpleBlockStateProvider(BlockInit.FLOWER.get().getDefaultState()),
            new SimpleBlockPlacer())).whitelist(ImmutableSet.of(Blocks.GRASS_BLOCK))
            .tries(1)
            .xSpread(25)
            .ySpread(25)
            .build();

 

I always thought that the tries is how often it spawn. But if I use the Spread and set the tries to around 100 it doesnt feel, that it spawns more often.

 

My problem is now that I want to make the flowers a bit rarer and I also want to make a config file so that someone can change the rarity via the tries. 

 

Thanks in advance!

Edited by Timebreaker900
Posted

Look at the placement itself and how the variables are used. This looks like something for 1.15.2. It actually does do exactly what you said; however, you are thinking about the placement incorrectly. While it is true that it should generate 100 times, you are also neglecting the starting block position. By default, it will spawn at the height specified by the block position. However, if you try and variate the movement, there is a chance it might spawn within a block or in the air, making it nonviable to generate. Variating the x and y positions will have this affect although it is necessary to make it spawn more than one particular flower. Rarity of placement is more of a luck of the draw type thing like any other probabilistic type outcome. The more chances you give, the more you see a more probabilistic outcome. To make a flower rarer, you can just as easily make a block placer which has a probability to spawn the flower. As for having it generate from a configuration file, you would need to attach the features to reference a supplier holding the actual value of the config file. Otherwise, the changes will not be synchronized across sides.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Announcements



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • Hello , when I try to launch the forge installer it just crash with a message for 0,5 secondes. I'm using java 17 to launch it. Here's the link of the error :https://cdn.corenexis.com/view/?img=d/ma24/qs7u4U.jpg  
    • You will find the crash-report or log in your minecraft directory (crash-report or logs folder)
    • Use a modpack which is using these 2 mods as working base:   https://www.curseforge.com/minecraft/modpacks/life-in-the-village-3
    • inicie un mundo donde instale Croptopia y Farmer's Delight, entonces instale el addon Croptopia Delight pero no funciona. es la version 1.18.2
    • Hello all. I'm currently grappling with the updateShape method in a custom class extending Block.  My code currently looks like this: The conditionals in CheckState are there to switch blockstate properties, which is working fine, as it functions correctly every time in getStateForPlacement.  The problem I'm running into is that when I update a state, the blocks seem to call CheckState with the position of the block which was changed updated last.  If I build a wall I can see the same change propagate across. My question thus is this: is updateShape sending its return to the neighbouring block?  Is each block not independently executing the updateShape method, thus inserting its own current position?  The first statement appears to be true, and the second false (each block is not independently executing the method). I have tried to fix this by saving the block's own position to a variable myPos at inception, and then feeding this in as CheckState(myPos) but this causes a worse outcome, where all blocks take the update of the first modified block, rather than just their neighbour.  This raises more questions than it answers, obviously: how is a different instance's variable propagating here?  I also tried changing it so that CheckState did not take a BlockPos, but had myPos built into the body - same problem. I have previously looked at neighbourUpdate and onNeighbourUpdate, but could not find a way to get this to work at all.  One post on here about updatePostPlacement and other methods has proven itself long superceded.  All other sources on the net seem to be out of date. Many thanks in advance for any help you might offer me, it's been several days now of trying to get this work and several weeks of generally trying to get round this roadblock.  - Sandermall
  • Topics

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.