Mr01sam
-
Posts
1,245 -
Joined
-
Last visited
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by Mr01sam
-
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.
-
Hmm, so I just tried this and I couldn't get it to happen - it only deducted one raid point. I had -Player A has a base with stacked privs (two total) -Player B uses the MLRS rocket to attack Player A's base -The rockets hit both TCs, but after the first one was hit the raid was logged and consumed one point, the following rockets did damage but did not consume and more points since the raid was already logged Is there perhaps more details that are important here? A couple questions that might help: -Do you have any plugins that may affect TC ownership or MLRS rockets? -Is the base able to be raided normally and logged properly? -Do you have revenge raiding on? -Are you able to reproduce this issue consistently?
-
I'm not familiar with AutoZones, but in 1.3.0, you will be able to specify a partial match for the zone name or id. So you can do something akin to "all zones that contain the word 'pvp' in their name will force you to be pvp" will that handle that case? And no - when a player enters a pvp zone they still retain their "true" mode under the hood, so it doesn't affect anything they own outside the zone. -
I'll check it out - can you verify that this scenario is correct (so that I can reproduce it) - Player A has a base - Player A has full raid points - Player B attacks Player A's base with the MLRS rockets - This attack causes Player A to lose all their Raid Points
-
Would you be able to create a support ticket for this - otherwise it makes it harder for me to track when its in this discussion board. -
Depending on how they achieve that, it might be conflicting with quality crafting. Have you noticed this problem with the other weapons? Or just the new smg?
-
Is Damage Scaler another plugin?
-
Very close.. in v1.2 of WarMode (the current version), you have to specify the zone id (not the zone name), and the value is just a string not a list. So it would need to look like this. "ZoneManager": { "ForceModeInZone": { "zoneidhere":"pvp", } }, This will make any zone that has a zone id of "zoneidhere" a forced pvp zone. Now, if you want to use the zone name instead, that's actually a feature I'm adding in v1.3 of WarMode, which is currently being tested.. if that's something you're interested in, I can DM you an early copy to try out if you would like. Just let me know!
-
WarMode doesnt have any rules for hacked crates (since they aren't owned by players) so yes, there is nothing stopping a PVE player from grabbing it. However, I highly recommend using WarMode alongside ZoneManager in this situation to setup zones that are forced PVP. You can do this in the config, and then PVE players will have to enter the forced PVP zone if they want to loot the hacked crate. Edit: Some people suggested LootDefender, which is another great option!
-
Hey thanks for the feedback, I'll note this down as a suggestion 🙂 -
Can you provide some info on when this happens and what simple status plugins you have? It looks like some plugin is not providing a translation string in the right format.
-
Ah okay, then this makes sense for how it currently works. It currently does not know a difference between a backpack that was willingly dropped and one that was dropped due to death. In the case of death - typically people don't want other players to be able to loot PVE players, which is why PVP -> PVE and PVE -> PVE interactions wont let you loot the backpack. For the time being, if you want backpacks to be lootable, you would have to enable players to be able to loot PVE players. In the next update I'm going to be expanding the granularity of what is protected/unprotected, perhaps I can include a section for backpacks so you can choose how you want backpacks to be handled specifically. Also, I'm going to be including fixes for a lot of your bug reports in the next update too, which is a big update so that's the reason why its taking some time (just so you know!). As for the parachute, I'm not sure what's going on there - is it possibly within a building zone that belongs to someone else? As for clans support, currently it just supports team members, but I'm considering support for clans as well.
-
Changed Status from Closed to Not a Bug
-
Changed Status from Pending to Closed
-
Currently, WarMode only protects containers that are placed within building zones, so if they are outside of a building priv then it is working as expected if they are not protected. I can add this as a feature suggestion though.
-
Changed Status from Pending to Closed
