Jump to content

Damage blocked to players if another raid is active

Pending 2.9.2

Ghosthunter
Ghosthunter

Posted

players tell me that in pvp bases (which spawn automatically in mine) they are encountering the following problem: they do not damage enemy players because it appears that they have another raid active. How can I remove this limitation? (this did not happen before)

nivex

Posted

heya, this hasn't changed

Prevent Players From Hogging Raids is true by default
Prevent Players From Hogging Purchased Raids is false by default

Ghosthunter

Posted (edited)

12 minutes ago, nivex said:

heya, this hasn't changed

Prevent Players From Hogging Raids is true by default
Prevent Players From Hogging Purchased Raids is false by default

my pvp bases spawn automatically, while the bases that are purchasable are pve, are the settings you're talking about ok as you wrote them? 

Edited by Ghosthunter
Ghosthunter

Posted

in my case, in the pvp bases, some players claimed that those who still had active raids didn't do damage but could suffer them

nivex

Posted

Prevent Players From Hogging Raids and other will prevent you from trying to own more than 1 raid.

I would need the exact message, from a screenshot is best

and your config

 

Ghosthunter

Posted

13 hours ago, nivex said:

Prevent Players From Hogging Raids and other will prevent you from trying to own more than 1 raid.

I would need the exact message, from a screenshot is best

and your config

 

"you have entered a raidable pvp base"

"you must finish your last raid at n4 before  joining another"

I don't know why players didn't complain before... but looking at the config I thought of changing the following parameters as follows:

1) "Apply Lockouts To PVP": false, (in my config it was TRUE)

2) "Prevent Players From Hogging Raids": false, (in my config it was TRUE)

do you think that with these changes players will always be able to kill each other in pvp bases?

nivex

Posted

yes, that is from the prevent players from hogging setting

nivex

Posted

what problem remains? it is not possible to get that message in PVP with the hogging options set to false ("<color=#FF0000>You must finish your last raid at {0} before joining another.</color>")

what message are you getting and when exactly?

Ghosthunter

Posted

I attach the video sent to me by the player who reported the problem to me

nivex

Posted (edited)

.

Edited by nivex
nivex

Posted

here is an alternate solution

o.grant group default raidablebases.hoggingbypass

 

Ghosthunter

Posted

Does giving this permission also affect the PVE bases purchased on my server? because I don't want the players to be able to make the bases they purchased in peace

nivex

Posted

no, it is strictly for the hogging option

Ghosthunter

Posted

the problem has not been resolved, players who are in a pvp raid cannot cause damage to other players if they try to contest another pvp raid

nivex

Posted

heya. what is the message now?

it is not possible to get the above message with that permission granted.

o.grant group default raidablebases.hoggingbypass

Ghosthunter

Posted

hello unfortunately even with that authorization the problem was not solved. As you can see from the attached combatlog the player in pvp base does not take damage

 

I'll attach a video to your next message

RUST_Screenshot_2024.10.16_-_15.14.19.73.png

RUST_Screenshot_2024.10.16_-_15.16.30.14.png

RUST_Screenshot_2024.10.16_-_15.23.02.32.png

nivex

Posted (edited)

hi. its impossible for your previous issue to persist with that permission granted.

describe the new problem in complete detail. step by step. write it in your native language.

DM your profiles and config too. in private message.

 

Edited by nivex
1.4m

Downloads

Total number of downloads.

6.8k

Customers

Total customers served.

101.4k

Files Sold

Total number of files sold.

2m

Payments Processed

Total payments processed.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.