There where some discussions on Discord about this as well.

So, I am thinking a separate component would make sense as an option.

Someone also had the idea of making sure bingo spawns are always on the same chunk coordinate and to give a preference option to display chunk coordinates in HEX. I liked that idea for the more technical minded person, but I also don't think this is a good option for the general player.

My idea additionally to a separate component was to give the option change coordinate display to chunk coordinates when a certain condition is met (e.g. holding a treasure map in one of the hands). However, for the lapis trick you might want chunk coordinate display as well to avoid F3+G, so I don't like that option too much.

xz probably makes the most sense. Currently, there is no application for section coordinates I know of.

1. As I guess, we should do it as separate component, right?
   Like Chunk: 5 10 (xz) / Chunk 5 10 7 (xyz)
2. Probably still implement it within /components/player_position/,
   just like there are already both player_position and y_position updated after shared calculations:
   

   bingo/data/bingo/functions/custom_hud/components/player_position/update.mcfunction

   Lines 8 to 9 in 7af8f60

   	execute if data storage bingo:custom_hud currentPlayer.components[{id: "bingo:player_position"}] run function bingo:custom_hud/components/player_position/update_x_z
   	execute if data storage bingo:custom_hud currentPlayer.components[{id: "bingo:y_position"}] run function bingo:custom_hud/components/player_position/update_y

3. Also which configuration - xz or xyz?