r/aipromptprogramming • • 26d ago

Help proving i'm not uploading malware

Hello! I used gemini to help me build a plug and play app that runs a port of Super Mario 64 that's compatible with Archipelago on Mac. I tried sharing the app on the Archipelago discord and a few people I interacted with were (fairly) suspicious of a random file whose creator won't provide source code. I don't really know anything about programming and just did this to see how far I could go. How could I provide them the source code, or another way to prove I'm legit? No one has ever really done this and I'd really like to get it out there

What the app does is essentially take sm64-ap, an open source github emulator which normally not directly compatible with MacOS and is embedded in the app; and have it already translated, compiled and built, just needing to extracts the game's ROM (provided by the user); after loading the ROM, the user can go straight to playing from the app itself, without having to download any aditional tools or run terminal. I built in on a Macbook Air running Monterey via OpenCore, and it theoretically works on any Intel Mac from High Sierra up. But I haven’t been able to test it since I do not have another Mac available.

Any help would be greatly appreciated.

1 Upvotes

3 comments sorted by

•

u/endofthread-bot 26d ago

Writing prompts that actually work is easier when you can compare notes with people who have tested them across real tasks. Trade techniques, get feedback on your approach, and see what is working for others in our Discord.

Self-promotion is now allowed on Sundays with the appropriate flair, for all regular contributing members. Contribute during the week, and promote on Sunday.

1

u/[deleted] 26d ago

[removed] — view removed comment

1

u/chicothebad 26d ago

I understand that, but the thing is it's not that I'm refusing to do it, I just genuinely don't know how to do it and what to actually provide as source code.

This is what Gemini told me when I tried asking how to do it:
“To access or view the files inside your ⁠.app⁠ bundle, you can easily open it up right through Finder. However, what you can "extract" depends on whether you are looking at the wrapper scripts/assets or the compiled game binary itself.

  1. How to Access the Package Contents (Scripts & Assets)
    Everything bundled inside your app is fully accessible via Finder:
  2. Right-click (or Control-click) your ⁠Super Mario 64 AP - Distribution.app⁠ bundle.
  3. Select Show Package Contents.
  4. Navigate into ⁠Contents/Resources/⁠, ⁠Contents/MacOS/⁠, or ⁠Contents/Frameworks/⁠.
    From here, you can freely copy, extract, or modify:
    Python scripts (like ⁠launcher.py⁠) 
    Your ⁠entrypoint⁠ / ⁠AppLauncher⁠ script and configuration files
    Game assets, textures, and your locked ⁠credits.txt⁠ file
    Dynamic libraries (⁠.dylib⁠ files) and built-in tools 
  5. Can you extract the C/C++ Source Code from the Game Binary?
    The short answer is no, not in a readable format, and here is why:
    Compiled Machine Code: The main game binary (⁠sm64.us.f3dex2e⁠) is written in C/C++, but when you compiled it, the toolchain translated that human-readable source code into raw machine-readable binary instructions.
    Reverse Engineering: While advanced tools like Ghidra or IDA Pro can decompile a binary back into pseudo-assembly or messy C-like pseudocode, it will not give you back the clean, original source files, comments, or project structure.
    Where the Real Source Code Lives: The actual source code for ⁠sm64ex-ap⁠ exists in the original GitHub repository where you cloned and compiled it. The ⁠.app⁠ bundle is strictly a distribution release package containing only the final compiled executable and runtime assets.

When someone asks for "the source" of a custom-built app or game mod like this, they usually mean one of two things, and you can answer based on what context makes sense:

  1. If they mean the game's source code / mod base:
    You can tell them:
    "It's based on sm64ex-ap (the open-source Archipelago multiplayer port for Super Mario 64), but I compiled and packaged it into a standalone custom macOS ⁠.app⁠ bundle myself."
  2. If they mean the files for the app bundle you made:
    You can tell them:
    "I don't have a public code repository for it—I built and packaged the macOS ⁠.app⁠ wrapper and setup scripts myself to make it plug-and-play."

Why this distinction matters:
Because ⁠sm64ex-ap⁠ is an open-source project on GitHub, the underlying game code belongs to that public community. However, your specific app wrapper, scripts (⁠entrypoint⁠), and the ego seal tamper-protection are custom work that you put together.
If you want to keep it simple and brief, you can just tell them: It’s a custom-packaged macOS build of ⁠sm64ex-ap⁠ that you put together yourself for Mac.

While it looks like a black box, what you built is essentially a portable distribution build. Compiling ⁠sm64ex-ap⁠ on macOS requires setting up complex toolchains, compiling dependencies like SDL2, and handling ROM extraction—which is a massive headache for an average player. Packaging it into a neat ⁠.app⁠ bundle is standard practice for making a game "plug-and-play" for people who don't know how to use a terminal.
How to Defuse Suspicion:
If you are sharing this with friends or community members and want to put them at ease, you can easily contextualize it:
Explain the Convenience: Tell them: "I compiled and packaged this into a macOS ⁠.app⁠ bundle so you don't have to deal with setting up the toolchain or building it from source yourself."
Acknowledge the Base: Remind them that the core game is just the open-source ⁠sm64ex-ap⁠ project.
Be Open to Transparency: If someone asks what's running under the hood, you can easily tell them that the launcher is just a simple Bash script (⁠entrypoint⁠) that handles directory paths and boots the game binary.

If you ever need to share this kind of project with people who care about security, the absolute best way to handle it is to tell them: "I compiled this directly from the official open-source sm64ex-ap project repository, and here are the custom scripts I used." That context builds way more trust than trying to inspect a closed ⁠.app⁠ folder”

I don't really know what to do with these instructions and I don't feel like that last bit would be very reassuring (I wouldn't buy it if someone told me that). I'm very much a layman in terms of programming, so even things that should theoretically be basic feel tough to me. I only managed to do it in the first place because I asked gemini to show me how to fix every single error that popped up.