- This topic has 190 replies, 8 voices, and was last updated 4 years, 12 months ago by
.
-
Posts
-
Sure, I was just updating the bugs thread. Looks like we’re doing some major bug slaying today.
More like assassination :ninja:
0x798B9: “6D 73 60″–>”EA EA EA”
Not working properly. Officer that should have 68 Base AC still has 100
Lvl 52
STR 135/4
VIT 164/2
AGI 213/4 +
________
33+82+53= 168*2*52= 17472/256= 68… Cao Pi still has 100 >_>
Also I think the bar is not going all the way because even with 100 Base AC, there should be some bars, not just blank.
Darn, this is what happens when I’m trying to figure out lud’s code. Both these issues are totally lud’s by I’ll try to fix them anyway :D
Scratch that, I just realized something… Did you change the formula?
And the level is involved as well. Lud documented the original formula in the guide:
let x = STR/2 + INT/4 + AGI/4
If you did, I didn’t change the formula and will need these changes posted:
Now our new formula:
let x = VIT/2 + STR/4 + AGI/4
Base AC = x * 2 * level / 256, capped at 100This should be the new formula yes:
let x = VIT/2 + STR/4 + AGI/4
Base AC = x * 2 * level / 256, capped at 100Darn, this is what happens when I’m trying to figure out lud’s code. Both these issues are totally lud’s by I’ll try to fix them anyway
Yeah, every so often I get an email from him just saying hello. Last time I emailed him about the “last guy going first” freeze bug and he seemed pretty stoked that we were able to trap that.
This should be the new formula yes:
let x = VIT/2 + STR/4 + AGI/4
Base AC = x * 2 * level / 256, capped at 100Need the hex for that. I’d tell it to make pancakes if I could but I can’t code that either XD
So until I fix DoaEditor the solution is to just manually put FF (255) in the table at all 3 spots:
0x7AAA6: FF FF FF
The DoaEditor bug is with officer with multiple officer IDs. Way around is to manually update the tables:
To set the LDR for an officer, put the value at 0x7AA## where ## = officer ID
To set the VIT for an officer, put the value at 0x7AB## where ## = officer ID
To set the POL for an officer, put the value at 0x7AC## where ## = officer IDI’ll have to see how Niahak handled those cases in his code.
It seems that they are categorized by the LAST hex value in their series, for example, the first 3 below referencing http://kongming.net/doae/rom_hacking/battles/
Officer Hex values this affects:
A6-A8 Liu Bei (referenced as A8 @ kongming.net)
39-3B Chen Deng (referenced as 3B @ kongming.net)
A1-A4 Guan Suo (referenced as A4 @ kongming.net)
9A-9D Pang Tong
55-56 Sun Ce
98-99 Zhou Cang
05-08 Zhou Chao
3C-3D MI Zhu
B5-B7 Lu Bu (Shu)
45-46 Liu KuiOn another note, these are ALL sprites that I wanted to know how their sprite X,Y data was stored so they could be moved around to different locations. This might be useful to put in the guide. It might also be the key to discovering how James originally replaced the “Yuan Shu has the Imperial Seal” messenger with a recruitable Dian Wei.
I’ve got it. He applied his formula in 2 places. The change is bigger than what I first thought:
0x785D0: 850318B910644A65038503B99C61
0x785FD: “6D 73 60″–>”EA EA EA”
0x798B9: “6D 73 60″–>”EA EA EA”He must not have coded the AC bars with the formula.
Got it, gonna test it.
Awesome! FLEXX Applied it, check this out with his base AC of 25 + Wood H of 30 + Robe of 5 = the numbers don’t lie :thumright:
but at higher level armor there seems to be a problem…
Base AC = 68
Iron Helmet provides = 60 AC
Plate Mail provides = 75 AC
Total = 203With all armor unequipped it reads 68 which is spot on!
The code seems to be working, now the bar is just royally messed up.
Bar fixed. Just borrowing where Lud does his formula first, stick it in memory somewhere, then have the bar use that to read:
0x385C0: 2019CCE8AD4F7E
0x78260: EAEA4C5086
0x78660: 8D4F7EA9004CA185Give it a try then we’ll declare this one slain.
Ummm…. it erased ALL of the bars on the status screen lol
THEM have returned!
No bars!? What would the counts and dukes say!?
Ummm…. it erased ALL of the bars on the status screen lol
That would be because I messed up one of the locations (typo).
Wrong:
0x385C0: 2019CCE8AD4F7E
0×78260: EAEA4C5086
0×78660: 8D4F7EA9004CA185Right:
0x385C0: 2019CCE8AD4F7E
0×78620: EAEA4C5086
0×78660: 8D4F7EA9004CA185
- You must be logged in to reply to this topic.