Banner
Views: 737,272,594
Time:
18 users online: Classfan, ECS.98, file, Flamesofshadow, Fullcannon, GreenHammerBro, Jamie-Lee Brotheridge, LEcrOse, MarioFanGamer, Meirdent, Nicoke42, Pablo's Corner, ShUriK KiD, SSIIMMPPLLYY, Stiviboy, Super Maks 64, TheEvilKingBowser, Tob - Guests: 64 - Bots: 200Users: 38,784 (1,919 active)
Latest: Chaos Bass
Tip: Don't make Mario die after cutting the goal tape. Fake exits are not cool.Not logged in.
BTD6_maker's YI Text Editor (1.12) by BTD6_maker
Forum Index - Valley of Bowser - Moderation Questions - Tools - BTD6_maker's YI Text Editor (1.12) by BTD6_maker
Pages: « 1 »
File Name: BTD6_maker's YI Text Editor (1.12)
Submitted: by BTD6_maker
Obsoletes: BTD6_maker's YI Text Editor (1.11)
Authors: BTD6_maker
Operating System: Windows, Mac OS X, Linux
Platforms: SNES
Games: YI
Source Included: Yes
Featured: No
Website:
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.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.
Screenshots:
First of all, sorry for taking so long to moderate this. I know how annoying that is, especially when your stuff gets rejected in the end. #w{=(}
Secondly, I don't know if the reason for rejecting this is a warranted one, to me personally it's more of a minor issue, but then again it's still probably a bug and might be a bigger problem to people not provoking the error willingly, so I wanted to be on the safe side here. Anyways, it's something that I assume should be easily fixable, so if you want to resubmit the script, it shouldn't take you a long time to do so.

Based on the submission's description, the main benefit of this script seems to be that it doesn't overwrite any random data in the ROM when text data gets too long, so naturally one of the things I tested was to take a TextData file with a lot of text in it and try to insert it into the ROM. This is the file I tested, and upon trying to insert it, the script hung forever and never seemed to finish. I let it sit there for a couple of minutes, but it kept going and going, so something seems to not work quite correctly here and the script never seems to finish on files that get too large. Admittedly, the test file I'm using here is an extreme example and almost as big as a Yoshi's Island ROM itself, end users are not likely to use text data that big, but I think it's reasonable to assume that the same error might occur even when a user exceeds the maximum size just slightly, and in that case, I do think it's important to have the error output work correctly, since this situation could occur just naturally for users of the script and it would basically just stop working for them at that point without any information on what's wrong. Now it's very possible that the workload of this file just turned out to be too much for the script and that it didn't actually hang forever, but just took a very long time to finish. If that's the case, I'd still argue that something isn't quite working correctly there, because ~2 KB aren't a lot of data for a modern computer and it should still be able to work through such a file in at most a few seconds, even if it has to process the data in some way. Whatever the case, some error seems to not be handled quite correctly yet, so if you want to resubmit the script, I suggest taking a look at that and trying to insert my TextData file linked above, it should not hang for an extended amount of time.

A few more minor things to comment on (these aren't reasons for rejection, just some things you might want to know about).

First of all, you forgot to change the version number in the readme, it still says version 1.11.

Secondly, responding to your omment on the previous version of the script (which I only noticed recently):

Originally posted by BTD6_maker
The message seems to show for me when I call it from a batch file. I will add try statements, though, to try to catch any other errors.


I think you misunderstood what I was suggesting there. I wasn't saying that the error messages didn't show for me. They actually did. I was saying that error messages alone aren't a sufficient way of handling errors. Instead of doing something like this:

Code
print("There is not enough freespace in the ROM for all messages")


You might want to do something like this:

Code
print("There is not enough freespace in the ROM for all messages")
Sys.exit(-1)


(Note: not sure if this is how it's actually done in Python, but something along those lines).
The reason for this is that parsing an error message argueably takes a bit more effort than just using the exit code of a script. The exit code is something that can easily be checked from, for example, a BAT file. That's very useful. Parsing the text output from a script, on the other hand, can require a bit of effort, depending on what you're using (somewhat complex to do in C, for example).

--------------------
Feel free to visit my website/blog - it's updated rarely, but it looks pretty cool!
Pages: « 1 »
Forum Index - Valley of Bowser - Moderation Questions - Tools - BTD6_maker's YI Text Editor (1.12) by BTD6_maker

The purpose of this site is not to distribute copyrighted material, but to honor one of our favourite games.

Copyright © 2005 - 2019 - SMW Central
Legal Information - Privacy Policy - Link To Us


Total queries: 23

Menu

Follow Us On

  • Facebook
  • Twitter
  • YouTube

Affiliates

  • Talkhaus
  • SMBX Community
  • GTx0
  • Super Luigi Bros
  • ROMhacking.net
  • MFGG
  • Gaming Reinvented