Some final code requests (and screenshots) - 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: Some final code requests (and screenshots) (/thread-3722.html) |
RE: Some final code requests (and screenshots) - Lightning - 05-12-2019 (05-11-2019, 07:58 PM)Subtraction Wrote:(05-11-2019, 04:17 PM)madsiur Wrote: Well in that case, use a debugger and set a breakpoint at C2/566E to see if the code is executed when you use step mine. Ahh, you are correct about the code being run at the start of the battle. I actually did modify the correct code, because I simply searched for the code you gave me rather than look for the address (I prefer doing it that way unless I can't find it in a search). The really strange thing here is that the MP usage for Step Mine is correct in-battle (54), but when I go through the menu and look at Step mine, it still says 108... This is why I was confused, and I don't know why the MP usage of Step Mine in the menu is not updating! RE: Some final code requests (and screenshots) - Subtraction - 05-12-2019 (05-12-2019, 01:09 AM)Lightning Wrote: The really strange thing here is that the MP usage for Step Mine is correct in-battle (54), but when I go through the menu and look at Step mine, it still says 108... This is why I was confused, and I don't know why the MP usage of Step Mine in the menu is not updating! Ah, that explains it then. I wasn't even thinking about the menu. To make it show correctly in the menu, you have to change a different bit of code. Code: Fork: Step Mine RE: Some final code requests (and screenshots) - madsiur - 05-12-2019 And to be clear, to halve the MP cost in menu and just retain Hours as MP cost, NOP the ASL A at $C35122 and $C35125 to $C3512D. RE: Some final code requests (and screenshots) - Lightning - 05-13-2019 I think that did the trick guys, thanks! RE: Some final code requests (and screenshots) - Lightning - 05-19-2019 Is there a way to have a weapon randomly cast something else other than basic magic? In FF3USME, it only lets you select magic (other than the specific wind slash effect in the drop down menu). I would like to have something else casted randomly, like sand storm or Aero. Can this be done merely by hacking a byte somewhere, or is there more to it? RE: Some final code requests (and screenshots) - madsiur - 05-20-2019 (05-19-2019, 10:03 PM)Lightning Wrote: Is there a way to have a weapon randomly cast something else other than basic magic? In FF3USME, it only lets you select magic (other than the specific wind slash effect in the drop down menu). I would like to have something else casted randomly, like sand storm or Aero. Can this be done merely by hacking a byte somewhere, or is there more to it? It only allow 64 choice; player spells and a few Espers spells. The highest two bits are used for something else so you can't have 256 choices of spells or attacks. If you want a different range of available spells, you could add a ADC #$XX in the code below. If you add $60, you would have access to spells $60 to $9F. Another thing you could do is add exceptions, like if the spell ID is X or Y, load Aero or Sandstorm instead. Code: C2/10F4: BF 12 50 D8 LDA $D85012,X (random weapon spellcast) RE: Some final code requests (and screenshots) - Subtraction - 05-21-2019 (05-19-2019, 10:03 PM)Lightning Wrote: Is there a way to have a weapon randomly cast something else other than basic magic? In FF3USME, it only lets you select magic (other than the specific wind slash effect in the drop down menu). I would like to have something else casted randomly, like sand storm or Aero. Can this be done merely by hacking a byte somewhere, or is there more to it? I've actually made a patch for this: https://www.ff6hacking.com/forums/thread-3754.html It's a little awkward to work with in FF3usME, though. The patch makes the game use the two ?s below Swdtech in the properties byte for "randomly cast" and "destroy if used". Then the "randomly cast" and "destroy if used" checkboxes set the top two bits of the break/proc spell. So, for example, if you wanted to make an item break for Aero (spell 0x8f), you have to select the spell Flare (0x0f) and then check the "destroy if used" checkbox to add 0x80 to that. To use the patch, you would also have to go through all of the items in FF3usME and manually move any checks in those boxes to the ?s in the properties byte. Oh, also, if you try to make a weapon proc for a Blitz, Swdtech, Bio Blast, Flash, Chocobop, H-bomb, or 7-Flush, it'll not use the correct animation and in some cases softlock. It's fine to make items break for those though. RE: Some final code requests (and screenshots) - Lightning - 05-21-2019 (05-21-2019, 05:14 AM)Subtraction Wrote:(05-19-2019, 10:03 PM)Lightning Wrote: Is there a way to have a weapon randomly cast something else other than basic magic? In FF3USME, it only lets you select magic (other than the specific wind slash effect in the drop down menu). I would like to have something else casted randomly, like sand storm or Aero. Can this be done merely by hacking a byte somewhere, or is there more to it? By the way, when I compile the code, it says line 16: invalid opcode or command [BMI $274A]". Is this something I should be concerned about? The patch seems to work fine, but I don't want any bugs... RE: Some final code requests (and screenshots) - Subtraction - 05-25-2019 (05-21-2019, 04:45 PM)Lightning Wrote: By the way, when I compile the code, it says line 16: invalid opcode or command [BMI $274A]".Weird, I thought I fixed that. Maybe I put up an old version. Just change this bit Code: org $C22743 RE: Some final code requests (and screenshots) - Lightning - 05-25-2019 (05-25-2019, 06:14 PM)Subtraction Wrote:(05-21-2019, 04:45 PM)Lightning Wrote: By the way, when I compile the code, it says line 16: invalid opcode or command [BMI $274A]".Weird, I thought I fixed that. Maybe I put up an old version. Just change this bit So I am just curious, what does this line do? I have been using your old code for days now without any issues. Do I really need to revert back to apply this one line? I already created an .ips patch with some of my changes, after all. |