hlsdk-portable
hlsdk-portable copied to clipboard
FWGS
NPCs ignore pit drones how to fix it
Hello there so i been playing half life opposing force on phone okay? I got this issue of having NPCs not shooting pit drones now i only want friendly grunts to attack them since i have them with me most of the time using a spawner to spawn marines you normally leave behind since they cant get in vents jump etc here is how they treat pit drones
My question is how to fix this? If you can edit the behavior of friendly grunts to shoot pit drones that be enough to help me then upload the file and give me it (: i will owe you a beer XD
Hi. Where did you take Opposing Force for Android from? You're probably using the LostGamer's launcher or some other outdated version.
There's an issue with pitdrone relationship in our current opfor branch, indeed, but it's a different one - pitdrones won't attack barneys. I've made a PR to fix it https://github.com/FWGS/hlsdk-portable/pull/327
Anyways someone will have to make an updated Opposing Force launcher for Android and I'm not sure who's responsible for it. Especially considering that the new xash3d-fwgs engine is not quite ready for Android yet.
Hi. Where did you take Opposing Force for Android from? You're probably using the LostGamer's launcher or some other outdated version.
There's an issue with pitdrone relationship in our current opfor branch, indeed, but it's a different one - pitdrones won't attack barneys. I've made a PR to fix it #327
Anyways someone will have to make an updated Opposing Force launcher for Android and I'm not sure who's responsible for it. Especially considering that the new xash3d-fwgs engine is not quite ready for Android yet.
Yes it said to me that its an old version here is a pic of it
I can confirm, that the old OF port by Hing has this issue with pitdrones. I checked updated OF dlls from hlsdk-portable, and they seem to work properly. Regarding Android version we still need an updated OF APK to fix the problem.
@nekonomicon can we just close this issue as it's clearly not an issue with this sdk, but with the one that was used to make the Android build?
