megazeux.bsky.social
I make MegaZeux, games for MegaZeux, and other junk. MegaZeux is a cross-platform game creation system originally written for DOS in 1994 by Alexis Janson.
she/her · Account run by Lachesis · https://digitalmzx.com/
66 posts
68 followers
33 following
Regular Contributor
Active Commenter
comment in response to
post
(but acknowledging this would require introspection that they are incapable of)
comment in response to
post
yeah. they don't get that 1) most leftists sucked it up and voted for her anyway, and 2) most that didn't hail from states where she won anyway. if they want a demographic to blame it's dudes in a handful of states that weren't inspired enough to stand in line for hours instead of paying bills
comment in response to
post
how Dare you imply spending the back half of the campaign hanging out with the cheneys is anything but genious,, 4-dimensional political chess
comment in response to
post
Also, a clarification: MegaZeux is *also* unaffected by the CVE since it was in ProWizard, a part of libxmp that MegaZeux doesn't use.
comment in response to
post
Example: in Scream Tracker 3.03+, if a Pattern Loop jumps on the same row as a Pattern Break or Position Jump, the Pattern Loop jump ALWAYS takes precedence. Impulse Tracker 2.00+ is similar, except it will instead give precedence to a Position Jump in a channel following the Pattern Loop jump.
comment in response to
post
The biggest format/playback fix this time is probably that libxmp has initial support for handling interactions between Pattern Loop jumps and Pattern Break/Position Jump effects on the same row on a per-format basis. This is currently supported for most ITs, most S3Ms, and a few other formats.
comment in response to
post
I *think* a statement like this should be enough for Wii devs to cover the FOSS code that libogc copied, yes.
comment in response to
post
comment in response to
post
at what point does "passively violating OSS copyright" turn into "actively violating OSS copyright", I wonder
github.com/devkitPro/li...
comment in response to
post
b-b-but I was told the code wasn't Taken Directly™ 😰
www.rtems.org/news/2025-05...
comment in response to
post
official line seems to currently be "sorry uwu, no code was directly copied, therefore we didn't actually do an accidental copyright". reminder: the only thing they'd have to do to fix the problem they're trying to deny is to copy and paste around some license boilerplate.
comment in response to
post
When you find out your code looks nearly identical in structure to someone else's free licensed code and the person who wrote it confirms they "studied" the original too closely, the correct response is to add the original copyright or to replace the code, not to ignore it for over a year tbh
comment in response to
post
literally $5 right now and no DRM 👍
www.gog.com/en/game/elde...
comment in response to
post
Might be possible to instrument your build with ASan+UBSan to catch whatever this is in the act of corrupting the heap? I have not tried this with the 3DS though
comment in response to
post
yep: 3+ trans lead developers/maintainers and likely dozens of MegaZeux games made by trans authors. Unfortunately I don't think exhaustivity was the goal because MegaZeux is not hard to find, particularly if you scrutinize the works of other mentioned authors
comment in response to
post
The main problem here is the used market is eventually going to dry up due to disc rot and landfills. not clear if that's going to happen before all the hardware goes first though
comment in response to
post
as a SWITCH TO LINUX!11 person I would also like to mention that Windows 10 IoT Enterprise LTSC has official support until 2032. it is what I recommend to people stuck in the Windows ecosystem in the short term. we'll see how long commercial software supports it though..
comment in response to
post
Thanks for clarifying this! I'm not sure which version I'll use yet, but I will keep it in mind.
mainly i thought it would be funny if i took the hall of fame picture playing on my Special Pikachu Edition Gameboy but if i have to fight brock with pikachu then no way
comment in response to
post
can you mention Yellow in rule 3, or was it intentionally excluded?
comment in response to
post
I think it was a Museum of ZZT Discord meme for a while
comment in response to
post
This bug prevents dylibbundler from working for PowerPC64 builds and it took me longer than I'd like to admit to figure out! Fun!!!!!!!!!!!!!
comment in response to
post
also fun fact, modern otool loses its mind if you try to use it on PowerPC 64 binaries, which required another workaround. This is because it's based on llvm-objdump and LLVM has no clue how to handle the LC_UNIXTHREAD section of a PPC64 Mach-O. I needed a PATH hack to redirect it to otool-classic
comment in response to
post
the normal Xcode builds are just pressing a button twice in Xcode 14.2 for comparison
comment in response to
post
For the 5-arch builds, I boot High Sierra, run the first four builds from the command line, then reboot to Monterey and run the fifth and package them together. They need to be done in this order, because ARM64 macOS doesn't like High Sierra's codesigning.
comment in response to
post
I have a High Sierra install with Xcode 9.4.1 (x86/x86_64) sideloaded with the Xcode 3.2.6 toolchains (PPC/PPC64) via XcodeLegacy (which I had to patch for PowerPC 64), plus a Monterey install via OCLP with Xcode 14.2 for ARM64. Also the 2011 Mac Mini that runs these builds has hardware issues :<
comment in response to
post
It's literally impossible to do without a dual boot—the Xcode 3.2.6 toolchains will not run at all on any version newer than IIRC Mojave (10.14).
comment in response to
post
I think it's mostly a solved problem for now, but... wow. The Xcode project only needed a minor overhaul once I figured out how to build the dependencies, but the 5 architecture build is done with regular tooling and requires an x86_64 dual boot and some pretty nasty hacks (especially PowerPC 64).
comment in response to
post
Having worked through the logistics of deduplicating robot programs I can confirm that you should have left this in ZZT land :)
Looking forward to finally breaking out zap state into per-robot bitfields, but I keep having to deal with other things like fixing builds for developer-hostile macOS...
comment in response to
post
I also didn't mention it, but libxmp 4.6.2 was released a few days ago with a bunch of minor fixes mostly related to MED.