finiteCraft

Here, have my proxy code @Pixelz22
— @quantumbagel

Why thank you, kind sir
— @Pixelz22

What's this?

This code is meant to be a conglomerate of all tools you could think of needing for mastering Neal Agarwal's Infinite Craft (https://neal.fun/infinite-craft). Up until now, these tools have been scattered across various repos and profiles, so we finally decided to bring them all together into one omniscient entity.

If you find this code interesting, we would love it if you would follow finiteCraft and star our repo! Your support is appreciated :D

The benefits of our system:

• a smart auto-rescheduling multi-threaded scraper to search for recipes and elements
• Max scraper speed achieved (so far): 115 crafts/second
• a constantly growing database easily accessible through the website
• a tree searcher that finds the most optimal way to craft any element, using the least number of elements and crafting steps
• No queue.Queue() lol
• Loading your own progress on infinite craft into the tree searcher
• Plain Awesome.

About the Developers

− @Pixelz22:
The original developer of this project. The work for this started on his own repo back when this was just a small personal project. Pretty soon he challenged the other developer, a good friend of his, to work on this project, which is where it really started to kick off. Finally, we discovered that there was another group out of Waterloo working on a nearly identical project. That's when this became a war.

− @quantumbagel:
Pixelz might have been the original developer, but Quantum kicked it into high gear. He has pioneered the scraping side of this project, creating the best scraper for InfiniteCraft currently out there. He single-handedly built the proxy scraper and rescheduling system from the ground up to get around InfiniteCraft's rate limiter. He's given it multi-threading, interfacing with MongoDB, and so much more. He has, without a doubt, hard-carried this project.

How to install finiteCraft

First, install docker.

Then, open the terminal and run this oneliner: (You will need to enter your password)

macOS/Linux: git clone https://github.com/finitecraft/finitecraft.git && cd finitecraft && sudo docker compose build && sudo docker compose up -d

Windows: You will need to install git for windows before you can run this snippet IN GIT BASH: git clone https://github.com/finitecraft/finitecraft.git && cd finitecraft && sudo docker compose build && sudo docker compose up -d

If you have any trouble with this, please open an issue :)

TODO LIST:

• Autocrafter (quantumbagel)

  • Proxy Scraper
    • Searches multiple proxy sources
  • Proxy management
    • Keep track of which proxies are successful and which aren't
    • automatically cycles through proxies that are unreliable
    • reschedules proxies that have been temp-blocked by neal.fun to be used later
  • Multi-threaded Workers searching for crafting recipes
    • Probes InfiniteCraft through sessioned GET requests
    • Sends packets of multiple requests at once to make up for slow proxies
  • Storage of elements and recipe info
    • Stores element info in a map from numerical key to element info.
      Should store element's
      • Name
      • Emoji
      • Depth
      • Whether it was discovered by the bot or not
      • list of recipes that this element is used in, formatted with the other ingredient and result.
    • Store recipes in map
      • Maps from element key to a list of all recipes that make that element, each stored as a tuple of the two ingredient keys
  • API for accessing information from the repo
    • Interfaces with chunking
    • User can get element info
    • User can get recipe info
  • Docker container
  • Support for not-always-online MongoDB
  • optimized generation algorithm

• Arborist (Pixelz22)

  • Basic tree generation
  • Naive search function
  • Basic pruning based on breadcrumb count
  • Pulls recipes using Autocrafter API
  • Recipe scoring function
    • Prioritize recipes that were part of other smallest trees
    • Uses max depth of the ingredients
    • Try prioritizing recipes that make use of already crafted elements - [ ] Come up with other ideas
  • Order recipes during search using scoring function
  • Timeout option to cancel search early
  • Research other means of optimization

• Website Frontend (quantumbagel)

  • Scrollable list of elements
  • Search bar for elements
  • Element display:
    • All recipes that result in that element
    • All recipes that use that element
    • A basic crafting tree
    • Option for generating a more optimal tree with a search timeout
  • Ability to load InfiniteCraft save data from user's cookies
    • Option to use this save data to affect tree generation
    • Maybe an option to show the next crafts available to the user?
  • Links to github profiles and repos, because who doesn't like a little shameless self promotion?

• WebSocket Server (quantumbagel)

  • Implement basic modular opcode server
  • Opcodes:
    • Display Opcode range (offset, length, sort): return emoji, first discovery, depth
    • Display Opcode specific (element): return emoji, first discovery, depth
    • Tree Opcode specific (element): return tree of element with id and emoji for each step
    • Heartbeat opcode: keep alive
    • Stat opcode: get stats for DB
    • Uses opcode range (offset, length, sort, element): get uses for element
    • Included in opcode range (offset, length, sort, element): get things the element is the result of
  • Sorting modes (for now):
    • Depth
    • Name

• Tyler