aes

Well, you can do the composition on the fly, by having the different sides of the diagonal on different tilemap layers, that'd make things easier, right?

Check my thinking here, but you'll get a checkerboard pattern alternating diagonals, right? Then, I'd suggest

• two layers, 'far' and 'near', for the tile-halves
• a parent 'control' tilemap layer, with ugly editing tiles offset half a tile, (so it gives you a way to draw using the materials you care about) and code to render that into the fragment layers.

It's how this works: https://github.com/aes/autotile3d and it would work.

But then, there's this, I guess: https://youtu.be/dclc8w6JW7Y

First thought: Wow, that looks just like how Syndicate works.

Second: that's a terrible idea. (at least in 2025)

There's a tutorial (this one, I think https://youtu.be/i_XV78N7Zuo) on how to make a tool to compose your tiles.

If you want to make a tile-space renderer, that's harder, but having done it, I can probably talk you through it. You need to look through tile-space diagonally to make in-front/behind work correctly. The way I'd do it today would probably be to 'shoot rays' from the view direction, into the tile-space, and record the first, or however many tile fragments necessary to completely obscure the view. Then, just* render from that look-up-table. (there's a fruity view(x, y) to tile(x, y, z) transform, and you still need to render transient objects at the correct depth. Also, scrolling/panning, do you only do that by tile, or do you also do sub-tile-fragment pan?)

If you can get away with just stacking some tilemaps, do that instead, but ask if you need more.

For 32-bit space I can simply make a 512MB Bitmask lol and then AND/OR the two Bitmask. Easy

Uh, no, that's O(n), yeah?

That's not what I need

That's maybe something I think is sus. If it's at all possible, make a before-rebase branch, and make a small change in a rebase, check that the results are the same, then do another. I wrote git-test specifically for this work flow. (it runs tests, but only if the tree is one or hasn't seen before)

https://github.com/spotify/git-test

Change who's around you.

Plan B, try to change how you let them affect you. Easier said than done, but very effective when pulled off.

The perspective shift is this: if they bully you, tease you, put you down, and you get angry and sad, notice that you let them decide your feelings. Instead, view what they say, as something that says more about them than it does you.

Source: I struggled with bullying. I'm still considered odd, but that I'm OK with that.

No, but that's what it meant. Or maybe it was malicious, but it doesn't matter, because you need to give it the best interpretation. Somebody else reading it might take that interpretation and agree, so write for them, not the original commenter. (troll or not)

I'm glad you're enjoying PHP and have given me another perspective on the subject.

This comment is not optimized for engagement.

This is why I'm here.

I really prefer .config and .cache to just having random crap in your home directory. It comes with fallbacks, too, if you want things somewhere else.

xdg dirs are a win. I don't know which parts you might be thinking about, (and quite possibly being quite right about,) but this part, at least, is good.

I use the same setup with Syncthing and Obsidian. The git plugin sometimes gets confused, but nothing I can't untangle. I also use Syncthing for pictures off my phone, and ebooks onto it.

Actually, I think I do have a setup that might qualify as unusual: I use the scheduled backup feature of Podcast Addict to get a listing of listened podcast episodes, and then I inject them into my Obsidian notes.

Tap water is so cheap it might as well be free, and it's probably included in the rent in a lot of places.

I guess it's not free in places that need to have a revolution first?

This.

Also, one of the machines is running the git plugin, so things get saved in my Forgejo as well. I guess I could set it up so they save to hit, but in different branches. 🤔

Fair, but it's also just a way of saying that programming isn't a task for humans. (At least not in the correctness aspect)