Original C64 Lode Runner Source Code
Posted3 months agoActive3 months ago
github.comTechstory
calmpositive
Debate
20/100
Retro GamingAssembly LanguageGame Development
Key topics
Retro Gaming
Assembly Language
Game Development
The original C64 Lode Runner source code was shared on GitHub, sparking discussion among retro gaming enthusiasts and developers about the code's structure, algorithms, and history.
Snapshot generated from the HN discussion
Discussion Activity
Active discussionFirst comment
8m
Peak period
18
0-3h
Avg / period
5.6
Comment distribution28 data points
Loading chart...
Based on 28 loaded comments
Key moments
- 01Story posted
Oct 19, 2025 at 6:13 PM EDT
3 months ago
Step 01 - 02First comment
Oct 19, 2025 at 6:21 PM EDT
8m after posting
Step 02 - 03Peak activity
18 comments in 0-3h
Hottest window of the conversation
Step 03 - 04Latest activity
Oct 21, 2025 at 2:41 PM EDT
3 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
ID: 45638514Type: storyLast synced: 11/20/2025, 7:35:46 PM
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
It will still be a while until copyright expires, unfortunately.
https://mmr.quarkrobot.com/
Is this good? I downloaded but Virustotal said 1/66 vendors gave > "MaxSecure Trojan.Malware.300983.susgen Acronis (Static ML) Undetected"
Probably a false positive but enough for me not to try it.
https://en.wikipedia.org/wiki/Lode_Runner_2
Here is the repository owner explaining the process himself: https://github.com/Piddewitt/C64-Game-Source-Code
Nice work and interesting still, but maybe we can correct the title?
A lot of old games were written in assembly. The difference between the disassembled and assembled code is/was pretty minimal.
What you ultimately lose out on is the comments and perhaps jump location names depending on the assembler.
https://github.com/Piddewitt/Loderunner/blob/main/Lode%20Run...
Original source, I imagine, would be very tersely commented, if only to fit in memory / floppy, and would have very short variable and subroutine names, and lots of mess and commented-out lines from experiments.
This looks like a very lovingly done disassembly.
Whatever happened to that guy?
https://www.mobygames.com/game/59739/moraffs-escapade/
Here it is in C (from my own notes)
The bug can be seen on level 29 if you stand on the left set of blocks that has a single gold in it. The enemies will get stuck on the second ladder which has a pole on the right side.The Apple II, Atari 8-bit, Commodore 64, and naturally the VIC-20 versions of the game have this bug since they were all made by Broderbund. But interestingly so does the Hudson Soft NES port. The later Macintosh version, which is otherwise a direct port of the Apple II code, fixed it. The IBM-PC version didn't have this bug because it was rewritten with the memory layout column-ordered instead of row-ordered. But then introduced a similar bug by subtracting when it should be adding.
(edit: I hadn't checked until just now but I'm amused to find that Lode Runner Legacy from 2017 preserved this bug in the classic game mode.)
In the case of level 29[1], the best position on the second ladder is to move to the top then use the horizontal pole to move left. That's what it will do when below the right-side pole. But when it gets above that it switches to thinking it should move down. Because the goal changes it gets stuck in the loop of moving up then moving down.
What you may be thinking of is when the "best" position is at the top of a ladder but no clear path left or right. It will climb to the top so the only way to go next is down. But after moving down immediately wants to go up again.
[1] https://strategywiki.org/wiki/File:Lode_Runner_level29.png
This is pretty cool.
https://www.geeksforgeeks.org/c/bresenhams-circle-drawing-al...
The secret is to draw 1 arc of a 45 degree angle and the reflect it (redraw it with different coordinates).