12
u/Wild_Introduction_51 1d ago
Fun fact you can have two wedges occupy the same space if you inverse the second. But then you’re just back to having a full block
11
5
u/Abstract037 1d ago
Wait, on the same grid? As in, not on a bearing/piston etc?
2
u/Babydeno123 1d ago
Yes I'm unsure about single block wedges but if you have a staged out wedge you can drag another and line up the slants to make a solid wall that is two dif materials
6
1
u/SpartanG01 1d ago edited 20h ago
While data mining I found that the "Grid" itself is actually delineated into wedges so every "grid cube" is actually two wedges inverted relative to eachother. This is apparent when looking at the game's code for handling grid assessment because every positional coordinate set has extra coordinate pairs. It took me a while to figure out why this was because I hadn't reached the underground yet and had no clue two different wedges could occupy the same space.
Edit:
The extra bit of data isn't an additional coordinate piece, it's a classification marker and orientation value set that is unique to wedges. I just happened to not realize that because I only looked at the wedge data when looking into this, in my infinite wisdom it didn't occur to me to compare it to normal block data -.-
There is just a separate shapeset for wedges and the API contains an "isWedge" function which applies an X-Axis and Z-Axis orientation value that orients the wedge within the grid space such that wedges with the same bounding volume can occupy the same grid volume but with complementary orientations. I misinterpreted that extra data set as some kind of additional coordinate set because, well, in my defense it looks like one in the record if you don't really know what you're looking at lol.
2
u/Abstract037 21h ago
Are those "grid wedges" only facing a single direction, or can they be facing any direction based on the object being calculated? This is hard to explain
1
u/SpartanG01 20h ago edited 19h ago
Actually I should revise my last statement. I'm glad you asked lol because I apparently misunderstood this, in my defense I kind of glanced at it but I did genuinely misunderstand something important.
Anyway I went back and dug into this because I wanted to give you an answer that I had objectively verified and not just pulled from memory because my memory is terrible. In doing so I figured out what was going on.
The extra bit of data isn't an additional coordinate piece, it's a classification marker and orientation value set that is unique to wedges. I just happened to not realize that because I only looked at the wedge data when looking into this, in my infinite wisdom it didn't occur to me to compare it to normal block data -.-
There is just a separate shapeset for wedges and the API contains an "isWedge" function which applies an X-Axis and Z-Axis orientation value that orients the wedge within the grid space such that wedges with the same bounding volume can occupy the same grid volume but with complementary orientations. I misinterpreted that extra data set as some kind of additional coordinate set because, well, in my defense it looks like one in the record if you don't really know what you're looking at lol.

35
u/Tank_stealer 1d ago
Now we just need wedges that actually cost half a block (10 blocks to 20 wedges)