Also made a minor edit removing those white flashes in the climax scenes.
Sadly, was unable to fix the disappearing accessories bug for now.

NOT inspired by Ravenemore's goth Frankie Foster, though in hindsight I see the similarity.
Made in FFDec.

Might do some more classic /f/lash palette swaps at some point, lemme know if you have any ideas you want me to take a crack at.

Reiko 2 Halloween 2023 version.swf (1.93 MiB) 550x400, Compressed (Deflate). 1994 frames, 30 fps (01:06). Ver6, AS1/AS2. Network access: No. Text: Yes. Bitmaps: Yes. Audio: Yes. Video: No. [find in archive]

http://swfchan.com/41/200147/

I don't know why the FTF editor cut out the fingering and titfuck scenes, I'd have to re-edit them from scratch. Pretty neat how they slipped in that other cumshot though.

So that way the girls do get knocked up

btw nice job here

A. Copy/paste the word "FFDec" to google to get (JPEXS Free Flash Decompiler. Works with Java on Windows, Linux and macOS. (the answer to your question)

or

B. Put in effort to reply that you don't know.

JPEXs lets you adjust the asset colours without extracting, and for smaller edits that should be how you do it because there's always a risk of the asset getting fucked up when you extract, save and re-import it (different versions of flash accept different standards of svgs and whatever tool you're editing with probably won't know the exact standard you're targeting). if you DO extract make sure it's as svg because png assets will have aliasing and stretch/shrink poorly the moment you change the size of the flash player window. personally for editing svgs I just use https://www.svgviewer.dev/ and any of the online hex colour pickers.

>>100103
open the flash in jpexs. on the left panel go to shapes. find the shape you want to recolour. on the right panel, shapes -> fillstyle -> fillstyles -> find the exact fill that has the colour(s) you want to adjust, adjust as required. make sure to click save at the bottom of the window when you're done.
this can be pretty tedious, especially if there's a lot of colours to do that for. if you want to do it in another app, on the left panel, right click -> export selection. again, I am BEGGING you to export as svg, flash renders them so much better than any other format of asset.

I can view the sprites and animations and they are functional but have no idea where to restart repairing these from where they were left off.

ty again anon

eh, it's not that hard, just fiddly. here https://pixeldrain.com/u/41LTEnL2 dunno if you want to put this in the archive too? not sure how I'd feel about uploading the 3rd version of this flash after I've made the smallest edit to it compared to your work, so your call.

if you care, here's a little bit about how I did it (if this helps even one person make edits I'm happy)
firstly, you're gonna want to set the view (the rightmost option on the top ribbon under "file") to the tag list, not resources. tag list shows us the items in the flash (shapes, buttons scripts) like they are actually laid out in the flash, that is to say, sequentially and first appearing only on the first frame they're needed. this will be very helpful shortly

now, we search the actionscript (tools -> text search) for either of the clothes toggles. luckily, in this flash they're named "jacket" and "leg", so they're easy to find. it would be a little trickier (or rather, tedious and time consuming) to find them otherwise.

this is where the tag list is helpful. when we find the jacket's definesprite tag with the script (511), you'll notice that there are two buttons right above it in the same frame (509 and 510). these are the buttons for toggling the on and off state. if we were in the resources view it would be much harder to identify which button controlled this, but since they're right next to eachother here we know it's them.

actionscript2 is basically a dynamic language, like javascript or python if you have any experience. so we can just tell it that the _root object (the central object of the flash that every script must have access to) has a boolean flag for the clothes being off or on, and actionscript will just accept this. so we can just set the jacket button to set "_root.showJacket = true;" and it'll do that. then we just have the sprite set the jacket on or off depending on that field, in each of the DoAction tags in the sprite's frames.
then, I also set up a little "firstRun" flag in one of the DoAction tags in the same frame (frame 317, I mean). if the flag isn't set, we set the clothing to be hidden (as default) and then set the flag. this means the clothing will remember the toggle setting when you press "do it again".

i hope this made sense. i program a lot so most of this feels natural to me, if you feel I missed something let me know. I understand this type of stuff looks intimidating but really it's mostly just knowing where to look (or getting good at guessing).

personally, I wish I was better at art. the main edit I've always wanted for this flash was making it so she wasn't getting fucked by such a fat piece of shit. oh well

Niiice. Could you tell us something about actionscript3, so I knew something in case if I'll decide to develop a flash game/animation?

atleast from the editing side though, as3 has mostly identical syntax, the scripts are just in different places. they're in their own section, rather than frame specific stuff. for instance, in most of zones later stuff almost all of the logic is in the "MainTimeline" script (I would use the Resources view for AS3 scripts mainly, since it's all consolidated already so you don't have to find stuff). Note that I said "almost all", there will be a bunch of other smaller script files but generally they won't have anything of interest in them. sometimes they will, but rarely. now, I don't know if this is how the scripts are actually displayed when you're making the flash, or if it's just a quirck of how jpexs decompiles as3.

anyway, the main differences to what I said in the previous message would be that you would have to directly define the boolean flags in the maintimeline class, instead of just saying that _root has them and flash going along with it. that's easy, in any as3 flash with any logic at all you'll see a bunch of these definitions at the start of the maintimeline script, you can just copy how they do it.
also in as3 you can directly access the sprites and their state in the other scripts by naming the sprite (when the sprite is added to the frame), and having a variable with the same name and type declared. then you just access it like you would any other. so for the jacket (if this flash was as3 instead of as2) I would declare "public var arm2a:MovieClip;" ("arm2a" being the name of the arm sprite which the jacket is attached to, MovieClip being the type of the sprite) and then to toggle the jacket to show on the arm, "arm2a.jacket2a._visible = true;" (jacket2a being a named child of the arm2a sprite). if you've done any programming this should be fairly familar to you.

Don't worry too much about spamming up swfchan with other versions, the poster who made all those Umeko polishing edits put a lot of them here too. As well as that anonymous, mysterious person with all those HKG edits.

As for the fat ugly bastard, maybe another partner could be spliced in from one of the many other FTF edits of this piece. Reiko is swfchan's most prolific cosplayer, after all.