You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
10,000 is not arbitary, it is the value where the game can only choose a totem of undying by definition (All other items would require an amount of more than 5 at this point). Most of the times, the function newgoal.mcfunction does run more commands than the max chain length, which is set to 100,000 after installation of the datapack. Sometimes it does actually succeed, though.
When setting maxCommandChainLength to 1,000,000, a huge lagspike occurs and while the end of the function is reached (Debug say at the end of it gets executed), no item is chosen.
Possibly an edge case when the list of possible items has a length of 1.
The text was updated successfully, but these errors were encountered:
This happens on day 27, in the current difficulty scaling. I think the reasonable thing to do might be to just start scaling up the number of max items when the value starts getting very high.
- Tweaked max item count to 5 instead of 4.
- Allow requests of up to 10 items if difficulty is above 5000.
- Added back nether stars at 8000 value.
- Cap out difficulty at 20000.
10,000 is not arbitary, it is the value where the game can only choose a totem of undying by definition (All other items would require an amount of more than 5 at this point). Most of the times, the function
newgoal.mcfunction
does run more commands than the max chain length, which is set to 100,000 after installation of the datapack. Sometimes it does actually succeed, though.When setting
maxCommandChainLength
to 1,000,000, a huge lagspike occurs and while the end of the function is reached (Debugsay
at the end of it gets executed), no item is chosen.Possibly an edge case when the list of possible items has a length of 1.
The text was updated successfully, but these errors were encountered: