Lazy Shell is a third party .NET application written in the C# programming language which is capable of editing a wide range of elements within the Super Mario RPG (US) ROM image file. These elements include allies, battle animations, attacks, spells, sound effects, music, battlefields, dialogues, fonts, effects, events, formations, items, shops, level/location maps, the main title, menus, the mine-cart maps, monsters, sprites, world maps, and more. In addition, it also includes a help database and a project manager to help organize a full hack project.
You can view screenshots of the editor and watch videos of hacks made with LAZY SHELL from the editor's home page
Notes on latest/recent release(s)...
v3.19.0 is primarily a bugfix; it's release is exactly 5 years to date from Lazy Shell's initial release in January 2009. v3.18.0 has additional undo/redo support for battlefields, world maps, and battle scripts. An NPC packet editor has been added, and the drawing selection box has a new, nicer look.
*Now allows user to load any ROM file, with a warning
*Restore elements node "Main Title" renamed to "Intro"
*Selection marching ant timers no longer run infinitely in background
*Dialogue: palette for disabled menu items (dark blue) now editable
*Sometimes crashed when creating selection because of dash offset
*Audio: score viewer shouldn't be enabled if sound effect loaded
*Audio: only set percussive pitch if reading notes when MML importing
*Dialogue: not reading pointer when compressing/saving menu palettes
*History: crash if using mouse/keyboard at same time in listboxes
*Levels: crash if drag solidity tile & solid mods enabled but no mods
*Levels: deleting selection in solid mod not saving to undo history
*Levels: rapidly ctrl+clicking tiles to select in tileset creates lag
*Levels: crash when toggle layers, try to redraw tilemod maps b/c null
*Mini-games: crash if edit tilemap b/c reading from null levels form
*Monsters: ignoring user-set target in "If target affected" commands
*Monsters: ignoring user-set "Do Nothing" for "Do 1 of 3" commands
*Sprites: crash if moving through sequences while clicking sometimes
*Audio: can now adjust sample rel freq by half/full pitch amount
*Image drawing code now safer and much faster
*Audio: loop start value now divided by 9 for greater precision
*Never removed header after save b/c romLength not being updated
*Some problems with new history logging format, dragging objects
*Nearly all editors asking to save during close even after saving
*Audio: score vscrollbar not staying put when writing music
*Audio: crash if try to open hex editor b/c passing HiRom offset
If you find or encounter a bug...
As is the case with releases containing several additions, there is always the possibility of new bugs surfacing. As usual, any bugs encountered please report them here. The recently added custom exception/error message box makes this easier and less trivial. If you encounter an error read the brief instructions in the message and make a new post here. You can click "ignore error" if you don't want to close and lose your work. Always remember to frequently save your work. Make back-ups using the options in the settings. Use the notes feature to keep track of changes and keep organized, etc.
If the editor crashes, copy/paste the contents in the crash window here, explaining what you did before the crash occurred.
For corrupted data issues such as garbled/glitched graphics, text, etc. that you encounter after modifying the ROM, please answer each of the following FOUR questions:
1. What was the last thing you changed before you first encountered the problem?
2. Were you using a fresh ROM with OK checksum (see box at top of main window)?
3. If answer "no" to #2, what portions of the ROM did you modify before the problem? Is it a hack?
4. Do the problems appear in the *editor*, the *emulator*, or *both*?
For all other bugs encountered, such as failure of the editor to perform a task like saving or changing data, incorrectly modifying or displaying data, etc. just briefly explain what the problem is and what you're doing to cause it.
When I make changes in the Sprite editor, save states become messed up, and even when using a save game, some battle animations (such as Dodo and Smithy) are messed up. Also seem to be some event issues in the latter part of Smithy Factory.
Also, in the World Maps editor, if I try to change the assigned event #, it gives an unhandled exception.
Thanks for the bug report. I've fixed the World Maps problem, but I'll need you to be more specific on the first problem:
1. what exactly did you change in the sprites editor?
2. in what order did you make those changes?
3. provide as much detail as you can: the sprite #, the mold #, sequence #, whatever; it will make it much easier to locate and fix the problem
4. are you trying to edit a ROM that has been modified by an earlier version of Lazy Shell?
Just to let anyone know, I am paying attention to your reports and fixing the bugs as new ones are discovered. Remember, if the editor throws an exception or acts crazy, it's most likely an issue with the editor and not your fault.
There is nothing labelled "permutation" in the sprite editor; did you mean the mold image (ie. inside the sprite box)? I still haven't been able to reproduce the problems you've encountered.
If you could provide a screenshot of the sprite editor after all the changes you made to cause these problems (like you did w/the world map editor) it would be much easier for me to find the source of the problem.
Also, I recommend posting bug reports in this thread since I check that more often and that forum is more active and responsive to updates. Also, the latest updates for the editor changes are there.
It may be an issue with save states. If you've saved the sprites in Lazy Shell v3.x and load a save state in ZSNES, Snes9x or whatever and get garbage sprites, try walking into a house or another area. I had the same problem as you, but exited the area and everything was fine. Save state memory and modified sprite data don't agree very often.
I tried one error that I could make on the version I was using on the new one and it still occurs.
It occurs when I don't choose anything on the element list, then click on "add indez to element notes".