Patrol Helicopter Napalm Not Damaging Players

Roine

Supporter
Hi
It appears that players are not damaged by the napalm flames fired by the patrol helicopter.
Maybe this has been happening since the official update this month.
My server uses TruePve and this has never happened before.

Can you help me solve this isuues?
 
I'll need the following details to figure out what happened:
  • The data file for the helicopter tier that fired the napalm
  • How the helicopter was spawned:
    • Was it automatically spawned by the plugin, or
    • Spawned using a command?
  • If it was spawned via command:
    • The exact command used (full line)
    • Where it was entered: server console, F1 console, or chat
  • If a player called it in:
    • Was the player who got hit by the napalm the same one who called the heli, or part of their team?
  • Any True PVE rules you have that might block napalm damage
 
How the helicopter was spawned:
Shop UI to call for helicopter

Was the player who got hit by the napalm the same one who called the heli, or part of their team?
the same one who called the heli

Any True PVE rules you have that might block napalm damage
TruePve has Fire cannot hurt players rule.

As a side note, from my research, it appears that the helicopter does not own the napalm and its flames fired from the helicopter.
I am not sure if this is a bug or an official spec.
Napalm used to have ownership from the helicopter, but not anymore.

I would like a good modder like yourself to investigate this issue.
 

Attachments

Custom Helicopter Tiers does nothing with fireballs (the ones created by napalm rockets), it doesn't handle them in any way, whether blocking or allowing, so if players aren't taking damage, that's coming from another plugin, in your case it's True PVE

By default, you should disable all heli-related flags or settings in any other plugin when using CHT. CHT already handles the PVE side of things as long as you enable the following settings:
JSON:
"PVE": {
  "Block Damage To Non Caller Players": true,
  "Block Damage To Non Caller Owned Entities": true
}
 
Back
Top
Chat commands start with a /, while console commands can be entered directly in the F1 console or server console. Use find <keyword> in console to search for available commands related to the plugin. Parameters in < > are required, while [ ] are optional.
This plugin uses Oxide's permission system. Grant or revoke permissions using oxide.grant and oxide.revoke. You can assign them to individual players or groups using their Steam id or group name.
Settings are stored in the config file found under the config/ directory. You can edit this file manually, then reload the plugin to apply your changes.
Persistent data is saved in the data/ directory. This includes things like saved settings, usage stats, or player progress depending on the plugin. Deleting a data file will reset stored progress or customizations.
Language files are located in the lang/ folder. To translate messages, copy the en.json file into your target language folder (e.g. fr, de) and edit the values. Reload the plugin after changes to apply new messages.
This section lists public methods exposed by the plugin for use in other plugins. You can call these via the CallHook method. Ensure the plugin is loaded before calling its API to avoid null reference errors.
These are custom hooks that other plugins can listen for. Simply define a method with the same name and expected parameters in your plugin to handle the event. Hooks are triggered at key moments and are useful for extending or reacting to plugin behavior.
These hooks are injected into the game's code using Harmony. They let the plugin run code at key points in the game's internal logic. You can return values to block or modify behavior. Use with caution — these are powerful and can affect core mechanics.
Cart