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
I think a very useful "NOT" operator should also be an option. This mainly arose from trying to compare coordinates of 2 features with limited customizations (e.g. comparing spawn to world origin, where I want seeds where spawn is NOT within 100 blocks of it). This can be implemented as a checkbox in the customization.
The text was updated successfully, but these errors were encountered:
1) fixed broken system theme on linux since last version (#140)
2) fixed map artifacts at a large zoom (#135)
3) fixed UI freeze when using 48-bit block search with strongly restrictive conditions (#145)
4) fixed analysis of condition trigger not giving proper insight about its activation
5) changed area input to allow flipped coodinates (#133)
6) changed seed type indicator so it is hidden for number input (#149)
7) changed the default scale at which structures are visible so they show up on a coordinate reset (#112)
8) added customization option for the scale at which structures become visible
9) added map loading indicator
10) added "ignore reference" option to exclude the source instance in relative conditions
11) added match-any biome search for 1.17- (#130)
12) added NOT logic gate helper condition (#138)
13) added quick access to biome color editor and structure zoom to preferences dialog
Has been added in 2.3.0.
Also there is now an option to just exclude the origin of the source in a relative condition, which can eliminate the need for a NOT in some circumstances.
I think a very useful "NOT" operator should also be an option. This mainly arose from trying to compare coordinates of 2 features with limited customizations (e.g. comparing spawn to world origin, where I want seeds where spawn is NOT within 100 blocks of it). This can be implemented as a checkbox in the customization.
The text was updated successfully, but these errors were encountered: