Joakim Posted November 29, 2012 Share Posted November 29, 2012 As per fixpack reamde, 15th lv. Haer'Dalis' extra long sword proficiency should be fixed, but unlike that this bug is not fixed with fixpack v9. As of v9.14's fixpack.tp2, this still exist, so I assume you may don't recognize. I hope this wil be fixed:) And I have some WeiDu questions. 1. In your fixpack tp2, beta fixes' kensai and monk weapon speed bonus bug fix ends like this. // kensai weapon speed COPY_EXISTING ~spcl143.spl~ ~override~ PATCH_IF (SOURCE_SIZE = 0xca) THEN BEGIN READ_LONG 0x64 "ho" READ_LONG 0x6a "eo" READ_ASCII "ho" ~h1~ (0x28) READ_ASCII "eo" ~fx~ (0x30) FOR (READ_SHORT 0x68 "hc"; "hc" < 10; "hc" += 0x1) BEGIN INSERT_BYTES ("ho" + ("hc" * 0x28) + 0x00) 0x28 WRITE_ASCIIE ("ho" + ("hc" * 0x28) + 0x00) ~%h1%~ WRITE_SHORT ("ho" + ("hc" * 0x28) + 0x10) ("hc" * 0x4) WRITE_SHORT ("ho" + ("hc" * 0x28) + 0x20) "hc" INSERT_BYTES ("eo" + ("hc" * 0x58) + 0x00) 0x30 WRITE_ASCIIE ("eo" + ("hc" * 0x58) + 0x00) ~%fx%~ WRITE_LONG ("eo" + ("hc" * 0x58) + 0x04) ("hc" + 0x1) END WRITE_SHORT 0x68 "hc" WRITE_LONG 0x6a ("eo" + (0x28 * ("hc" - 0x1))) END BUT_ONLY Why this ends with 'BUT_ONLY', not with 'BUT_ONLY_IF_IT_CHANGES'? What are the differences between them? 2. 'REPLACE_TEXTUALLY' syntax is sensitive to use. For example kitlist.2da 20 HELM 25196 25169 25222 CLABPR03 48 0x02000000 3 I should change '48 0x02000000 3' to '48 0x04000000 3' all, not only '0x02000000' to another, because there is another '0x02000000' kit in the list. But if the space is changed by another mod(In this case, the space between '48' and '0x02000000' is 12, but some mod changes this), 'REPLACE_TEXTUALLY' doesn't work. So this can't be universal. How should I do this to work universal? I hope to have your answers. Link to comment
CamDawg Posted November 29, 2012 Share Posted November 29, 2012 As per fixpack reamde, 15th lv. Haer'Dalis' extra long sword proficiency should be fixed, but unlike that this bug is not fixed with fixpack v9. Fixpack no longer messes with Haer'Dalis' proficiencies, so it's probably that we need to update the documentation. Why this ends with 'BUT_ONLY', not with 'BUT_ONLY_IF_IT_CHANGES'? What are differences between them? These two are equivalent. 2. 'REPLACE_TEXTUALLY' syntax is sensitive to use. For example kitlist.2da 20 HELM 25196 25169 25222 CLABPR03 48 0x02000000 3 I should change '48 0x02000000 3' to '48 0x04000000 3' all, not only '0x02000000' to another, because there is another '0x02000000' kit in the list. But if the space is changed by another mod(In this case, the space between '48' and '0x02000000' is 12, but some mod changes this), 'REPLACE_TEXTUALLY' doesn't work. So this can't be universal. How should I do this to work universal? REPLACE_TEXTUALLY uses regular expressions, so you could use something like REPLACE_TEXTUALLY ~48[ %TAB%]+0x02000000[ %TAB%]+3~ ~48 0x04000000 3~ The [ %TAB%]+ means to match one or more spaces or tabs, so it won't matter if the whitespace there has changed. Link to comment
Joakim Posted November 29, 2012 Author Share Posted November 29, 2012 Thx to your answer. '[ %TAB%]+' works fine! Would you let me know where to learn WeiDU syntaxes? WeiDU documentation isn't sufficient. Link to comment
CamDawg Posted November 29, 2012 Share Posted November 29, 2012 Honestly, the WeiDU docs are really it in terms of syntax. Looking through mods, especially tweak mods, are a great way to see how all of it works in practice. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.