-
Posts
1,609 -
Joined
-
Last visited
-
Days Won
28
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by Mr01sam
-
- 314 comments
-
- 1
-
-
- 299 comments
-
- #protection
- #base
- (and 5 more)
-
So if a base has mixed mode owners (some of the owners are pvp, and some are pve) then the base's mode will be whatever mode is first priority among the modes. With default settings, pvp mode overrides pve mode. So in the case where a base has some pvpers and some pvers, the entire base is considered pvp - so it can be raided by other pvp players. Same goes for teams, if a team is mixed of pvp and pve players, then all the players in the team will be set to pvp (if you have the team sync config option enabled).
- 314 comments
-
- 1
-
-
- 314 comments
-
This plugin lets you customize every interaction a player has with other players. By default, PVE players cannot raid other players at all - it wont let them damage other players buildings and yes other players cannot harm them either. However, this is just the default settings, you completely change these interactions. I recommend also downloading the extension plugin WarMode Admin Panel (its free) which will let you configure all these interactions in game and instantly apply changes.
- 314 comments
-
Yes - you can have it so PVE players can only use X command and PVP players cannot use that command. Each mode has its own oxide group that gets generated. For example, the PVE mode group is called "warmodepve" you can assign permissions to this group like you would with any other oxide group. So yes, you can control if a player can use a command based on the mode they have.
- 314 comments
-
- 314 comments
-
- 299 comments
-
- 1
-
-
- #protection
- #base
- (and 5 more)
-
- 314 comments
-
You are correct, if you disable TruePvE that will resolve conflicts - but you don't have to disable all of TruePVE, you only need to disable that parts that WarMode already covers. The rule of thumb for managing conflicts is you dont want two plugins trying to do the same thing. So for example, if you want TruePVE to handle player damage but you want WarMode to handle raid damage, then you would turn off player protection for WarMode and you would turn off building protection for TruePVE.
- 314 comments
-
The fire damage over time damage is disabled by WarMode, and this is because Facepunch currently does not give us the info on who the source of the fire was, so WarMode doesnt have enough info to determine if someone should take damage or not - so by default it disables all fire damage so that PVP players cannot use fire to damage PVE players. This is only for the damage over time effect though, the direct damage from incendiary rockets and bullets will still follow normal rules - just the damage over time is disabled. In the next patch I'm adding a config setting so that you can control this a little more. If you want the better chat prefixes to be colored, you have to set the color in the ModeTitleFormat setting under the BetterChat section of the WarMode config. For example, if you wanted the prefix to be a reddish color you can do something like "BetterChat": { "ShowModePrefixInChat": true, "Modes": { "pvp": { "ShowModeTitleInChat": true, "ModeTitleFormat": "<color=#eb4034>[{0}]</color>" }, "pve": { "ShowModeTitleInChat": true, "ModeTitleFormat": "<color=#34eb65>[{0}]</color>" } } }, This should make it so the mode pvp shows up as a reddish color (eb4034) and pve shows up as a greenish color (34eb65) these are codes for hex colors, so you can Google different colors if you want. I know its confusing because in the warmode admin panel it allows you to pick a color for each mode, so it would be nice if it just applied those to BetterChat as well. However, BetterChat allows you to format more than just colors, so it needed its own configuration setting. I hope this clears things up.
- 314 comments
-
- 1
-
-
- 314 comments
-
- 299 comments
-
- #protection
- #base
- (and 5 more)
-
- 299 comments
-
- #protection
- #base
- (and 5 more)
-
- 314 comments
-
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. |
- 314 comments
-
- 1
-
-
- 314 comments
-
- 1
-
-
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.
- 299 comments
-
- #protection
- #base
- (and 5 more)
-
- 314 comments
-
- 1
-
-
- 314 comments
-
- 314 comments