https://modrinth.com/mod/hexsky
v1.0.8 adds propper Iota SerDe support (meaning you can now read/write them when using Computer Casting)
@19phoboss98 I heard you request this >:)
computer casting is a feature of hextweaks
and yes it no longer depends on ducky (and even differs in some cases from ducky peripheral’s format)
All right, how does it work? I cant find any docs about it… is it like an api? How do I read and write iotas to computers?
Best statement I can say is generate a iota in Hex using runPattern and call popStack/getStack
If it can be put into CC it will have a iota$serde field with a non "null" value
But normal lua types (number, string, boolean) do map directly to hex
ah so should it be like:
{
iota$serde = hextweaks:pattern,
startDir = "SOUTH_EAST",
angles = "aqaaq",
}
I tried doing this instead since lua didn’t want me referencing iota$serde like that:
wand.runPattern({
["iota$serde"] = "hextweaks:pattern",
startDir = "SOUTH_EAST",
angles = "aqaaq",
})
Once I implement hexal serde. (And mabey complex hex serde also)
Wait there’s a 4.0.1 and a 4.0.2? Where can I get them? I cant seem to find them in the modrinth page or in the github releases
They are hextweaks versions
Screenshot_20240924_083756_Chrome.jpg
I think the torque spell is still to expensive. I made an issue thread about it:
https://github.com/walksanatora/hexsky/issues/24
is it really too processing intensive to multiply the torque with the ships inv inertia tensor?
the new assembly spell works but it offsets the child ship a bit:
https://github.com/walksanatora/hexsky/issues/25
I think I found out what’s causing it, see the end of the issue thread
This conversation is on Discord · Reply there
image.png
image.png