You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some servers prefer to have all biomes force PvP Mode ON and only set the 'home biomes' for a players selected faction as biomes where players are allowed to toggle PvP Mode.
This would require a 'reverse' approach to the 'enemy biome override' mechanic and eventually, an individual approach as well. I think it might be done using the current system and an extension that may become available as soon as we connect this mod to the part of Lembas that will manage player prefixes (selected faction) and other individual player related aspects.
Imagine one high level toggle setting whether a server wishes to set biome override based on either 'enemy biome overrides: EBO' or 'safe biome overrides: SBO'.
In the case of EBO, the default, the biomes specified with each alignment precondition in the 'enemy biome override config' will trigger forced PvP Mode ON.
In the case of SBO, the reversed approach, the biomes specified with each alignment precondition in the 'enemy biome override config' will trigger the players ability to toggle PvP mode, but based on the reversed alignment precondition.
Example: If the enemy biome config has alignment precondition 'GUNDABAD: 100; 2'.
For EBO, players principally have the choice to toggle PvP everywhere, except when they enter an enemy biome. In this case players with a GUNBABAD alignment smaller than +100 will get PvP Mode forced ON when entering the Misty Mountains, and only players with GUNDABAD alignment higher than 99 will not get a PvP Mode override.
For SBO, players principally have PvP Mode forced ON, except when they enter an safe biome. In this case players with a GUNBABAD alignment higher than +99 will get the opportunity to toggle their PvP Mode when they enter the Misty Mountains, and any other player will not get that opportunity.
So, primarily, this would require a recode of the code and texts now used for the 'enemy biome override' feature:
Add a config input parameter determining whether the mechanic is to use the default EBO approach or the 'reversed' SBO approach.
Add an alternate condition check.
Ensure users comprehend all naming and messaging, including descriptions and explanation in config, wiki, etcetera related to this feature.
This issue is meant to ensure the 'safe biome override' system will be implemented. Another issue, #HOLD, aimed to support 'faction selection & allocation' for players, will depend on this issue to be implemented. That issue, is planned for implementation in a v3 of the PvP Mode mod, when the mod is more structurally connected to other server utility functionalities and support systems.
To reduce the stress on v2.0, and to ensure this is realised before v3.0, I propose to assign this issue to v2.1 or a later v2.subversion.
The text was updated successfully, but these errors were encountered:
Some servers prefer to have all biomes force PvP Mode ON and only set the 'home biomes' for a players selected faction as biomes where players are allowed to toggle PvP Mode.
This would require a 'reverse' approach to the 'enemy biome override' mechanic and eventually, an individual approach as well. I think it might be done using the current system and an extension that may become available as soon as we connect this mod to the part of Lembas that will manage player prefixes (selected faction) and other individual player related aspects.
Imagine one high level toggle setting whether a server wishes to set biome override based on either 'enemy biome overrides: EBO' or 'safe biome overrides: SBO'.
Example: If the enemy biome config has alignment precondition 'GUNDABAD: 100; 2'.
So, primarily, this would require a recode of the code and texts now used for the 'enemy biome override' feature:
This issue is meant to ensure the 'safe biome override' system will be implemented. Another issue, #HOLD, aimed to support 'faction selection & allocation' for players, will depend on this issue to be implemented. That issue, is planned for implementation in a v3 of the PvP Mode mod, when the mod is more structurally connected to other server utility functionalities and support systems.
To reduce the stress on v2.0, and to ensure this is realised before v3.0, I propose to assign this issue to v2.1 or a later v2.subversion.
The text was updated successfully, but these errors were encountered: