1
Releases / Re: [FF7PC-98/Steam] New Threat Mod (v2.0.99994)
« on: 2024-03-26 05:42:56 »I took a look and it seems the majority of its attacks are %-based on the target's maximum HP. I'm unsure what a good way of getting through it without things becoming resource-intensive would be, as you'd likely need to burn a lot of Potions to deal with it. It's maybe worth trying grenades as they should deal a decent chunk of damage at that point. If you need more resource while in Reactor 5, Special Combatants drop Hi-Potions or Potions, Blood Hounds drop phoenix downs (and potions with a better rate than special combatant), and Proto-Machineguns drop Grenades. Sorry I don't have much better advice than that, 1.5's not too familiar to me by this point as a lot of time has passed.
I'm unsure what would be causing this; are you on Type A or Type B? Also, is this the main NT 2.0 IRO or one of the variants like the vanilla combat one?
I'll do a once over of it to get these things set back up; sorry for the inconvenience.
I wanted to go back to the original bosses for Type A and do different ones for Type B; they do have the same renovation to their attacks, AI, etc. as the 1.5 bosses do but a bit less drastic and closer to their original FF7 counterparts. Type B I could maybe expand on in the future; not all bosses were swapped out I think.
From what I can see, the only trigger is that you're on Disc 3 and Barret is in the party, both of which you have met. Are you on the regular NT 2.0 or one of the variants like vanilla combat? It'll be disabled for those.
I'll see what I can do about the Shinra Building one, that's intermittently come up in the past but I'm unsure of the cause. I think it may be related to the model listings or perhaps some corruption on the field itself that I need to try and fix.
The Junon League was removed in the 2.0 build, it was only in the 1.5 build.
Apologies I'm unsure if I am type A or B, I dont recall having the option. Its the main NT 2.0 IRO that I'm using. I've since changed my FFNx from stable to canary version and that seems to have resolved the issue. Not sure if its temporary fix or not but it seems to be ok.