EDIT: I don't think my previous help would be any use to you. I think it only worked for me in the old Tactext; unless you're using the older one, of course. (Newest is .478)
July 06, 2025, 12:19:12 am
News:
Use of ePSXe before 2.0 is highly discouraged. Mednafen, RetroArch, and Duckstation are recommended for playing/testing, pSX is recommended for debugging.
Show posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages1
1
Help! / Re: FFTactext object reference not set to an instance of an object.
January 16, 2011, 12:35:38 pm2
Help! / Re: Another ASM question.
January 16, 2011, 07:20:55 am
Impressive, formerdeathcorps. Your work is always interesting. Thanks for the fix.
3
Help! / Re: FFTactext object reference not set to an instance of an object.
January 15, 2011, 05:17:13 pm
For descriptions, try to keep them below a width of 200~. Job, item and ability names should be 72~ or lower. Space is generally the biggest issue with FFTactext, so try to keep descriptions as brief as possible. I myself wouldn't use more than four lines per description; however, there are exceptions, just try to keep most of them at around 4~ lines. Sometimes it's buggy if your second and beyond lines are wider than the first line, so try to keep them at the same width or smaller. Using codes like {Ramza} in certain descriptions can cause problems, as well. These are most of the things that gave me problems whilst experimenting with FFTactext, and I think it's pretty much limited to these. I wish you the best of luck.
EDITED: Minor grammar errors.
EDITED: Minor grammar errors.
Pages1