• Welcome to Final Fantasy Hacktics. Please login or sign up.
 

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.

Topics - BigManStan

1
PSX FFT Hacking / Status Effect Text
April 19, 2016, 08:06:18 pm
Hi all,

I was watching some Jot5 playthrough videos and saw a few neat things, such as the 'Defending' text when a character goes into Defend status, as well as new 'Doom' text instead of Death Sentence.

I was interested in implementing my own new status in place of Wall with status text to display.  I was wondering if any of you could point me in the correct direction for making this display work.  It looks like the text is stored in FRAME.BIN...but is there any area in the code responsible for loading particular slices out of FRAME.BIN?  Did you Jot5 devs need to free up space in FRAME.BIN or is there unused areas in there that one could store new text?
2
Hi,

I was interested in adding a 3rd palette to the Demon sprite.  FFTEVGRP only lets me edit the first 2 palettes of the Demon sprite though- is it possible to alter the 3rd if it is greyed out?

Note I have used Shishi to add the 3rd palette and make it work properly in battle - I am trying to fix up the formation and menu screens.
3
PSX FFT Hacking / ASM Questions
March 07, 2016, 08:37:06 pm
Hi all,

New to FFT hacking and hacking in general.  This is my first foray into assembly language coding and I had a few questions on how stuff is done.


1)  I want to create a new routine in free space that is called from existing code.  In order to do that I need to use 2 instructions I assume, a jump and delay slot.  Assuming this is correct, what is done with the instructions that are overwritten by the jump/delay? 

I was studying Xifanie's Weapon Strike fix v1 as an example, and it looked like the 2 existing instructions that were stomped (saving $31 to stack) were tacked on to the end of the Weapon Strike routine before jumping back to the original code.  I was wondering if this is a general solution that can be used.


2)  Temporary registers:  If I call a routine from my code that is in the middle of an existing routine in the original code, and the original code is using the temporary registers (4-7 I think) do I need my routine to handle saving the temporary registers?  I was reading some assembly stuff and it says that saving temporaries is the caller's responsibility, not the callee's but in this situation I would need to overwrite even more existing code lines to do this.  I was wondering how this works?  Does my code need to save them (seems bad) or do I need to overwrite more lines from the existing code to do this?

And please let me know if I am way off base with these questions, or if I am lacking some fundamental knowledge.  I am very new to assembly and hacking so there may be some holes in my knowledge that I am not aware of.

Thanks!