Oh no, IntCodes! (I'm starting to see a pattern here...)
After an easy decryption of an image file, we're back in our module and speeding through the solar system. Unfortunately, we seem to have picked up a distress beacon! What is it saying? We must update our IntCode interpreter to find out!
Part 1 seems simple enough: Add big number support and a new relative parameter addressing system.
And after whacking our heads against the wall on why relative mode wasn't working the way we thought it should for too long, Part 2 is "merely" the same as part 1, but potentially very slow. If you weren't careful, your solution might be running for a long time.
120635-5c140b9a- provided by Linda Thompson
If you were part of Ryan Palo's leaderboard last year, you're still a member of that!
If you want me to add your leaderboard code to this page, reply to one of these posts and/or send me a DM containing your code and any theming or notes you’d like me to add. (You can find your private leaderboard code on your "Private Leaderboard" page.)
I'll edit in any leaderboards that people want to post, along with any description for the kinds of people you want to have on it. (My leaderboard is being used as my office's leaderboard.) And if I get something wrong, please call me out or message me and I’ll fix it ASAP.
There's no limit to the number of leaderboards you can join, so there's no problem belonging to a "Beginner" and a language specific one if you want.
I'm planning on adding some statistics, but other than "what languages did we see yesterday" does anyone have any ideas?
- kotlin x 2
- python x 2
By applying a best-fit descending power trend-line to the 1 and 2 star columns on the stats page, my estimates predict:
1 star on day. 25: 6358 people
2 stars on day 25: 420 people. Nice
If you're still going, take heart in that you are in a rapidly dwindling pool of people.
Doing other questionable statistics gives me: 415/6248