Import Structures via Encoded String

[gukangran2026-source]

I think we could add another feature - import from clipboard, so even on the server, people could import their own structures

[gukangran2026-source]

Or store the projection in aa resource package and then read it using a behavior package

[ForestOfLight]

Or store the projection in aa resource package and then read it using a behavior package

This was my original intention with Construct but as far as I'm aware, it's not possible to get any information from resource packs to behavior packs.

[gukangran2026-source]

What about the clipboard? The clipboard should work though

[gukangran2026-source]

Can't we just do it with the clipboard too? Just type in a piece of text and then have it recognize that text to generate the projection?

[ForestOfLight]

Text input is theoretically possible, but I have not been able to find a sufficiently large input field for the player to type into. Every one I've considered has a max input length that's nowhere near long enough to encode an entire structure file.

[ForestOfLight]

If anyone knows of a sufficiently large input field or another solution, I would be happy to include this import method!

[gukangran2026-source]

If anyone knows of a sufficiently large input field or another solution, I would be happy to include this import method!

Can items be stored in a concise format? For example, water would be 0000 111 22 0 - where 0000 is the position of the block in the chunk, 1 is the block ID, and 2 is the block status. If it's a non-original item, using its original ID would probably save some space. (I used a translator - please let me know if there are any mistakes.)

[ForestOfLight]

Yes, surely there is some kind of efficient encoding that would make the strings smaller, but that doesn't solve the input field max characters issue since large structures would hit the limit anyway. Perhaps pagination is a potential way forward.

[gukangran2026-source]

Yes, surely there is some kind of efficient encoding that would make the strings smaller, but that doesn't solve the input field max characters issue since large structures would hit the limit anyway. Perhaps pagination is a potential way forward.

That works too. It would be best to put appropriate markers at the beginning and end of the section so it's easier to import without making mistakes