HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
pmret
papermario
C2023–2024
pmret / papermario

papermario

Decompilation of Paper Mario (Nintendo 64)

3Distinct people
3Mentions
0Explicit recommenders
1.6KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Decompilation of Paper Mario (Nintendo 64)

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month3 dated mentions

Observed mentions: 2023-04-20 13:19:14 UTC to 2024-01-13 22:19:24 UTC.

0122023-04-01 00:00:00 UTC to 2023-05-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 commentsApr 20232023-05-01 00:00:00 UTC to 2023-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-06-01 00:00:00 UTC to 2023-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-07-01 00:00:00 UTC to 2023-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-08-01 00:00:00 UTC to 2023-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsAug 20232023-09-01 00:00:00 UTC to 2023-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-10-01 00:00:00 UTC to 2023-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-11-01 00:00:00 UTC to 2023-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-12-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2024-02-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJan 2024

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Apr 20232023-04-01 00:00:00 UTC2023-05-01 00:00:00 UTC211
May 20232023-05-01 00:00:00 UTC2023-06-01 00:00:00 UTC000
Jun 20232023-06-01 00:00:00 UTC2023-07-01 00:00:00 UTC000
Jul 20232023-07-01 00:00:00 UTC2023-08-01 00:00:00 UTC000
Aug 20232023-08-01 00:00:00 UTC2023-09-01 00:00:00 UTC000
Sep 20232023-09-01 00:00:00 UTC2023-10-01 00:00:00 UTC000
Oct 20232023-10-01 00:00:00 UTC2023-11-01 00:00:00 UTC000
Nov 20232023-11-01 00:00:00 UTC2023-12-01 00:00:00 UTC000
Dec 20232023-12-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
Jan 20242024-01-01 00:00:00 UTC2024-02-01 00:00:00 UTC101

What Hacker News says

3 sources
> Apologies, I don't know much about (disassemblers for) modern ISAs; I'm mostly aware of "dumb" assembly languages used in the 70s and 80s, before macro assemblers, instruction modifier prefixes, instructions with opcodes that change based on argument types, etc. I was literally thinking about assemblers from the 80s, which are _anything_ but dumb. If anything, it is _todays_ assemblers which may be dumb. Just think how many 8086 assembler kits there were (and are) and whether their syntaxes resemble each other at all. Now single MASM itself and think of how many million ways you have to create a program that builds to the same object code, whether you use macros or not. (Did you use .if or CMP?) > it definitely did to whatever assembly language the IBM bootloader was written in. No. Just no. We have assembly listings of the IBM BIOS. E
Read the rest
ven the first line of it may be different depending on whether you use DW or DB and still compile to the same machine code. > There are no "technological measures" used to protect IP rights (i.e. DRM) in these older works; This is also wrong, because _there are_. We literally discussed 10NES which is one such method for a console two generations older, and you can see the ones from Paper Mario 64 right in the decompiled source: https://github.com/pmret/papermario/blob/main/src/general_he... > Re: ReactOS, and Re: 10NES... [incredibly-long-wall-of-text-that-you-keep-editing-and-moving-from-topic-to-topic-so-that-no-one-has-a-chance-to-interrupt-it-is-really-quite-hypnotic] No one is claiming that reverse engineering is illegal. What is claimed is that decompiling a protected work in full and then distributing that decompilation is definitely illegal. You can definitely decompile for reverse engineering. I have done it as part of my RL work, at least in the EU (which definitely clarifies that you have a right to decompile and _even copy_ the parts that are strictly required for interoperability. Not the entire game). But it is ridiculous to think (and I emphasize: ridiculous) that just because I apply a simple transformation to a protected work I can end up with a non-protected work that is legal for me to distribute without authorization. It would mean the end of copyright for computer programs as we know it. In fact, it is so ridiculous, that even since the act of _compilation_ is also a non-revertible transformation (or in your terms, non-bijective), the actual object code would NOT be subject to copyright ! (Because, despite what you're saying, what is copyrighted is the actual source code, with the object code being a derivate work).
In Paper Mario PC ports beckon as coder completes decompilation of the N64 classic

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.