
Developer Experience and Engine Engineer @ Rare.
Working on tooling to make games go nyoom.
Also fluffy fox, modder and owner of https://foxes.rocks
| Pronouns | They/Them |
| https://twitter.com/KitsuneKihira |

Developer Experience and Engine Engineer @ Rare.
Working on tooling to make games go nyoom.
Also fluffy fox, modder and owner of https://foxes.rocks
| Pronouns | They/Them |
| https://twitter.com/KitsuneKihira |

I've got a spooky themed party this weekend so I made my own witch hat! I'm supposed to put more decorations on the top but tbh, I kinda love it just like this. It's mostly just left over felt but I also brought a bunch of stuff to go on top and I might just return it
I followed these to make it!
https://redshoesredwine.com/witch-hat-diy/
https://redshoesredwine.com/loblolly-witch-hat/
https://www.youtube.com/watch?v=Iz2nulh2pFo
There's a cool new Datapack in town!
"Engineered Compatability" ties Immersive Engineering in with a bunch of other mods (and some vanilla recipes too!)
This is developed by Voidsong, who has contributed a bunch of content to IE recently and she has now made this datapack of things that don't belong in core IE, but are still super useful to have!
Get it here:
https://modrinth.com/mod/engineered-compatibility
For those curious, the rough current stack:
- NextJS (honestly just using it host the GraphQL server atm, I still need to convince myself to do the frontend...)
- GraphQL Yoga
- Prisma (for model management and database access)
- Pothos (for generating GraphQL types/interfacing with Prisma)
- PostgreSQL
And that's actually about it. It's Typescript (wouldn't dare to try this in just JS) and a few other util libraries for parsing but thats it
However it's also quite nice to break out of that, especially for hobby projects. I often found myself getting bogged down in the weeds, writing the best framework to suit my needs, doing tons of research on new tech and just burning out on the project.
Whilst I did also learn a bunch of new tech during this project, it was a more "how do I use it" instead of a "how do I implement this".
I actually really like GraphQL as an endpoint, but I can see how painful it would be without frameworks