The_Sky_rider
- thescientistabra
- JIRAUSER749052
- Europe/Stockholm
- Yes
- No
MC-261025
When you set the probability value of a custom processor list below 0.1, the processor list is ignored upon loading the world, (Note that there is no error logged.) **
Steps to Reproduce:
1. Create a custom processor list for a structure (I used the pre-existing processor list bastion_generic_degradation as it was easier to see) and set the probability of a noticeable change to 1 (Such as replacing blackstone with emerald blocks, You could also remove a pre-existing noticeable change).
2. Change the probability of any other rule to a value below 0.1.
3. Generate your structure and investigate it for your blocks that should have generated.
4. Change the second probability to 0.1 or higher, and generate your structure again.Observed Results:
While the second probability is of a value below 0.1, the 100% (Or 0%) chance rule was completely ignored, As in my case I had removed a rule which was showing up, the new processor list was being ignored not that particular rule.
**Expected Results:
The processor list to function, including the removal/insertion of new rules.I discovered it while removing a gilded blackstone from Bastion Remnents and found the processor list would not work with the default probability for blackstone -> air.
When you set the probability value of a custom processor list below 0.1, the processor list is ignored upon loading the world, (Note that there is no error logged.) **
Steps to Reproduce:
1. Create a custom processor list for a structure (I used the pre-existing processor list bastion_generic_degradation as it was easier to see) and set the probability of a noticeable change to 1 (Such as replacing blackstone with emerald blocks, You could also remove a pre-existing noticeable change).
2. Change the probability of any other rule to a value below 0.1.
3. Generate your structure and investigate it for your blocks that should have generated.
4. Change the second probability to 0.1 or higher, and generate your structure again.Observed Results:
While the second probability is of a value below 0.1, the 100% (Or 0%) chance rule was completely ignored, As in my case I had removed a rule which was showing up, the new processor list was being ignored not that particular rule.
**Expected Results:
The processor list to function, including the removal/insertion of new rules.I discovered it while removing a gilded blackstone from Bastion Remnents and found the processor list would not work with the default probability for blackstone -> air.
I should note that Air often causes the same issues for me, I'm not certain that this is problem is on Minecraft's end.
When you set the probability value of a custom processor list below 0.1, the processor list is ignored upon loading the world, (Note that there is no error logged.) **
Steps to Reproduce:
1. Create a custom processor list for a structure (I used the pre-existing processor list bastion_generic_degradation as it was easier to see) and set the probability of a noticeable change to 1 (Such as replacing blackstone with emerald blocks, You could also remove a pre-existing noticeable change).
2. Change the probability of any other rule to a value below 0.1.
3. Generate your structure and investigate it for your blocks that should have generated.
4. Change the second probability to 0.1 or higher, and generate your structure again.Observed Results:
While the second probability is of a value below 0.1, the 100% (Or 0%) chance rule was completely ignored, As in my case I had removed a rule which was showing up, the new processor list was being ignored not that particular rule.
**Expected Results:
The processor list to function, including the removal/insertion of new rules.I discovered it while removing a gilded blackstone from Bastion Remnents and found the processor list would not work with the default probability for blackstone -> air.
I should note that Air often causes the same issues for me, I'm not certain that this is problem is on Minecraft's end, as it doesn't always happen.
When you set the probability value of a custom processor list below 0.1, the processor list is ignored upon loading the world, (Note that there is no error logged.) **
Steps to Reproduce:
1. Create a custom processor list for a structure (I used the pre-existing processor list bastion_generic_degradation as it was easier to see) and set the probability of a noticeable change to 1 (Such as replacing blackstone with emerald blocks, You could also remove a pre-existing noticeable change).
2. Change the probability of any other rule to a value below 0.1.
3. Generate your structure and investigate it for your blocks that should have generated.
4. Change the second probability to 0.1 or higher, and generate your structure again.Observed Results:
While the second probability is of a value below 0.1, the 100% (Or 0%) chance rule was completely ignored, As in my case I had removed a rule which was showing up, the new processor list was being ignored, not that particular rule.
**Expected Results:
The processor list to function, including the removal/insertion of new rules.I discovered it while removing a gilded blackstone from Bastion Remnents and found the processor list would not work with the default probability for blackstone -> air.
I should note that Air often causes the same issues for me, I'm not certain that this is problem is on Minecraft's end, as it doesn't always happen.
When you set the probability value of a custom processor list below 0.1, the processor list is ignored upon loading the world, (Note that there is no error logged.) **
Steps to Reproduce:
1. Create a custom processor list for a structure (I used the pre-existing processor list bastion_generic_degradation as it was easier to see) and set the probability of a noticeable change to 1 (Such as replacing blackstone with emerald blocks, You could also remove a pre-existing noticeable change).
2. Change the probability of any other rule to a value below 0.1.
3. Generate your structure and investigate it for your blocks that should have generated.
4. Change the second probability to 0.1 or higher, and generate your structure again.Observed Results:
While the second probability is of a value below 0.1, the 100% (Or 0%) chance rule was completely ignored, As in my case I had removed a rule which was showing up, the new processor list was being ignored, not that particular rule.
**Expected Results:
The processor list to function, including the removal/insertion of new rules.I discovered it while removing a gilded blackstone from Bastion Remnents and found the processor list would not work with the default probability for blackstone -> air.
I should note that Air often causes the same issues for me, I'm not certain that this is problem is on Minecraft's end, as it doesn't always happen, and tends to fix itself after a few minutes without any input.
I've tried that Dhranios... That's how I get percentage values, I have tried the command:
My movement speed value is 0.4. It should return 400.0f, but it returns 0.0f
I'm also trying to pull it from the attribute command, so I don't have to calculate what my speed at any time is (I have upgrades that increases the player's movement speed by 0.02 or 0.01)
Thx tryahtar, I did not know that you had to (or even could) place the scale at the end of the command,
But it still feels off to me, Everything else you can place the scale factor in the after the execute store and get the proper value, only the movement speed attribute does this,
Updated.
Added