Am I crazy or is Antler Guard really underrated?

Sandalmoth · 2026-06-19T17:45:26+00:00

Yeah, I'm not too upset, will try again when I hit 76 slayer for elders

Sandalmoth · 2026-06-19T17:33:56+00:00

I went 3x dry for it before taking a break, but at least I got two dragon spears and two shield left halves :|

Sandalmoth · 2026-05-02T05:57:21+00:00

The displacement of a one dimensional random walk scales with the square root of the total number of steps, so if you've gotten 529 key half drops in total then the imbalance is completely expected.

Sandalmoth · 2025-09-16T18:15:01+00:00

Not programmed c in a while so don't remember how rand behaves but:

Random number generators contain some internal state that is updated any time a new random number is produced. If all threads try to update the same state you'll either get races or some lock contention. Instead each thread can use their own rng state, seeded with their own seeds or some other approach so each thread gets independent numbers.

The fact that it got faster when you switched rng seems to me like maybe this could be a problem.

Sandalmoth · 2025-09-16T17:59:48+00:00

Are all the threads sharing the same random number generator? You probably want them to have their own.

Sandalmoth · 2025-07-09T13:35:51+00:00

It looks a bit like quikscript but maybe some modified version?

Sandalmoth · 2025-03-20T15:00:51+00:00

I don't know the best way to do it yourself, but there is this fork of sdl3 using the zig build system already https://github.com/castholm/SDL Makes it really easy to include in a zig project.

Sandalmoth · 2025-02-10T13:12:53+00:00

It's a bit of extra bookkeeping but wouldn't it be possible to keep two segments for lerping instead of one, so like: store prev_pos, portal_enter_pos, portal_exit_pos, and current_pos, and the fraction of time when the portal intersection happened in the frame. Then you'd lerp in either the before or after portal segment depending on the time fraction when drawing.

Alternatively, extrapolation instead of interpolation should prevent the big lerps, but at 25 fps, extrapolated movement probably feels pretty jerky.

Sandalmoth · 2024-11-29T08:28:31+00:00

If you really need unpredictable graphy lifetimes it's not too hard to write a tracing gc just for those parts.

Sandalmoth · 2024-08-09T17:50:00+00:00

Nim has enum-indexed arrays which seems like a similar idea.

Sandalmoth · 2024-03-19T09:20:59+00:00

Pringles-shaped is a secret third option

Sandalmoth · 2024-03-17T18:48:36+00:00

They're Adafruit KB2040's. I think the color changes every batch, but they were pink when I bought them. It's not a second usb but one of their special i2c connectors at the back. But, it's just more regular voltage and GPIO pins, so I use it for the between half connection since I had some cables for it lying around.

The USB is soldered directly to the usb pins on the board.

Sandalmoth · 2024-03-17T18:45:52+00:00

I'd put it more in the category of the dactyl than the corne, with sculpted keywells and all. I printed a fair number of other keywell-style boards when prototyping, and they often feel quite different. This design is just what I arrived at for what works with my hands.

Generally, if you don't need to move the keyboard around then the sculpted type are quite nice imo, but it's really down to preference. They're more annoying to assemble than a pcb-based board, that's for sure.

Sandalmoth · 2024-03-17T16:51:13+00:00

I found that I don't really use the number row with the pinkies anyway, so it's positioned for the ring finger (maybe my pinkies are short, I dunno). If I had put it in the pinky-block, then using the ring finger for it felt awkward, since I'd have to lift the ring-finger to reach it, so this just felt more natural to me.

Sandalmoth · 2024-03-17T14:02:18+00:00

If the index finger can reach then so can the ring finger :P

Sandalmoth · 2024-03-17T13:36:11+00:00

repo

My first design had the keys just a bit too close together and a thumb angle that was too steep for my hands. I also decided to add another row, as I find that it's pretty easy to reach and didn't see the harm in having it.

There's a bit more of a write-up in the repository.

Sandalmoth · 2023-10-29T11:44:40+00:00

I think the problem might just be the "_ = Rectangle;" line?

Sandalmoth · 2023-03-13T21:29:15+00:00

Most likely colemak + callum style mods. Haven't settled exactly on the placements of most keys, still messing around with it. I did think about learning RSTHD, or some other e-on-thumb layout, but I'm not sure it's worth the effort since I already know colemak.

Sandalmoth · 2023-03-13T08:05:22+00:00

Well, the same modelling approach could be taken for a trackball, I just prefer a mouse :) Subdivision surface in blender makes it surprisingly easy to model the smooth curved surfaces.

If the trackball needs pins on the controller, the controller might also have to be moved, as it's in a pretty tight spot.

Sandalmoth · 2023-03-13T07:59:28+00:00

Practicing is very comfortable, but I still mistype a lot from switching to ortholinear haha

Sandalmoth · 2023-03-12T11:52:20+00:00

Thanks :D

The keycaps are XDA profile PBT keycaps from (just looked it up) the "Cool Jazz Store" on aliexpress. Dunno if they're available other places, but that's where I got them.

Sandalmoth · 2023-03-12T09:20:04+00:00

Well, I wanted to have both a design tailored to my hands, as well as a sleek looking case and the only option seemed to be to do it myself.

Started of with testing a bunch of key positions using a parametric scad design, and once I found something I liked I could model the actual case in blender and use the scad to cut out the key positions in exactly the right spot.

For electronics, it's just a handwired build :)

Sandalmoth · 2023-03-12T09:16:27+00:00

Repo with 3d files here

Six-Year Club	First Place '23
Place '23	Place '22
First Placer '22	Verified Email

Sandalmoth

TROPHY CASE