Round 2 of staring at the computer screen for hours and wanting to put my face through it. but this time, not due to my own retardation.
so i code the discussed space optimizations in mid-February, not touching the file since 2/16. then yesterday, i pick it up again, and add/tweak a few labels so it'll assemble. but it runs like a mess. when a torch extinguishes, it's still illustrated as burning, and random un-lit torches show up in the wall or elsewhere on screen. occasionally, they'd disappear from their original places.
this is another case of "no way my changes are causing this". i stared at it so long that it took me from alert to fatigued, with frustration and rage varying but persisting through many levels of consciousness. a little after waking up today, i finally pin down the issue to MathOnNapkins' disassembly (from which i've copied much of my code on this iteration; why rebuild the wheel?):
LDA $0540, Y : ASL #2 : STA $0540, Y : STA $7EFB40, X
that should be "ASL / LSR". while the two ASLs did seem a little odd yesterday, it took scanning an original disassembly today to learn the problem. dunno whether it was a manual typo, or if there's some wider malfunction in any program he's using to automate things.
drove me effing nuts! i can't really judge, as i've had incorrectly disassembled or typed instructions in my own documentation sometimes. but these pseudo-instructions (see also: "CLC / ADC $nn" becomes "ADD $nn") annoyed me even before this issue popped up. this is assembly language; don't obscure stuff from the reader.
Yeah, yeah, blame a guy who doesn't post here... :trollface: If the game doesn't crash, you could have posted it and say it's a cool new feature, like a lot of programmers say when someone finds a bug :P
It's really funny how just 1 byte can screw a game that much xD
it seems to run alright. but if you're up for further testing, that'd be appreciated. i hesitated to ask when i knew this is not a final product candidate (as it still needs $0414 and/or room-specific checks). but clearly, this cursed project needs to be checked at every remotely major update.. because when it's not me forgetting how to count bytes, there's trouble like this.
Tested and everything seems fine.
i hesitated to ask
You shouldn't. If you need something, just ask for it.
This time, I have been a little slow replying, but it's because I didn't see it earlier. I was checking this forum like... once a week? And the last time I tried to check it, the website was offline, but I try to answer as quickly as possible. Normally, if I see activity, I check it every day.
We have EVEN MORE themes now, but some old ones are gone...
Show Posts
.
