Mr01sam
-
Posts
1,443 -
Joined
-
Last visited
-
Days Won
26
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by Mr01sam
-
Oh, yeah, that is a big list... lol. Is there any you think might affect teams?
-
Hmm the way it currently is "supposed" to work is that the Infliction Damage Action : "melee" property should make it so grenades do not inflict it, and only melee attacks do. If thats not working, then it sounds like its a bug. -
Thats really weird, I can't really think of what WarMode would be doing to prevent that. If possible, can you provide a list of your plugins you have?
-
As for the flag thing - yes! You can set a cooldown duration for using the /flag command, which I think is essentially what you are asking. This was actually missing from the google doc (my bad!) but it does exist. The cooldown is in seconds, so for 7 days you would want 60 * 24 * 7 = 10080 for this value. For the team thing, the plugin does not prevent players from joining teams, however you can set it to force players modes when they join a team. By default, if there is a team of PVP players and a PVE player joins that team, then the PVE player will be forced into a PVP mode. You can enable or disable this feature with the SyncModeWithTeamMembers option. Each Mode has a priority assigned to it, and it willl force all players within the team to whatever mode they share that has the LOWEST priority. Using default settings, PVP has a priority of 1 and PVE has 2, so PVP is the lower priority, so all players in the team will be forced to PVP. A similar thing happens with bases - if a base has both PVP and PVE owners, then the base will be considered PVP. I can add prevention as a suggestion as well if you would prefer it work like that. | -
I have not heard this before - would you be able to open a support ticket and add details?
-
I think I need some more info. Time period as in days into the wipe? Or as in the amount of time the protection has been active for? In general, the answer is no. However, the plugin is permission based, so you could alter player permissions and give them different protection levels after a certain amount of time in the wipe. -
which button? -
Changed Status from Pending to Closed Changed Fixed In to 1.3.0
-
Changed Status from Pending to Closed Changed Fixed In to 1.3.0
-
Changed Status from Pending to Closed Changed Fixed In to 1.3.0
-
Changed Status from Pending to Closed Changed Fixed In to 1.3.0
-
Changed Status from Pending to Closed Changed Fixed In to 1.3.0
-
That's very helpful, thank you!
-
Sounds good, since I don't have that plugin it may be difficult for me to fix - but hopefully if you can provide enough info I can patch it for you!
-
Hey, can you give some context as to when this is happening? Do you have any custom vehicle plugins?
-
I'll take it as a suggestion for sure
-
You can adjust the Y offset of these tabs in the RaidProtection config.
-
Okay I will take a look when I can
-
Does the error occur if you reload it again? - Also did you previously have any version of quality crafting?
-
Yeah, I actually had to rewrite all the logic in 1.3.0, so theres a chance it might work a little different - let me know what you find!
-
Is this the current version of WarMode (1.2.2) or the beta version I sent you (1.3.0)? Because those messages look like the 1.2 version?
-
Just an update - I did try it on oxide (same test as above) and I still couldn't get the issue to occur unfortunately.
-
You know what, my server is carbon, I haven't tried it with oxide - I can try that next
-
Alright, I loaded up your exact config and tried to reproduce what you had going on in the video - unfortunately, I still couldn't get it to consume two points, it still correctly only deducts 1 point. I provided a video, maybe you can identify what I'm doing differently? The only thing I can think of is I noticed in your example, there is a small elevation distance between your TCs. Something you could try is upping the distance at which TCs are considered "stacked", because it may be that your 2nd TC is just barely out of range of the other one. To do this, you can look for this part of the code, and change this "20f" value to "25f" or something like that and see if that fixes the issue. Video 2024-11-20 12-51-30.mp4
-
Thats really good detail you provided so hopefully I can reproduce it - I'll check out your video and try again later today.
