I tested locally on the Ruffle nightly release /f/ uses, so short of lamely uploading an asset-less "test" version and bumbling through trying to "Delete Post," all for the sake of identifying issues I'd never even begin to understand or at least immediately know how to fix, why not just role the dice and upload it?If it's completely broken, that's what the "v1" at the end is for, silly.It should go without saying, but sorry I left so unceremoniously 10 years ago—The only remedy is to just as unceremoniously reappear.On the event the flash is playable/interactable: If you come across any breaky problems I'd be glad to know about them; any flash-functional questions, I'd be even more glad to attempt an answer.
LOLJust look at that pixelation.So THAT's the difference between running locally and running through browser: Small .pngs do NOT retain their bitmap crispyness, also the font in the info bar has changed.Downloading it and running it on Ruffle/Flash locally seems to correct it: The font should literally be discrete pixel-blocks and should stretch from the left to the right of the frame. I guess there WILL be a v2, and it's gonna be all default text-boxes and simple scrolling, none of this fancy .png stuff.
>>3518011spent 30 seconds reading the most schizophrenic text ever and then i just played with the 't' sound restart pretending im a dj as i scrolled down infinitely
>>3518018>spent 30 seconds reading the most schizophrenic text ever and then i just played with the 't' sound restart pretending im a dj as i scrolled down infinitelyThat was the intended experience, Tiësto.
>>3518012Don't bother optimizing (or butchering) for ruffle; given the point is to emulate flash, if the project is competent and has drive , things that don't work should eventually and it's not worth making it worse in order to accomodate it when you can just watch it in the player anyways.
>>3518029>Don't bother optimizing (or butchering) for ruffle; given the point is to emulate flash, if the project is competent and has drive , things that don't work should eventually and it's not worth making it worse in order to accomodate it when you can just watch it in the player anyways.Yeah, I've been coming to that conclusion as the day's gone on; it works just fine on the app player, and that's really all I could ask for.I'm actually really proud of myself for coming up with the solutions I implemented, but I'm also aware it's my first foray into ActionScript/openFL, and those were just "possible" solutions—I want to go back and remake it, but not in order to abitrarily placate browser-Ruffle (to whom I owe nothing! lol), but to learn more techniques.
Holy crap! He back :o
>>3518011I forgive you for leavingBut I do not forgive for not coming back here on December 31 2020
I don't get it
>>3518035>Holy crap! He back :oI'd say, "I never left," but—yeah—I, like, totally left o:>>3518044>I forgive you for leavingWhat a gift :)>But I do not forgive for not coming back here on December 31 2020I can't imagine how special Deprecation Day must have been. If I ever get a time machine you'll have seen me there.>>3518048>I don't get itJust a miasma of creativity (writing, music, flash-construction, etc.) that needed exorcising, partly due to the sum's increasing unwieldlyness.If it's hard to parse, then that makes sense: No matter the circumstance, I've been known for inadvertently brokering ceasfire-deals between stomach muscles—in other words, everything I touch becomes "abstruse."If by "I don't get it" you mean you literally can't read the grabled flash, but you want to, but you also don't want to download it to play it on a non-browser flash emulator, I pdf-catbox'd it >>>/lit/24119353
>>3518055It was special. That day, /f/ was the fastest board on the entire site. A bunch of old flashers that haven't been on the site in a while also came.