A question about the <D> delay command - Printable Version +- FF6 Hacking (https://www.ff6hacking.com/forums) +-- Forum: Discussion Forums (https://www.ff6hacking.com/forums/forum-5.html) +--- Forum: Magitek Research Facility (https://www.ff6hacking.com/forums/forum-9.html) +--- Thread: A question about the <D> delay command (/thread-2228.html)

A question about the <D> delay command - vince94 - 06-26-2013 I've noticed that, while editing text in FF3USME, the game sometimes cuts off half of the letters that come before a <D> command. This isn't usually noticable, since every <D> command in the unedited script has a space in front of it. Is this my emulator being strange, or is it an actual bug in the game? Here's an example of an elipsis being cut off in this way. EDIT: now using [img] tags. RE: A question about the <D> delay command - B-Run - 06-26-2013 Please use img tags instead of attaching. RE: A question about the <D> delay command - BTB - 06-26-2013 Always put a space before the <D> and you'll be all right. RE: A question about the <D> delay command - SSJ Rick - 06-26-2013 u 2 saved me the trouble thanks lol RE: A question about the <D> delay command - vince94 - 06-27-2013 Through a quick experiment, I found out why it sometimes happens and sometimes doesn't. The odd letters are good, and the even letters will always be cut off. Do you think it would be possible for someone to go into the ASM relating to how the text is printed, and fix this? I don't have any experience with that kind of thing, but it should be possible, and I know that several other bugfixes for the game exist. EDIT: Never mind, I came up with my own solution! I took one of the unused letters (the little tornado symbol) and edited the width in FF3USME's GFX editor to be 0 pixels long. Then I just type that in before every <D> command, and boom! No cutoff. RE: A question about the <D> delay command - BTB - 06-27-2013 It's not that simple. You might notice that the space used in the dialogue bank is not byte for byte. This is because, to save space, the text as printed is stored in two-character "chunks" (for lack of a better term). Any odd behavior of the text as printed is likely related to that. Again, the point is moot since any problems with delay tags can be easily resolved by using them <D>like so.