øA slickproductions.org /forum/index.php?PHPSESSID=5f0fck550j2m4m2fpbtkj2vkm1&action=profile;u=123;area=showposts;start=315 e:/My Web Sites/Slick Productions - FFIV Message Board/slickproductions.org/forum/index91c3-2.html slickproductions.org /forum/index.php?PHPSESSID=5f0fck550j2m4m2fpbtkj2vkm1&action=profile;area=showposts;u=123 e:/My Web Sites/Slick Productions - FFIV Message Board/slickproductions.org/forum/index91c3-2.html.z x òg^ ÿÿÿÿ ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÈ …¬ í¤ OK text/html ISO-8859-1 gzip (¾Ö í¤ ÿÿÿÿÿÿÿÿ Tue, 10 Mar 2020 20:17:43 GMT 0ó° °® 0® P® €§² ð® òg^ ÿÿÿÿÿÿÿÿòM í¤
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.
That's awesome!
I also had an idea for a spell routine I'd like to see (a couple actually ^_^):
Race-specific damage
Something like the "Harm"/"Dia" series from FF1. I was originally trying to achieve this by making a spell that healed all enemies; thus it doesn't hurt non-undeads but does hurt undeads. It just seems a little weird when a spell called "Harm" causes healing, especially if someone unfamiliar with the first game tries to cast it; they'd probably get super confused. Anyway it could be regular damage with a racial bonus, like attacks, or could only deal its damage to monsters of that race and miss on others (like Quake with fliers). Speaking of which...
Earth damage
Instead of the game looking for specific spell indexes, we could have a separate damage routine that causes damage only to non-flying enemies. Perhaps it could even be more generalized by looking at the element index ("damage all enemies that aren't weak to XX").
Heal status + some HP
There is a routine for damage + add status, why not heal HP + remove status? Something like Chakra from FF5.
Damage + extended byte status
Currently Sap/HP-Leak is the only "extended" status you can add with damage. For that matter it might be nice to have a routine that can add an extended status (or combination thereof?) based on the element/status parameter rather than having one routine for stop, one for reflect, one for count, etc.
That's all I got for now, just trying to brainstorm for ideas. I might have more later ^_^
I like it, but I do have a few questions, mostly just clarification points...
So the spells the characters learn as a result of using their specific jobs, do they always have them regardless of job thereafter?
That is, does Scholar Edward have access to Bard Edward's spells?
How is the battle counter affected by job changes? If I'm at 254 with DK Cecil and I morph into P Cecil, will P Cecil be one battle away from his next spell? If not, then will he be 255 battles aeway? Or is this what those 26 bytes of SRAM are for?
Since we're on it, are Paladin and Dark Knight two of Cecil's jobs?
Also - and maybe you've covered this in some previous post somewhere - are there enough Job IDs to handle three Jobs for every character?
What about Tellah? Does he have three Jobs? If so, are you planning on "pulling an Aeris" on the player, or will he be revivable? Or maybe FuSoYa will be Tellah part two (or four, or whatever)?
Actually that part came as a side-effect. The variable that told it how far down the list to look is the same one it's reading from the rom for the six-letter spell range. I haven't actually tried seeing whether adding monster spells to a player spell set will display correctly in the actual rom now, but if so that would be fantastic.
Ok so FF4kster has been updated with this functionality and has been uploaded.
HOWEVER, when you change the range it might mess with your spell names (though it also might not). Here's exactly what happens:
- FF4kster, upon loading the rom, reads the names according to what it thinks the ranges should be based on the data currently in the rom.
- You go into the features editor and change the end of "six-letter spells" to something else.
- FF4kster looks at the new index and does the following to the list of spell names it has already read into memory:
- All spell names before the new index get truncated to six letters if they were longer (e.g. "MegaNuke" would become "MegaNu")
- All spell names after the new index get padded out to eight letters with trailing spaces if they were shorter (e.g. "_Image" would become "_Image__")
- When it saves, it will put all the newly modified names back to back in memory, trusting that the ROM will deal with them correctly.
OK, I remembered you talking about the "enemy ran away" routine, but didn't really remember what it actually did. So party running away is still out there somewhere, then. Guess I'll put it on the list of stuff to find at some point.
So all of those blank spaces seem safe according to ff4.txt with the possible exception of 977F0, which includes the data yousei has listed as "triggered event data," which I assume is the details of trigger event IDs, something that is definitely editable and expandable using FF4kster, which makes it dangerous to use...
Yeah, what I'm theorizing here is that the "enemy ran away" routine might actually be the party running away routine.
The way I see it (and maybe I'm wrong, wouldn't be the first time) the party running away routine must be mixed in among the commands somewhere.
Surely you've seen yousei's document. I think we've discussed it before. If you download his FF4ed utility, it's packaged in with that. It'll be in its own subfolder called "documents" when you unzip the utility. I'm pretty sure the ROM map assumes v 1.0 (everything else yousei did specified 1.0) but the addresses are all close enough to give a broad overview of where most things are in ROM.
Wait - hang on. All this time when you were talking about "retreat," I assumed it was the thing that the soldier captain does after the three soldiers are defeated. Are you telling me that that's the same routine as when the party runs away?
No, you know the document. Yousei's document. Maybe it's called ff2.txt? Sorry if I made that more confusing. I haven't even had my computer on for the last week or so.
Wow, so this is a grand scale type thingy you've got going on!
The expanded spell routine space is what excites me the most personally, for sure, but something like this would really open up the platform for experienced hackers with good ideas to really play around...
Couple things come to mind immediately:
1) I was actually talking about whatever it is that makes the party run away, as in when you hold L and R... But is it possible that that is the actual use of what we've thus far referred to as the "Enemy Runs Away" routine? I'm not gonna get into actually doing stuff this evening, but tomorrow I might try setting a breakpoint to that routine and hold L and R to test that theory out...
2) be careful of those big empty spaces. Compare their locations with the ROM map in ffiv.txt. I had a brush with disaster recently by carelessly using some space in the 90000 block (I think). I was using some supposedly empty space after dialogue bank 3, and I was unaware of it. A long time later, I edited bank 3 in FF4kster and it almost destroyed my game. Took a long time to figure out what went wrong. Had do DL this utility called IPS Peek that analyzes a patch to tell you exactly which parts of ROM it affects, then compared each of those places between a ROM that was and was not patched with the recent changes. Took several hours to figure it all out, and that was only after I figured out that I'd be able to do this at all. Anyway, point is that I'm wary of big empty spaces now... Heh, I developed ROM agoraphobia. But as long as you know what is surrounding the free space you're using, you should be fine.
$03/E050 C9 3E CMP #$3E A:004F X:0000 Y:0000 P:eNvMxdizc - Is it Asura?
$03/E052 90 1A BCC $1A [$E06E] A:004F X:0000 Y:0000 P:envMxdizC - If less than Asura branch.
-----------------------------------------------------------------------------------------------------------------------
$03/E054 C9 3F CMP #$3F A:004F X:0000 Y:0000 P:envMxdizC - Is it Bahamut?
$03/E056 D0 04 BNE $04 [$E05C] A:004F X:0000 Y:0000 P:envMxdizC - If not Bahamut, branch.
-----------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------
$03/E05C A2 00 00 LDX #$0000 A:004F X:0000 Y:0000 P:envMxdizC - Load 0000 into X.
$03/E05F A9 02 LDA #$02 A:004F X:0000 Y:0000 P:envMxdiZC - Load 02 into A.
$03/E061 20 79 83 JSR $8379 [$03:8379] A:0002 X:0000 Y:0000 P:envMxdizC - Jump to Subroutine (RNG between 00-02 to get the random result for Asura)
$03/E064 48 PHA A:0001 X:0000 Y:0000 P:envMxdizc - - Push A onto Stack.
$03/E065 A9 F8 LDA #$F8 A:0001 X:0000 Y:0000 P:envMxdizc - Load F8 into A.
$03/E067 8D D4 26 STA $26D4 [$7E:26D4] A:00F8 X:0000 Y:0000 P:eNvMxdizc - Store A in Targeting (Target All Allies)
$03/E06A 68 PLA A:00F8 X:0000 Y:0000 P:eNvMxdizc - Pull A from Stack.
$03/E06B 18 CLC A:0001 X:0000 Y:0000 P:envMxdizc - Clear Carry Flag.
--------------------------------------------------------------------------------------------------------------
$03/E06C 69 3E ADC #$3E A:0001 X:0000 Y:0000 P:envMxdizc - Add 3E onto A (3E-40)
$03/E06E 38 SEC A:003F X:0000 Y:0000 P:envMxdizc - Set Carry Flag
$03/E06F E9 31 SBC #$31 A:003F X:0000 Y:0000 P:envMxdizC - Subtract 31 from A.
$03/E071 18 CLC A:000E X:0000 Y:0000 P:envMxdizC - Clear Carry Flag.
$03/E072 69 4D ADC #$4D A:000E X:0000 Y:0000 P:envMxdizc - Add 4D onto A.
$03/E074 8D D2 26 STA $26D2 [$7E:26D2] A:005B X:0000 Y:0000 P:envMxdizc - That is the Random Asura (or nomal summon)Action to Perform.
This is a really cool Idea. I'm a little hazy (maybe you went into more detail somewhere else?) On the details of exactly which limits you've overcome to the original set of commands.Welcome back Chillyfeez!
As I see it, the limits are:
1) bank 03 space (not too difficult to overcome)
2) command name space (pretty sure command names are wedged into a bank of other text data, like character default names &c. This could probably be moved pretty easily, as long as you find all of the pointers into command name data and adjust them appropriately)
3) command ID numbers - probably the toughest to overcome because of how the game regularly adds C0 to the ID for various functions, meaning there can only be a maximum of 3F commands, ever, and we want to make sure to not overwrite things like Change, Parry, Show (well, except in hacks that get rid of Hide), Off, Land (the second half off Jump), the ending portion of Spirit Wave, Running away (I don't think we've ever explored this, but it must be a command), whatever else I might be forgetting...
What about using the shop system somehow for unlocking the statues through purchase?