Mrls and PVEFixed

Hello Nivex,

We want to have the mrls  to do NO damage. How can we fix it.

the default configuration will block MLRS damage via defaultAllowDamage being set to false. otherwise a rule is allowing it, possibly. hard to tell without a tpve.trace file to verify this

same issue here as of the latest update.  this is a big problem....bases are being essentially destroyed.

I tried to add a ruleset and it makes no difference with building blocks - but does prevent player damage.
do we need to specifially make a RuleSet for buildblocks and walls?

 

Trace here:
======================
== STARTING TRACE ==
== 18:08:21.13398 ==
======================
From: MLRSRocket, rocket_mlrs
To: BuildingBlock, wall
No shared locations (empty location) - no exclusions
No exclusion found - looking up RuleSet...
Using RuleSet "default"
Initiator empty; allow and return

======================
== STARTING TRACE ==
== 18:08:21.13418 ==
======================
From: MLRSRocket, rocket_mlrs
To: BuildingBlock, wall
No shared locations (empty location) - no exclusions
No exclusion found - looking up RuleSet...
Using RuleSet "default"
Initiator empty; allow and return

======================
== STARTING TRACE ==
== 18:08:21.13432 ==
======================
From: MLRSRocket, rocket_mlrs
To: BuildingBlock, wall
No shared locations (empty location) - no exclusions
No exclusion found - looking up RuleSet...
Using RuleSet "default"
Initiator empty; allow and return

======================
== STARTING TRACE ==
== 18:08:21.13446 ==
======================
From: MLRSRocket, rocket_mlrs
To: BuildingBlock, wall
No shared locations (empty location) - no exclusions
No exclusion found - looking up RuleSet...
Using RuleSet "default"
Initiator empty; allow and return

some config:

"RuleSets": [
{
"name": "default",
"enabled": true,
"defaultAllowDamage": false,
"flags": "AuthorizedDamageRequiresOwnership, LockedBoxesImmortal, AnimalsIgnoreSleepers, HumanNPCDamage, NoHeliDamage, LockedDoorsImmortal, AdminsHurtSleepers, SelfDamage, TwigDamage",
"rules": [
"anything can hurt dispensers",
"anything can hurt resources",
"anything can hurt heli",
"anything can hurt npcs",
"anything can hurt ch47",
"anything can hurt fireworks",
"players can hurt cars",
"players cannot hurt players",
"players cannot hurt traps",
"traps cannot hurt players",
"mlrs cannot hurt players",
"highwalls can hurt players",
"barricades can hurt players",
"npcs can hurt players"
]
},

{
"name": "mlrs",
"members": "rocket_mlrs, MLRSRocket",
"exclusions": ""
},

admins can use "ent kill" on the mlrs to remove it from the server  ..thats the option i had to use on my pve server ..will not spawn unless map is wiped after that (does not effect the mil base just despawns the mlrs)

https://pastebin.com/shZvWQya


save as TruePVE.cs

try this and it should solve both issues where

1. initiator is empty - now blocked by default for MLRS Rocket
2. initiator is not set to player because they dismount too early - initiator is set regardless now

I should mention there are some changes to the flags where SamSitesIgnorePlayers was removed in favor of StaticSamSitesIgnorePlayers and PlayerSamSitesIgnorePlayers

either way this version is for testing even though i believe it to be stable
mrInappropriate

admins can use "ent kill" on the mlrs to remove it from the server  ..thats the option i had to use on my pve server ..will not spawn unless map is wiped after that (does not effect the mil base just despawns the mlrs)

There's a plugin called No MLRS Mount which prevents players from getting in the cab of the MLRS launcher. That's what I've used while trying to find out why MLRS damage isn't being prevented.

still awaiting feedback on the above test version

nivex

still awaiting feedback on the above test version

Tested it on my PVE server for 3 days. MLRS is fixed, everything works great. I have at evening around 90 players online, so thumbs up. do it live

thanks for the feedback. I am busy atm so will finish up the update when i can :)

getting reports of the same problem. ill just wait for the update...

He already posted an update - read up

Locked automatically