FAQ & Troubleshooting - besteon/Ironmon-Tracker GitHub Wiki

Contents

Common questions and responses

"Will the tracker show my Pokémon's EVs/IVs"

  • No, that data is not available to the player in-game so the tracker will not reveal it.

"How do I separate the tracker and game screens?"

  • It is not possible to separate the tracker from the Bizhawk window.
  • If you have seen separated screens on Ironmon streams, they will have separated them via multiple sources in OBS/similar.
  • To set this up, see the "Separating the Screens" section in our Streamer Setup Tips page

Common errors and solutions

Folder/Permission Issues

Sometimes people have issues where the tracker fails to load files correctly (either failing to load entirely or causing huge lag on the emulator) or is unable to write files such as the RandomizerErrorLog.txt

This is often caused by one of the following:

  • The tracker still being in a ZIP file (you need to extract it first)
  • The tracker being stored in a folder where permission issues block the tracker from accessing its files, for example:
    • In a OneDrive (or similar cloud storage) folder
      • Note that your "Desktop" or "Documents" folders might actually be OneDrive folders
    • Directly on the system drive (the C drive)
    • In Program Files
    • In a folder you created directly on the C drive / in your Users folder / etc (where Windows assigns strict permissions by default)
  • Special/non-english characters being present in any of the folders the tracker is in
    • e.g. C:\Users\user\Pokémon\Ironmon Tracker won't work because of the é in Pokémon

If you have any issues like this, move the tracker folder to another folder if yours is currently in one of the mentioned troublesome locations and/or remove any special characters in any folders containing the tracker folder

"Nothing happens and no error messages or output is shown in the Lua Console"

image

Cause:

  • The Ironmon-Tracker.lua script was erased or overwritten, this often occurs when clicking the NEW button instead of OPEN.
  • One way to confirm this is the case by checking the filesize of the Ironmon-Tracker.lua file. If it is 0KB or 1KB then it's possibly been overwritten.

    image

    • NOTE: the NDS tracker's Ironmon-Tracker.lua file normally shows up as 1KB. If you're having this issue with the NDS tracker then see the other confirmation method below.
  • Another way to confirm is if you open the Ironmon-Tracker.lua file in a text editor (e.g. notepad), if it only contains the following code block then it has been overwritten by a NEW script. 
    while true do
    emu.frameadvance();
end

Fix:

  • Download the Tracker again from the release and replace your existing files.
    • Alternatively, if you have a release that came with the UpdateOrInstall.lua file, run this file in the lua console and follow the prompts to re-install the tracker.
  • Be sure to carefully click on Script -> Open Script in the Lua Console to load the tracker.

"Can't have lua running in two host threads at a time!"

Cause:

  • Having the "Autoload Last Slot" toggle turned on in File -> Load State when using the New Runs feature and loading seeds that have savestates.
  • This toggle option interrupts the tracker's New Runs process.

Fix:

  • Disable the "Autoload Last Slot" toggle.
  • You can instead bind a hotkey to load savestates in Config -> Hotkeys -> Save States, and press this hotkey after loading the next seed to load the savestate.

"My old in-game save is showing on newly generated seeds"

Cause:

  • Emulators usually match saves (in-game and savestates) to ROMs by filename.
  • Since the tracker re-uses the same filename for its auto-generated seeds, in-game saves and savestates will carry over since the emulator "thinks" it's the same ROM.

Fix:

  • Press Up + B + Select on the title screen of the game, you should see a menu like below to delete the in-game save.

    Testing Maps 2022-09-14 12 17 12

  • If you instead see a "Berry Program Update" menu then that means the game only registered B + Select (the combination to open this menu), to get the correct menu try holding Up first and then press B + Select while holding Up

    Berry_Program_Update_FRLG

  • If you don't want to have to keep doing this, you could use savestates to save progress mid-run instead, which would still carry between seeds but not show on the main menu / be as intrusive.

"I loaded a save to continue my run and my Pokémon's stats/ability are different"

Cause:

  • This usually happens when you load a save/savestate on a different ROM (or different random seed) than the one you created the save/savestate on. The pokémon carries through in the save/savestate, but the pokémon's data in the ROM is now different than before.
    • This often happens if you mistakenly use the tracker's New Runs feature to try and "reload" a run to continue.

Fix:

  • The only proper fix is to load the original ROM that the save/savestate was made on, if it still exists.
    • If the save/savestate does not appear for you then you have not loaded the correct ROM.
    • If the stats change drastically on levelling up then it is also not the correct ROM.
  • If you're using the tracker to generate new seeds:

    • Note the name of the ROM that the tracker creates for you. It's based on the settings file you choose so will be named something like FRLG_Kaizo_AutoRandomized.gba. If you're on bizhawk you'll see the ROM name in the window title (with underscores replaced by spaces):

      image

      If you're on mGBA then it won't show the ROM name by default. You can toggle a setting to show the ROM name in the window title however the window title will not update for tracker-generated ROMs due to this bug.

    • DO NOT press the New Runs button combo unless you mean to start a new run. The tracker overwrites the current seed with the newly generated one.

    • Instead use File -> Open ROM (Bizhawk) / File -> Load ROM (mGBA) and navigate to your tracker folder to find your AutoRandomized ROM.

    • Alternatively you can load it through File -> Recent ROM (Bizhawk) / File -> Recent (mGBA), as it should be at/near the top of the list.

  • If you accidentally pressed the New Runs combo and overwrote your AutoRandomized ROM:
    • A backup of the previous ROM does get made in the tracker folder. Usually it'll be named something like FRLG_Kaizo_PreviousAttempt.gba.
    • Try loading this ROM and your save and see if it's your original run (verify by levelling up and seeing if the stat changes make sense).
    • You can also rename this file to the current FRLG_Kaizo_AutoRandomized.gba (or whatever it is for you) to make it match the save/savestate for loading.

New Run randomization errors

Meanings of common errors shown in the RandomizerErrorLog.txt file

"Invalid maximum heap size: -Xmx4608M"

Cause:

  • You don't have 64-bit offline Java installed.

Fix:

  • Download and install 64-bit offline Java from the official website.
  • If you currently have another version of Java installed you may want to uninstall it completely before installing 64-bit offline Java, in case they interfere with each other.

"java.lang.UnsupportedOperationException: Cannot read settings from a newer version of the randomizer."

Cause:

  • The randomizer.jar file you have provided is an older version of the randomizer than what the chosen settings file is for.

Fix 1:

Fix 2:

  • Open your own randomizer version. Load up your ROM and the right randomization settings using e.g. a settings string from the Ironmon Discord.
  • Click on "Save Settings" to save a .rnqs settings file.
  • Select your new .rnqs file for the settings file option in the tracker's New Runs settings.