Contents

1. What is Callisto?
2. What happened to Lunar Helper?
3. What happened to the build scripts?
4. Where is the BPS patch to use the baserom?
5. How do I remove things from the baserom?
6. How do I hide the status bar?
7. Does this have Fast Retry?
8. Why are my block graphics not looking right?
9. Why are there weird tiles in the background?
10. Is the baserom SA-1 compatible?
11. Help, Callisto is reporting conflict(s)!
12. Help, I'm seeing a "Restore System Issue"!

What is Callisto?

It's a build tool that manages your project and does all the usual romhacking things through a simple user interface with a few actions. Callisto designed to run tools only when needed and avoid potential conflicts between resources, this way it insures your hack is cleanly constructed whenever you make changes. The big upside of using this is if something goes wrong then you can easily pinpoint what that was and remove or fix it so the next time you build it is not included in your project.

Read the Callisto documentation in the docs/tools/Callisto folder for more details information about how to use this tool.

What happened to Lunar Helper?

Lunar Helper has been succeeded by Callisto, which is detailed above. Callisto functions in much the same way as Lunar Helper–as a tool that handles all other tools, and builds and updates your project with simple commands–but it was rebuilt to have better cross-platform support and improved performance.

What happened to the build scripts?

In an effort to keep the baserom lean, we're going all-in on the Callisto build tool. The build batch files, while useful, were also a bit of maintainance burden and didn't work for some people.

Where is the BPS patch to use the baserom?

To get people familiar with the build process of the baserom we've opted to not include the BPS patch to create a ready-to-use baserom. The very simple initialization steps will create a clean slate to get started on a project.

If you are in need of a BPS file, Callisto can create one with the "Package" action, or from the button on the included User Toolbar.

How do I remove things from the baserom?

Callisto makes it easy to remove items from the baserom without a problem as it re-builds your ROM from scratch avoiding resource conflicts. See the Baserom Basics page for more details on that.

How do I hide the status bar?

If you just want to disable it in a single level, this baserom comes with several insertable custom objects to toggle features per-level. including one to hide the status bar. Check out the UberASM Objects documentation for details.

If you would like to disable it hack-wide, there is a method for that as well:

• Open "GM12.asm" from the tools/uberasmtool/gamemode folder and you'll see the following.

  init:
      jsl retry_level_init_2_init
      jsl uberasm_objects_init
      ;jsl toggle_statusbar_init
      rtl
  

  .
• Remove the semi-colon in front of jsl toggle_statusbar_init and save the file.
• Run "Update" in Callisto to insert the UberASM changes in your project.

Does this have Fast Retry?

Yes! By default the baserom is configured to use the vanilla death routine but you can enable retry in a level using a custom object. The UberASM Objects page has a section for the retry system with details.

For hack-wide changes to the Retry System you can edit its global configuration files in tools/uberasmtool/retry_config.

• settings.asm – Change the global settings for the retry system.
• tables.asm – Several options tables for changing per-level settings.
• sprite_status_bar_tables.asm – More configuration tables for displaying the sprite status bar items.

After making changes to any of the above, run "Update" in Callisto to insert the UberASM changes in your project.

Why are my block graphics not looking right?

Many of the custom global block in the baserom use ExGraphics, loading E17 into the FG2 slot in the Super GFX Bypass dialog will make the blocks appear as they are intended to.

Why are there garbage tiles in the background?

If you're using a background resource that uses slot BG3 you may notice some of the tiles from the baserom's ExAnimations in its tilemap, this is because the addresses at the end of that slot are being used as the destinations for those animations. To stop this from happening you can disable global animations in that level from the menu: "Level → Edit Animation Settings" and uncheck "Enable Lunar Magic's global animations".

Is the baserom SA-1 compatible?

Yes! The baserom's resources are all compatible with SA-1, but the baserom itself is configured to be FastROM by default. However to use SA-1 it only takes a couple steps to switch over to it:

In the buildtool folder, open the "resources.toml" file and look for the initial_patch lines, something like the following.

# Fastrom initial patch
initial_patch = "resources/initial_patches/fastrom.bps"

# Uncomment the line below if you would like to use SA-1.
# and comment out the one above
#initial_patch = "resources/initial_patches/sa1.bps"

To change which initial patch is used, comment out (i.e. move the "#") the relevant initial_patch line, and "Rebuild" your project in Callisto to make the change.

You will have to check if any additional resources that you add are SA-1 compatible when doing this.

Help, Callisto is reporting conflict(s)!

If you're worrying about this, it's likely because you've ran a Callisto action and are seeing something scary like the following:

Caching modules
2 conflict(s) logged to C:\path\project\buildtool\conflicts.txt
Moving temporary files to final output

One of the features of the Callisto tool is to detect when two or more resources are modifying the same parts of the ROM. This is to help you address resource conflicts by showing you which bytes are in conflict and compare them to the original ROM bytes.

Unfortunately, some of the tools in the baserom are writing to the same bytes so there are some unavoidable conflicts occuring. But not to worry as they seem to have no adverse affect.

However, if you are seeing more than those 2 known conflicts, something else may be at issue in your project.

Lunar Magic Restore System Issue

If you have never used Lunar Magic before, it automatically tries to set up its built-in restore system so you don't lose edits and can recover from any problems that occur on your ROM. When setting up the baserom, you may therefore encounter an error like the following.

The restore system cannot locate a copy of the original unmodified ROM with header, which is required for an operation about to be performed. Would you like to browse for a copy of this file now? (Y/N)

If you do see this and a File Chooser window appears, simply browse for a clean, headered copy of your Super Mario World ROM and open it so Lunar Magic can be satisfied.

Additionally, newer versions of Lunar Magic (3.40+) have changed how the restore system works by keeping the location of a known clean ROM in the Windows registry so if you haven't yet used a newer version of Lunar Magic you may also see this message. You can resolve it by opening Lunar Magic outside of the baserom project and following its prompt to find a clean ROM.

You can confirm it's set up by opening Windows' Registry Editor, browsing to HKEY_CURRENT_USER\Software\LunarianConcepts\LunarMagic\Settings you can find Lunar Magic's stored settings, and checking for the "OrigROM0" key.