| Name: | BTD6_maker's YI Text Editor (1.13) |
| Author: | BTD6_maker |
| Added: | |
| Version History: | View |
| Operating System: | Windows, Mac OS X, Linux |
| Platforms: | SNES |
| Games: | YI |
| Source Available: | Yes |
| Featured: | No |
| Website: | None |
| Description: | This is a YI text editor written in Python. The advantage this has over YIPES is that while YIPES may occasionally overwrite important data, this never does. It supports all special characters as well as symbols (such as the Yoshi symbol). For more information regarding these, see chara.txt. This requires a Yoshi's Island (V1.0) (U).smc ROM. It now works with headered or headerless ROMS. Python 3 is required in order to run this. Version 1.13 Made it more efficient when dealing with very large files (to fix an issue RPG Hacker noticed) Removed Advanced mode and merged its features with basic mode (as some advanced features wouldn't work properly in basic mode but Advanced mode exported all special characters as hex automatically) Version 1.12 Exporting can now export the individual digits of the lives counter. Added the ability to make messages start on the second line in Advanced mode. Added the ability to import and export changes in text size. Version 1.11 Added Advanced mode, which exports special characters directly as hex. Fixed issue where single-line level names malfunction. Version 1.1 Added the ability to import and export level names as well as just messages. Version 1.02 Messages are now exported and imported in order, which may fix some free space issues. Improved error handling. Version 1.01 Large pictures now display properly. Added support for headerless ROMs. Exporting can now export individual hex characters (for example, part of a larger symbol used separately, such as if you only want the left half of the A button) Version 1.0 Allows both exporting and importing text. Fixes issues such as full stops and commas being duplicated as well as the lives counter not displaying. Known bugs: Large pictures (such as those in 1-1) do not show properly. |
| Tags: | editor python smw2 text |
| Comments: | 9 (jump to comments) |
| Rating: |
Download
8.50 KiB | 838 downloads
Comments (9)
I have Python 3 installed and assigned to .py files, I have a 1.0 (U) ROM (double-checked through an emulator), everything is in the same folder and I'm doing it by copying cmd.exe on the folder I'm doing it with.
Yet, the only answer I get is "There was an error in exporting the text.", with no further specifications.
I've tried deactivating my antivirus, moving the folder to various locations of my PC and even naming the ROM "romname.smc" but the result is always the same. What could be happening? I hope you can help me solve it.
EDIT: Okay, so I've updated Python to the latest version and now the message I get is:
Traceback (most recent call last):
File "C:\Users\andre\Yoshi's Island\texteditor.py", line 508, in <module>
rom = open_rom(sys.argv[1])
~~~~~~~~^^^
IndexError: list index out of range
I'm sorry, I'm really bad at coding, but why is this happening all of a sudden?
File "texteditor.py", line 508, in < module> rom = open_rom(sys.argv[1]) IndexError: list index out of rangeIt appears that you didn't specify the ROM. Did you type "texteditor.py romname.smc export" or something similar? If you just type "texteditor.py" that will happen, since you haven't specified the ROM name.
I did. If it helps, my rom is an .sfc file and not an .smc file (I also tried typing out the file name with an smc extension instead but got the same result). Not sure if there's a compatibility issue there
File "texteditor.py", line 508, in < module> rom = open_rom(sys.argv[1]) IndexError: list index out of rangeIt appears that you didn't specify the ROM. Did you type "texteditor.py romname.smc export" or something similar? If you just type "texteditor.py" that will happen, since you haven't specified the ROM name.
File "texteditor.py", line 508, in < module> rom = open_rom(sys.argv[1]) IndexError: list index out of rangeThough being serious, of course this is just a rather barebones script. You don't have any text preview, which can make it difficult to know what your text will end up looking, but it does what it's supposed to do, and that's what counts.
Pro-tip:
In the place where the script does
print("There is not enough freespace in the ROM for all messages")I recommend also putting an error return value or something like that. Otherwise, when you call this script from a bat file or another tool, you have no way of knowing whether the execution succeeded or not.
just wait until level names support