A new version of FFTPatcher is available! (0.497)
Started by Elric, September 28, 2019, 08:59:34 am
Quote from: TerrorSkeith on October 06, 2019, 02:30:30 amwill there eventually be an option with WoTL's translation? or will you be keeping the patch only with the PSX translation?
Quote from: Nyzer on December 14, 2019, 02:09:25 pmI'm pretty sure the new Dark Knight skills just point at the regular Weapon Damage formula, but don't quote me on that. AFAIK there shouldn't be a problem with changing their formula, as their weapon requirements ought to be dependent on their ability slots rather than their formula.
Quote from: Elric on December 14, 2019, 08:45:29 pmARH controls all of ashley riots skills and ALSO sets the requirements for the sword skills from vanilla. They are unchecked in fftp because thats how ARH has always worked, it may be a mini version of ARH, but that is still the same. So yes, changed will conflict, make your changes in ARH instead.
Quote from: RetroTypes on January 11, 2020, 08:20:54 pmSo I'm gonna go out on a limb here and assume more complicated ASM's like RAD 3 wouldn't work in conjunction to the TLW patch? A quick try produced broken results for me, from abilities not being moved around like I'm trying, to sprites changing to vastly different ones mid scene/battle. But maybe (likely lol) I'm missing something?
Quote from: Elric on January 11, 2020, 08:49:55 pmI mean... did you check that your RAD3 XML wasn't conflicting with other ASMs in the packed in resources? First and foremost, you cannot simply just add stuff to TLW. If you want to do that, you're gonna need to download the resources pack and make a new image yourself with my instructions, and include any new ASMs you want to add.I'm going to assume you did not do this, hence the issues you are having... RAD3 is a very broken ASM, and you are almost certainly correct in that it's not going to work with TLW. Considering how large the DK hack is, and how much space RAD3 takes up. I would not recommend RAD3 tbh, but to each their own. Remnants of that mod were in the initial build of Jot5, and caused many issues even without conflicts.It's also entirely possible that you simply did not setup RAD3 correctly, so it could be a combo of both. However without you checking the conflict checker in orgASM with your RAD3 xml, against the TLW ASMs, there is no way of knowing, and i don't have time to test that myself, which is why we released the resources.
Page created in 0.016 seconds with 23 queries.