- This topic has 645 replies, 10 voices, and was last updated 4 years, 9 months ago by
.
-
Posts
-
Quote:So this would essentially eliminate every officer from the game that wasn't on the list, right?
No, anyone with over 220 STR, AGI, or INT is safe by default. I assume most of your major characters would be safe because of that. I also recommend putting any rulers on the "Rare Duel List" which would make them 99% safe (but also put them on the no kill list just in case).
Okay so I put Gan Ning and Zhang Fei on the list. Zhang Fei on the death list by Gan Ning. It killed Zhang Fei and made Gan Ning unusable in battle. Gan Ning @ 4458 and Zhang Fei @ 4478.
When I reversed them though, it worked fine and removed Gan Ning from my party. But its a really random idea since what if they never duel you?
If you don't like this option and want to eliminate all "killing" you could change these 3:
0x50DB: DC (STR check – don't kill if target is over 220 STR)
0x50E7: DC (AGI check – don't kill if target is over 220 AGI)
0x50F3: DC (INT check – don't kill if target is over 220 INT)
Change those values to 00 and nobody will ever get killed (unless you put people on the mismatch list).
Quote:Okay so I put Gan Ning and Zhang Fei on the list. Zhang Fei on the death list by Gan Ning. It killed Zhang Fei and made Gan Ning unusable in battle. Gan Ning @ 4458 and Zhang Fei @ 4478.I'll check on that.
Okay so the way this works is if a general has under 220 of any stat they will be auto-killed in a duel?
Quote:Okay so the way this works is if a general has under 220 of any stat they will be auto-killed in a duel?No… Killing should be pretty rare. Here's the duel outcomes (updated):
If the duel is accepted, the two duel participants step forward and clash. There are many possible outcomes for a duel:
Close Match:
– Draw (2/3rd chance) – Neither participant gets any status change
– Both participants An Sha'd (1/3rd chance)
Clear Winner:
– One person is An Sha'd (2/3rd chance)
– Winner but both parties unharmed (1/3rd chance)
* The winner will either receive an agility boost (2/3rd chance) or a Bei Ji boost (1/3rd chance) after victory.
Mismatch (Think: Lu Bu vs Song Yong) –
– One person is An Sha'd (1/3rd chance)
– Loser flees and is his own men are disgusted (1/3rd chance). The fleeing general will lose Qi Shou and Bei Ji status and get Yi Xin status.
– Loser gets KILLED (An Sha'd and removed from the game) (1/3rd chance but this will also have stat protections (220+ STR, AGI, or INT) and a no kill list. If the officer is protected it will just be An Sha).
So the only way someone will be killed is if…
1. They have below 220 STR, AGI, and INT.
2. They get into a duel with someone far better (Lu Bu vs Song Yong)
3. They lose the duel badly.
4. Even after losing the duel badly, there is a 1 in 3 chance of getting killed after all of the above.
Kills should be pretty rare… All the important characters already have stat protections and human players aren't dumb enough to challenge far stronger generals to duels. The computer *might* offer a duel with a weaker general but that is rare too.
In any case, I think I'll go ahead and increase the difference it takes for a "devastating win" making "devastating wins" a little harder to get.
If you use the mismatch list all bets are off. That's the modder (you) saying "I want this guy to kill that guy".
Quote:Okay so I put Gan Ning and Zhang Fei on the list. Zhang Fei on the death list by Gan Ning. It killed Zhang Fei and made Gan Ning unusable in battle. Gan Ning @ 4458 and Zhang Fei @ 4478.I think this fixes it but I'd appreciate some more testing:
0x49B0:
008DE5BBC90AB0034C608AC93A90034C
0x49F0:
A5BBE5BAC90AB0034C608AC93A90034C
0x4E20:
7985B1A54B85B220B0904CDA89000000
0x4E80:
E03DD0034CA58DA57885B1A54B85B220
0x50F0:
4088C9DC90034C4891EAEAEA200090EA
EAEAEA20808BA6B2BDA860AAA9009D00
Arg… Still some issues if the enemy initiates the duel. Will fix…
I still think permakill is a bad idea. It's not my mod, though!
Hmm… theoretically an officer could be wounded so badly they need to recuperate in billeting for a bit (and, as such, are removed form the party for now). Obviously, "cannot remove from party" members are downgraded to An Sha, as are "parties" of only one officer.
Controlled killings would be much better than the "random" ones. I can think of a few instances where killing off a guy or three could be interesting :D So maybe I'll use it only for the "mismatch" point, if for certain battles you might lose someone important if you're too duel crazy heh.
Quote:Hmm… theoretically an officer could be wounded so badly they need to recuperate in billeting for a bit (and, as such, are removed form the party for now).Thats interesting. It might encourage people to not just use a "pack mule" as that person might be someone that would have to be used thus they would need equipment, but I do like the idea of risking certain guys, and not always your own. Maybe if you duel certain officers for an "easy win", you might kill them and thus not be able to recruit them in the future?
Well, what I was thinking is that someone who screws up badly (but not fatally badly) in a duel can simply be Revived. But if they're damaged enough to be banished to billeting (hello, DW3's Expel!), obviously that can't be revived!
On a side note, it just feels as if you could use a page swap command in the coding to swap to a post-normal page midcombat. Especially if we can get more tactics that way. ;)
Quote:I still think permakill is a bad idea. It's not my mod, though!The modder would have control over the feature and how much it is used.
Quote:On a side note, it just feels as if you could use a page swap command in the coding to swap to a post-normal page midcombat.The game is page swapping constantly. Mine and Lud's enhancements page swap like crazy. Just about every enhancement we have includes 4 page swaps. Original page –> page 1E –> page where we put the enhancement –> page 1E –> original page. But we can only put enhancements on the game's original pages (for which there is limited space) if we want access to the game memory (which is critical for most things).
Another little bug fix with the mismatch list:
0x5180:
60D96084D0034C8491A64ABDA8608810
0x51B0:
60D96084D0034CB491A64BBDA8608810
- You must be logged in to reply to this topic.