Forum Replies Created
-
Posts
-
Quote:Also, I just got my first item drop but it was when I was retreating! Maybe add a check to see if the battle was really won?
Ha! That's funny. I'll look into it. :D
Also noticed a problem in the Duel code… I had Zhang Fei duel Dong Zhuo, and Dong Zhuo has death protection. Zhang Fei always seemed to kill him before. I haven't tracked down the issue yet.
EDIT: This is the instruction at which I'm hanging:
Code:1F:C95E:02 UNDEFINEDIt's a case of just going to the wrong place in the code… as it reads right in this manner:
Code:1F:C94D:9D 00 02 STA $0200,X @ $0201 = #$00
1F:C950:A5 19 LDA $0019 = #$E4
1F:C952:9D 01 02 STA $0201,X @ $0202 = #$00
1F:C955:A5 1A LDA $001A = #$42
1F:C957:9D 02 02 STA $0202,X @ $0203 = #$00
1F:C95A:A5 1B LDA $001B = #$B0
1F:C95C:9D 03 02 STA $0203,X @ $0204 = #$10 (This is the "02" that we hang on)
1F:C95F:E6 19 INC $0019 = #$E4When all else fails... manipulate the source code.
He may very well have. I may not have put in the proper fix in my mod. But I did apply the 2 IPS patches, and on a whim decided to check Guo Si's status, and to my surprise he was still dying.
When all else fails... manipulate the source code.
I also found where the Gemsword is found, in Wang Yun's safe. (19 is Gemsword's ID)
Code:0E:8BE4:A9 19 LDA #$19This instruction is found at 0x38bf4.
When all else fails... manipulate the source code.
Fixed a small bug… it's the notorious mysterious "Smite Guo Si" bug. You know the one… if you were to cancel the leader's move in battle, it overwrote $6312 with "00". This has the effect of killing Guo Si and removing him from the game.
Here's the fix:
0x3ae2b:
Code:"A678 A900 9D1362" -> "A91E 2082C4 EAEA"0x7ae2b:
Code:a90e 2082c4 a678 e0ff d002 a200 a900 9d1362 4c1baeEffectively, this subroutine was zeroing out something concerning officer orders. It is officer before the one that canceled that is affected by this subroutine. Of course, when we cancel the leader's orders, we zero out the value corresponding to the member who goes before him in battle… and that means "ff" gets added to the pointer where party orders get stored ($6213). So "00" is placed in $6312, which happens to be the status byte for poor old Guo Si. You just toasted him.
The new subroutine checks for the "ff" value, and puts a "00" in there instead, thus saving Guo Si's life. I'd say he owes me now :cactuar:
When all else fails... manipulate the source code.
Quote:Speaking of which. Lud would it be ok if I added another little subroutine to your latest thing?Nice! That's perfectly fine. I like your ideas for new attributes. I'm actually very interested to see what you have cooking. Just how much work are you looking at? 8O
When all else fails... manipulate the source code.
Quote:That said, since this enhancement is at the end of battle it might be a great place to implement our little fix for your A.I. bug theory. I might borrow your jump off point there for that.Wonderful idea! I'd love it if you'd publish the code for that if you get it written before the end of the night. My best guess is that zeroing out the Enemy Tactic lists would be the most important thing.
When all else fails... manipulate the source code.
Thanks!
It was interesting to figure out where to put it in the battle victory routine, without borking everything. Then I got it to work, and was hearing the little typing sound, but no text was showing up :o I finally got it to work fully this afternoon.
When all else fails... manipulate the source code.
I have created the promised algorithm for Battle Spoils! :hook:
First, here are the Hex changes to the ROM. It requires at least a 512K ROM, and uses page 1E for its work.
0x3a547:
Code:"A900 8573 20D79A A202 1E0005 38 7E0005 CA 10F6" -> "a91e 2082c4 200d82 2095d4 ea a900 8573 20d79a"0x7a547:
Code:a90e 2082c4 4c50a5 ea 2082c40x7a560: This contains the algorithm guts. It decides whether something was found, and if so, whether it was a rare drop or not. Then, it picks a random item from 0 to 15, and gets that item from the correct chapter. Extra chapters are treated as the normal chapter of the same rank (Extended Wu would be treated as Wu).
Code:a202 1e0005 38 7e0005 ca 10f6 a5ad 6560
4a 65af 6510 297f c908 3005 a90e 4c40a5
65ae 4a 6561 6511 65ad 290f 856e ad3670
aa ca 8a 2907 0a 0a 0a 0a 656e 856e eaeaea
a5ae 6552 6511 6562 6563 297f c915 3010
a56e a8 b9d0a5 856e a900 856f 4c37a5 ea
a56e a8 b950a6 856e a900 856f 4c37a5 ea0x7a5e0 – 0x7a65f: These are the random common drops. 8 regions, 16 items per region. This item table just has ordinary items (Elixirs, Gullwings, Steeds, Power Pills, Revives, and Smoke Pots), except for one Red Hare in Wei's region.
Code:31313131313131313132303030282B2C
313131313131323232303030282B2C38
323232323232323330303028282B2C38
323232333333303028282B2B2C2C3838
32333333333330302828282B2C2C3838
33333333333334303028282B2C2C3838
34343434343434303028282B2C2C3838
343434343434302128282B2B2C2C3838EDIT: Alternately, this table weaves in some gold and ration drops:
Code:01010731313131313132303030282B2C
010208313131323232303030282B2C38
020309093232323233303028282B2C38
03040A3232333333303028282B2C2C38
04040A33333333303028282B2C2C3838
04050A0B3333333334303028282B2C38
05060B0C34343434343028282B2C2C38
060C0C34343434213028282B2C2C38380x7a660 – 0x7a6df: These are the random rare drops. 8 regions, 16 items per region. You will probably want to make these more helpful drops, such as equipment, as they can be offered rarely and thus can be made to not totally break the game. The format for this table is exactly the same as the common drop table.
Helpful tips to make Battle Spoils work for you
1. You can make all drops more or less common. The value to change is in this instruction:
Code:1E:A567:C9 08 CMP #$08This determines the chance, out of 128, to gain an item. Change 0x7a578, making it larger to make drops more common, and of course make it smaller to make drops more rare. Default drop chance is 8/128, or 1 in 16.
2. You can change the ratio of rare to common drops. The value to change is in this instruction:
Code:1E:A59C:C9 15 CMP #$15This is the chance, out of 128, that this current drop is rare, as when execution reaches this instruction, we know we are receiving a drop. Change 0x7a5ad, making the value smaller to make rare drops more rare, and larger to make them more common. If you change this value to greater than 0x40, you would be making "rare" drops more common than "common" drops– silly you :geek: . Default chance for this drop to be rare is 20/128, or 5 out of 32.
3. Obviously, you can change the items that drop. It does seem that you can make more gold coins or food rations drop. I don't recommend that you allow reception of items that you cannot sell or discard :wink:
I have tested this algorithm, and it will not bork the game if you don't have any space to put the item; it will just scream at you with the default message saying that you don't have any more room.
When all else fails... manipulate the source code.
Looks great! Sorry I wasn't around to help out in tracking down the palette stuff.
Quote:Also I noticed that the text colors change depending on where your party is. Ie…the palette for the text keeps changing.I've found that often, when traveling, the text is colored by the fourth color set. It usually pertains to water, but indoors it can sometimes look different than water (usually a floor tiling). The two-bit fontset requires a balancing act concerning the color the font should be, and how consistent you want the font coloring to be, based off of the colors that were set by the developers to set the moods for the various areas of the game.
When all else fails... manipulate the source code.
Quote:1. Lud – do you remember how to change the palettes for different parts of the screen? I've done it before but can't remember. The bottom two bars need to be the same color as the bars above it.I don't off the top of my head. I'd need to look at my notes but am camping right now (I'm actually at a store to stock up on supplies that I left) :scratch: Sorry.
Quote:2. Should I make the equip and tactic boxes wider and make the bars part a bit shorter?I think that would be a great idea. The wider you make them, the more creative modders can be with item/tactic names.
When all else fails... manipulate the source code.
That's a possibility. Other possible fixes might be to clear $60AF-$60B3 (Enemy General IDs) and $65CA-$65E7 (Available tactics for the enemy).
When all else fails... manipulate the source code.
Have you tried doing a breakpoint on write addresses 0x6205-620a, and watching what gets placed up there in the Hex Editor? That's what I'd try… It's not a problem with All-Out, so much, as I think it is getting confused with a tactics user from a previous battle (and DoaE doesn't overwrite the officers in the previous battle, if does not have to). In my testing something else, I could swear I saw the AI routine pick tactics for a dead officer…
When all else fails... manipulate the source code.
MiDKnighT–
I have a theory about the freezing bug during battle… I just faced a battle with four tacticians, and after I won that battle I was attacked by two wimpy regular forces (obviously no tactics). I gave my officers orders because I wanted one of my officers to heal everyone, because the last battle hurt like butt. It froze the first time, at the beginning of the round, but the second time I selected my same orders, the game accepted it and played out the round. I believe this may be a bug in the AI, which is picking tactics for enemy officers.
Maybe this could help in tracking it down?
When all else fails... manipulate the source code.
MiDKnighT–
That looks great. The only thing I could add would be to begin tactic names 1 character to the left, allowing the full 10 characters for names. It would also look aligned with your EQUIP box. My 2 cents.
When all else fails... manipulate the source code.
Quote:What address is the ppu editable for the blue/white mixture?If you bring up the PPU Viewer in FCEUX, you'll see the palettes at the bottom of the window. Those correspond to PPU Memory addresses 0x3f00-3f1f.
You can find the Status/Army/Battle screen palettes in the DoaE ROM at 0x7c687-0x7c696.
When all else fails... manipulate the source code.
