Mr01sam
-
Posts
1,395 -
Joined
-
Last visited
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by Mr01sam
-
Changed Status from Pending to Closed
-
Cool, I appreciate it - thanks for keeping me updated. Let me know if you get to the root of it and need some action from me
-
Okay, got a fix for the signs and carpets coming for the next release. The bbq seemed to already be protected properly when I tested it today. As for the heli thing, I dont think there is something I can do for that at this time.
-
Im confused, doesnt oxide say its loaded right here?
-
Changed Status from Pending to Closed
- 1 reply
-
- 1
-
-
Thats very bizarre, I haven't heard of that issue before... is there any error in the server console?
-
Yup, if it's set to free it's automatically enabled as long as there are "owners" (people authed on it) that have the proper raid protection level. -
It is intended that the raid limits only applies to REAL player bases. I haven't tested it with raidable bases yet, but it is not supposed to limit raids against those generated bases. -
Unfortunately no, as of right now - if you set it to be free, there isn't a time limiting factor attached to it. It would remain free until the TC is broken (from decay) or until the protection permission changes.
-
I thinki I might need some more info on how your raidable bases is configured, can you open a support ticket? (if you haven't already) -
I'll take a look! If you haven't already, can you open a support ticket? That way I won't lose track of it. Thank you!
-
Hey no updates for this, I'm still not sure what is happening here... you said the found has the ignore perm, but you still want the base protected? If thats the case, can you use the admin commands to assign a different founder?
-
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!
