Okay, I'm still a bit confused. I think what you're saying is that there is a single byte value that will print LAYBALL when used. Is this correct?

If so, when you say "pointer" in this case, are you referring to that single byte? If so, let's get away from using the word pointer and, instead, use something like "dictionary byte" or some such. Technically, it is a pointer, but not a pointer in the traditional sense the word is usually used in regards to ROM hacking. (There would be traditional pointers involved in regards to indicating to which word each byte corresponds.)

Anywayz, I guess if you've resolved it, it doesn't really matter now. It sounds like you did it in the same manner I would have, keep breaking shit until it starts working. If you do need any more help with it, however, you might try including a couple of screen shots, one of the hex editor and one of the actual game, so we can see exactly what you're talking about.

I guess you can call it an index or something else? The ROM uses some pointers that seem to have their own byte format (which I have not decoded) - they are a pointer within a text block that point to addtional text (weird) but do not follow the same pointer table...for now I am staying clear of them!

Yes there are also the "dictionary byte" pointers too, and in some cases the text doesn't even use pointers...not sure how to squeeze the text in at this time, perhaps I will have to use "Y" for yes and "N" for no. It's been a learning curve and a pain when you get into this non-standard bytes.

Sure I can and will post screen shots, I didn't want to sound insulting - look at this and everyone knows what it is...that type of BS that n00bs do  :laugh:

Tauwasser what is the differnce between an index and a pointer?

Thank you very much once again Tauwasser for that nice detailed explanation. Now that sums it up for me and I understand the difference between a pointer and index values (and how they work) very interesting!   I have indeed come across these values and if there is a standard in the way they work I do not know what it is, except the ones I have seen seem to point to a pointer table and not text blocks themselves.

It's easy for me to determine if it is a pointer or a value now, I am not going to go crazy w/ values as I can adjust my translation if needed...as long as it gets finished. I do have a problem w/ the current screen (hopefully I don't have to ask for help) as I can find the text blocks, edit them and they don't change on screen...the only thing I can think of is I am editing the wrong blocks until I do further research.

Thanks 

EDIT:
Well I have some screen shots and a patch for anyone who really cares about this, I am only happy as it's my first translation  It's not 100%, most KANJI has not been translated and some menus very well may use *compression* so I'll never get to those. It's far from perfect, it is a beta patch (mainly for testing).











Download the patch:
http://www.mediafire.com/?myjmymmxzuj

ROM: Ultra_Baseball_Jitsumeiban (SNES)
(part ENG beta 001).zip

Some good news is that the next game in the series (Super Ultra Baseball 2) the one that was mentioned in this thread: http://www.romhacking.net/forum/index.php/topic,4397.0.html uses basically the same table format and I have been able to start work on that game, which is quite different and uses a new engine. The current problem with that is the text can only be viewed at 1BPP and the bitplane images are not complete in a box (hard to explain w/o a screen shot) so editing the KANI is the only issue...text is easy since it contains the complete ROMAJI alpha.










I won't use Save States for that reason and this game is mostly menus so I am not dealing with in-depth platform or rpgs etc. I have just skipped over that section for the time being until I have to figure it out, hopefully I will. If you have any other ideas please let me know.

Thanks InVerse.