Notices by blabber (blabber@chaos.social), page 4

Oh, I just triggered a clang sanitizer for the first time. Maybe it is just me, but the diagnostic message is aesthetically pleasing.

@daniel_bohrer Bugs? Features? Where's the difference?

It seems as if my dungeon generation code is indeed generating unconnected rooms.

Write test and you will find bugs. The difficult part is to decide if your tested code or your tests are buggy.

The last week I lost myself in #bhyve experiments.

@rixx @dwardoric Being the bitlbee-mastodon maintainer, I really hope it keeps working ;)

@rixx But, like @dwardoric, I am running FreeBSD 12. Maybe that's an OS specific issue?

@rixx I am using both, Twitter and Mastodon, in my bitlbee without any issues, though.

I know that I am late to the party, but I am trying out #bhyve with the EFI VNC framebuffer and it is awesome.

#FreeBSD

@saxnot Give charter a try. That is what I settled on. https://ctan.org/pkg/charter

I reached a point in my #roguelikedev experiment, where I'll take a step back and clean up the code, implement some tests and try to make it easier to extend and adapt, before trying to turn the whole thing into an actual game.

@pinkprius @zaehnchen Ich hab Mal testweise einen Filter auf (at)twitter.com eingerichtet. Mal schauen, wie sich das so auf meine Timelines auswirkt. Danke für die Tipps.

Gibt es eigentlich eine Möglichkeit in #Tusky, oder auch im nativen Mastodon Webinterface, Toots nach Clients zu filtern? Ich glaube meine Timeline wäre noch schöner ohne diesen ganzen Mastodon Twitter Crossposter Crap.

Alle sind auf dem Camp, nur ich geh heute Abend in den Space. *shrug*

Implemented a rough autoexplore mode, where @ tries to step on every tile, but prefers torches, if it sees them. All driven by a single Disjkstra map. Nice.

#roguelikedev

I visualized the flooding algorithm, that I'm using to generate the Dijkstra map for a level.

You won't probably notice it, but this visualization revealed a subtle bug, where the origin of the flooding got visited twice and ended up with a distance value of 1 instead of 0.

#roguelikedev

I visualized the flooding algorithm, that I'm using to generate the Dijkstra map for a level.

You won't probably notice it, but this visualization revealed a subtle bug, where the origin of the flooding got visited twice and ended up with a distance value of 1 instead of 2.

#roguelikedev

Spotted a classic off-by-one error in the gif. *sigh*