Match History

MEGABONK MATCH HISTORY

Now you can check your previous runs.

Keep track of your runs

Match History adds a new button to the main menu, giving you a place to revisit your recent Megabonk runs. Browse your past matches, open a run’s details, and see how each run went.

Run details

• []Character and run date[/]

  []Kills, elite kills, and boss kills[/]

  []Gold earned, chests opened, and items picked up[/]

  []Total damage and a breakdown by damage source[/]

  []Estimated DPS and upgrade level for each damage source[/]

  []Weapon, item, tome, and passive loadout data for newly recorded runs[/]

  Damage-source icons are shown when the mod can match them to the game’s assets.

  Designed for easy browsing

  • []View detailed stats for individual matches[/]

    []Menu text supports multiple languages[/]

    []Your latest 100 runs are kept in the history[/]

    Compatibility

    Require MelonLoader. This release is built for MelonLoader.

    Save location

    Match data is stored locally at:

    Megabonk/UserData/MegabonkMatchHistory.json

    The file is not currently synced through Steam Cloud. Back it up if you plan to reinstall the game or move your installation.

    • []The history only applies to future runs; runs played before installing the mod are not recorded.[/]

      []The match history can be easily modified in the JSON file. For this reason, it is recommended not to use it as a basis for competition or comparison. (This may be changed in a future update)[/]

      ---

      Installation

      • []Install MelonLoader for Megabonk.[/]

        []Place

        MegabonkMatchHistory.dllin the game’s

        Modsfolder.[/]

        []Launch the game and select History from the main menu.[/]

        Bug Reports

        If you encounter a bug, please include:

        • []A short description of what happened and how to reproduce it[/]

          []Your Megabonk and MelonLoader versions[/]

          []Your MelonLoader

          Latest.log[/]

          []A screenshot, if it helps explain the issue[/]